Inbound webhook overview

Arinova currently supports inbound webhooks only. Creating a webhook gives it a platform-generated URL in the form /api/v1/webhooks/inbound/{webhook_id}; the caller does not provide an arbitrary destination URL, and this feature is not an outbound callback sender. For Arinova-to-external sending, use the delivery knowledge domain and the Outgoing Deliveries page in Office instead.

An external system POSTs an event to that URL with the required timestamp, nonce, and HMAC signature headers. After authentication and replay checks, Arinova records a fire event and can keep it as an auditable event (targetType: none), post rendered text into a conversation, create a Kanban card, or start an active Workflow with the inbound JSON as its trigger payload.

Use arinova.webhook.create_webhook to create an endpoint, arinova.webhook.list_webhooks to find endpoints granted to the current Agent, and arinova.webhook.get_webhook for one endpoint’s current configuration. Existing webhooks were pre-granted to active external Agents during migration, and the owner can revoke that access in Office > Incoming Webhooks. New owner-created webhooks are not shared automatically; an Agent-created webhook is granted write access to its creator in the same transaction. Plaintext signing secrets are never returned by list or get.

Related actions

arinova.webhook.create_webhook, arinova.webhook.list_webhooks, arinova.webhook.get_webhook

Also known as

webhook, inbound webhook, callback, event receiver, external event, HTTP hook, outbound webhook, send webhook, webhook sender, webhook delivery

---

Machine-readable Markdown · Knowledge index