Create a webhook and configure its target

arinova.webhook.create_webhook requires name. targetType defaults to none, enabled to true, and optional ISO-8601 expiresAt gates inbound requests.

The accepted target shapes are strict:

- none: targetConfig must be {}. - post_to_conversation: requires conversationId and messageTemplate; senderType may only be system. - create_card: requires boardId and titleTemplate; optional columnId, descriptionTemplate, and label UUIDs. - run_workflow: requires only workflowId. The workflow must belong to the webhook owner and be active when the event dispatches.

For run_workflow, accepted JSON becomes workflow trigger_payload unchanged; top-level fields use {{trigger.payload.field}}. Its separate 102,400-byte payload cap is smaller than the 1 MiB inbound limit; excess becomes render_error. Success means run creation, not completion. Once that Workflow creates its default ten runs in the rolling hour, counting every status, the function is skipped as workflow_rate_limited.

A missing target rejects create/update. An existing target without owner access saves with targetPermissionWarning but fails until fixed. Dispatch rechecks captured target configuration.

Each owner may have 100 non-cancelled Webhooks. Create returns plaintext signingSecret once; store it immediately. Idempotency replay omits it, and list/get never reveal it. Update handles metadata, target, enabled, expiry, or status: active; rotation is separately confirmed.

Related actions

arinova.webhook.create_webhook, arinova.webhook.update_webhook, arinova.webhook.get_webhook

Also known as

create webhook, targetType, targetConfig, post to conversation, create card, run workflow, destination

---

Machine-readable Markdown · Knowledge index