AsyncAPI channel · Coda
· Coda Automations Push API
docs/{docId}/hooks/automation/{ruleId}
Inbound channel: the per-rule webhook trigger URL for a single
webhook-invoked automation rule inside a single Coda doc. The
{docId} and {ruleId} path parameters identify the target doc and
automation rule; the rule itself is created in the Coda doc UI by
selecting the "Webhook" trigger type, which provisions this URL.
One inbound POST corresponds to one automation trigger. The body is
delivered
docId — ID of the doc. Example value from the API reference.
ruleId — ID of the automation rule. Coda automation rule IDs are prefixed
with the surface they live on (e.g. "grid-auto-").
Operations
publish
triggerWebhookAutomation
Trigger a webhook-invoked automation rule
Messages
WebhookTriggerJsonRequest
JSON payload delivered to a webhook-invoked Coda automation rule.
The payload is an open object; Coda does not constrain its shape
and exposes the parsed fields to the rule's actions.
Content-Type: application/json
WebhookTriggerFormRequest
Form-encoded payload delivered to a webhook-invoked Coda automation
rule. The Coda OpenAPI source lists
`application/x-www-form-urlencoded` as an accepted content type for
this endpoint alongside JSON
Content-Type: application/x-www-form-urlencoded
WebhookTriggerTextRequest
Raw text payload delivered to a webhook-invoked Coda automation
rule. The Coda OpenAPI source lists `text/plain` as an accepted
content type for this endpoint; the body is treated as an opaque
string.
Content-Type: text/plain
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.