Skip to content

Send events to your own systems with webhooks

Send what happens in every satellite, such as a paid booking or a published page, to your own systems, n8n, Make or Zapier, from one place in Orbit.

How-to guide3 min read

A webhook sends events from your satellites to an address of yours as they happen. For example, Northwilds sends every paid Travel Orbit booking to its CRM, and every published page in CMS Orbit to a channel in Microsoft Teams through Make.

One webhook can take events from every satellite your organisation uses. Owners and admins set them up under Webhooks in the organisation.

Northwilds sends bookings to Make, reviews to Zapier and orders to n8n.

To act on events inside Bifröst Orbit instead, with conditions, approvals and notifications, use Orbit Flows.

Who can use webhooks

Webhooks come with a paid satellite plan. A satellite on trial or with free access counts too. How many webhooks can be on at once depends on the best plan your organisation has:

Starter
Webhooks on at once
5
Growth
Webhooks on at once
20
Enterprise
Webhooks on at once
No limit

When no satellite has a plan any more, nothing is sent and nothing is deleted. Choose a plan under Billing and sending starts again.

Add a webhook

  1. Open Organisations, choose your organisation, then Webhooks.
  2. Choose Add webhook.
  3. Give it a Name your team will recognise, such as Bookings to our CRM.
  4. Type the Address that should receive the events. It must be a public https:// address. Addresses on private or internal networks are refused.
  5. Under Events, tick Everything from a satellite, or open the list and tick single events, such as travel.booking.created.
  6. Tick Only from production to leave out events from staging. This matters for satellites with environments, such as CMS Orbit.
  7. Choose Add webhook.
Adding a webhook that sends bookings to a Make scenario.

Orbit then shows the signing secret once. Copy it and give it to whoever runs the receiving system: they use it to check that each message really came from Bifröst Orbit. See Webhooks from Orbit.

Make, Zapier and n8n

Each of these tools gives you an address to paste into Address. The guides show where to find it and how to check the signature there: Make, Zapier and n8n.

Check that it works

Choose ⋯ next to the webhook, then Send a test. Orbit sends a test message straight away and tells you whether it arrived. The test is sent even while the webhook is off.

Deliveries shows the last 100 messages from the past 30 days: which event, when, the answer from your system and how long it took. Choose Send again next to one that failed.

When your system is down

If your system doesn't answer with a 2xx status within 10 seconds, Orbit tries again: after a minute, then two, four and so on, for up to 24 hours. Nothing is lost while your system is briefly down.

If every delivery fails for 24 hours, Orbit switches the webhook off and emails the organisation's owners and admins. Fix the receiving system, then choose Switch on again. Events from while it was off are not sent again.

Change, pause or remove a webhook

  • Edit changes the name, address and events. Turn On off to pause it.
  • New signing secret makes a new secret and shows it once. Messages are signed with the new one straight away, so update your system at once. Messages that fail in the meantime are tried again.
  • Remove stops sending at once and deletes the webhook's delivery history.

Every change is in the organisation's audit trail, under Webhooks.

Webhooks in the satellites

Some satellites also have webhooks of their own, for one job:

  • CMS Orbit's website webhook refreshes your website when content changes. Keep using it for that. See Refresh the website when content changes.
  • Careers Orbit and Commerce Orbit have their own webhooks too. They keep working. Webhooks in Orbit send the same events in one shared format, from every satellite, so new set-ups can use Orbit's.

Was this page helpful?

Read next