AsyncAPI channel · Coda · Coda Automations Push API

`docs/{docId}/hooks/automation/{ruleId}`

Name: docs/{docId}/hooks/automation/{ruleId}
Creator: Coda

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

Open source AsyncAPI → All Coda channels Coda provider profile

Provider: Coda AsyncAPI: v2.6.0 Spec: Coda Automations Push API Operations: 1 Messages: 3

Channel address

docs/{docId}/hooks/automation/{ruleId}

Parameters

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.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.