Bricksta
Deutsch
Integration & Automation

Outbound webhooks: sending events to other tools

Where a trigger drives Bricksta from the outside, an outbound webhook works the other way: when something happens in a case, Bricksta sends the data to another system — for example Zapier, Make, n8n or your own backend. You find outbound webhooks in the menu under Automation → Outbound.

On this page

How an outbound webhook works

A webhook listens for an event in a case's lifecycle for a given template — created, started, completed, a task completed or a phase completed. When it occurs, Bricksta posts the related data as JSON to the configured target address. Because almost every tool accepts inbound webhooks, this one building block covers any number of target systems.

Creating a webhook

  1. 1
    Open Automation → Outbound.
  2. 2
    Give the webhook a name, choose the template and the event it should react to.
  3. 3
    Enter the target address (URL) of the receiving system. It must be publicly reachable — Bricksta rejects addresses that point into an internal network (such as localhost, 127.0.0.1, private ranges or a cloud metadata address).
  4. 4
    Optional: generate a secret — Bricksta creates the value itself and adds a signature to each send so the other side can verify authenticity. “generate” replaces an existing secret immediately; enter the new value at the receiver as well.
  5. 5
    Use “Test send” to check the connection before the webhook goes live.
The filled-in create form for a webhook: name “Onboarding an Zapier”, template picker “Mitarbeiter-Onboarding”, event picker and the target URL, with the “Add” button on the right.
The create form: enter name, template, event and target URL — then add.
The outbound page: at the top the create form with name, template picker, event picker (“case completed”) and target URL; below it the webhook “Onboarding an Zapier” with template, event and active status.
The outbound page: at the top the create form with event picker and target URL, below it the existing webhooks with template, event and status.

Every send is recorded with its HTTP status in the run log, so you can see whether the other side accepted it. Use the active switch to pause a webhook without deleting it.

If the other side does not answer, Bricksta aborts the send after ten seconds and records it as a failed attempt — a stalled target therefore does not hold up your other webhooks. A single failed send is not repeated: it stays in the run log with its error, and the following events continue as usual. Bricksta only retries when it could not process an event at all — and at most five times, after which it gives the event up. A target Bricksta already called for the same event is only called again during such a retry if that first call is in the run log with an error. If the log shows an entry without an HTTP status, Bricksta could not record the outcome of the first call — then it stays with that one call, so the other side does not receive the same event twice.

Managing outbound webhooks and seeing their secret requires the template-management right (template.manage). Members without this right see the webhooks, but not their secret.

All topics