Skip to main content
Webhooks let your project notify another service when something happens. You can react to entry changes, form submissions, publishing, agent work, analytics reports, and media changes without building an automation system inside Fimo.
Only project members with Full Access can view or manage webhooks.

Add a destination

Open Project settings, choose Webhooks, and add a webhook. Pick the event, enter the destination URL, then choose whether to send the complete Fimo event or a custom JSON request. Each project can have up to 20 webhooks. A webhook listens to main by default or can include every environment. When Studio recognizes a supported destination, it offers to prepare the expected request for you. Nothing changes until you accept the suggestion, and you can edit every field afterward. For entry changes, Combine rapid changes controls how direct edits are delivered. The 5-second default waits for editing to stop, then sends one delivery with the combined changes. Choose immediate, 30 seconds, or 1 minute when the destination needs a different balance between latency and request volume. Bulk edits and environment merges are already batched and always send immediately.

Shape the request

The complete event envelope is the safest default. It includes the event type, project, environment, timestamp, and event-specific data. Use the custom payload editor when a service expects a smaller or differently shaped JSON request. The variable browser shows what is available for the selected event and previews the resulting payload with example data.

Authenticate with the destination

Add destination headers for API tokens or provider-specific values. A header can use a fixed value or reference an existing project secret as a raw, Bearer, or token credential. Secret values stay hidden in Studio and in delivery history. Fimo also signs requests by default so your endpoint can verify that the payload came from Fimo. Save the signing secret shown when the webhook is created. See Verify signed requests for a complete receiver example.

Follow every delivery

Open a webhook to see recent deliveries and their status. Each delivery shows the stable event ID, masked destination, request metadata and payload excerpt, queue message ID, attempts, response status, duration, and a short response excerpt when one is safe to display. The webhook list shows the latest delivery for each webhook. Fimo automatically retries temporary failures. After those retries are exhausted, choose Retry now to start a new delivery attempt. A delivery can be retried manually up to five times. Request and response details remain available for 7 days; delivery status and timing remain available for 30 days.
Use the test action before enabling a production workflow. It sends the selected event’s documented example payload through the same delivery path and marks the request with X-Fimo-Test: true.

Forms

Manage the content and forms that can produce webhook events.

Publishing

Understand the publish states available to webhook destinations.