Automations
Webhooks in and out
Start an automation from any system with its webhook URL and token, and call other systems from a flow with the API / Webhook step.
On this page
Webhooks connect automations to systems Unobits does not have a built-in tool for. In: another system calls an automation’s webhook address to start it. Out: a flow calls another system’s address with the Call webhook step.
Start an automation from another system#
Use the Webhook received trigger (in a flow, the Incoming Webhook step). Each automation has its own address and secret token:
https://<your app>/api/automations/<automation id>/webhook?token=<token>The other system sends a POST (or GET) to that address. The JSON body becomes the trigger’s payload, which you can use in conditions and later steps, for example payload.source.
Call another system from a flow#
Add API / Webhook Call (the Call webhook action) to a flow. It starts as a JSON POST with a small payload you can change:
{ "event": "{event.type}", "source": "unobits.automation" }Set the address, method, headers and body, and use tokens from earlier steps in any of them. Use Retries on failure on the step if the other system is sometimes unavailable; see Runs, errors and retries.
This is also how to reach the providers in the palette that do not run natively yet — Slack, GitHub, HubSpot and others: call their API with Call webhook.
Outgoing webhook fanout#
Send to outgoing webhook forwards the event to the workspace’s outgoing webhooks. Those subscriptions are set up through the developer API; there is no screen for them yet. Each delivery is signed with an x-unobits-signature: sha256=<hex> header and carries x-unobits-event-type. Deliveries are not retried.