Webhooks

A webhook subscription sends an event to another system as it happens: Full Fabric calls a URL you choose each time the event fires, with the event's details in the request. Use it to keep a CRM, a data pipeline or a custom integration in step with Full Fabric without polling the API.

Webhooks are managed from the settings (gear) menu, under Webhooks. The page has two tabs: Subscriptions and Activity.

Creating a Subscription

On Subscriptions, select Create subscription.

Field Behaviour
Event type The event to send, such as a form submission, an application submitted or a profile transition. Each option shows its technical event name underneath
Initial state, Target state Offered for profile transitions only. Pick a lifecycle state, or any
Webhook URL Where Full Fabric sends the event. Must start with http:// or https://

Select Create. A subscription to the same URL for the same event that already exists is refused with "Subscription already exists". Scheduled events (minute, hourly, daily) are not offered.

Warning: Use an https:// URL. Addresses that point at cloud metadata or link-local hosts are refused, but plain http:// is accepted and sends the event's data unencrypted.

The Subscriptions List

Column Shows
Trigger The event type
URL The webhook URL, marked POST
Runs How many times the subscription has fired
Created When it was created

The row menu offers Suspend, Resume and Delete, as for workflow templates (see Workflow Rules). Their confirmation messages say "workflow template"; they apply to the subscription. Subscriptions provided by Full Fabric are listed only for administrators and support staff, and cannot be deleted.

Workflow steps such as Call webhook work the same way as a subscription, from inside a workflow.

What Full Fabric Sends

Each delivery is an HTTP POST with a JSON body: the event's details, plus tenant (the institution's handle) and event_type (the event name).

Rule Behaviour
Timeout 5 seconds to connect, 10 seconds for the answer
Retries On a network error or a 5xx answer, the call is tried twice more, after about 5 and then 15 seconds
No retry A 4xx answer is final
Failure When every attempt fails, the delivery's workflow ends in Error (see Running Workflows)

Make the receiving endpoint answer quickly with a 2xx and do its work afterwards. Because a timed-out call is retried, the endpoint may receive the same event more than once.

The Activity Tab

Activity lists every delivery attempt:

Column Shows
Trigger The event type
URL Where it was sent
Status The HTTP status answered, green for 2xx, yellow for 4xx, red for 5xx
Payload The Request sent and the Response received, with Show more for long bodies
Date When the attempt was made

A retried delivery shows one row per attempt.

Permissions

Webhooks need the automation.automation_access feature, like the rest of workflow automation. See Permissions & Limits.