Platform
Automate work across your satellites with Orbit Flows
Orbit Flows acts when something happens in any satellite, with no code. Here is how a flow is built, what its steps can do and how it works with Make, Zapier and n8n, using one big booking as the example.
5 min read
On this page
A lot of work starts with something that has already happened. A booking is paid, a page is published, a one-star review comes in, a candidate is hired. Someone has to notice, check whether it matters and tell the right people. Often that someone is a person refreshing a list.
Orbit Flows does that part for you. Every satellite announces what happens through Orbit Exchange, and a flow acts on it: it checks what matters, asks a person when a decision is needed and passes the result on. No code, and no extra tool unless you want one.
Three parts: When, Only if, Then
Owners and admins make flows under Flows in the organisation in Orbit. Each flow has three parts:
- When: What starts it. An event in any satellite, such as
presence.review.received, a schedule every day or every week, or someone choosing Run now. - Only if: Conditions that must be true, such as a booking total over 2,000 or a review under three stars. Leave them empty to run every time.
- Then: The steps, from top to bottom, with branches where a flow needs them.
Templates that already work are there to start from, such as Answer bad reviews with care, Follow up no-shows and Big bookings to the team.
What a step can do
- Notify people: A notification in Orbit's bell to owners, admins, everyone or people you pick by name, with an email too if you tick it. Flows only ever notify people in your organisation.
- Ask for approval: Someone approves or declines, with a note if they like. The steps under If approved or If declined run next, and you choose how long to wait and what happens if nobody answers in time.
- Write with AI: A short text from your instructions, such as a reply to a review or a summary of a booking, for later steps to use.
- Do something in a satellite: Create a draft page in CMS Orbit, add a note to a Travel Orbit booking or move a Careers Orbit application to another stage.
- Wait: Pause for minutes, hours or days, up to 30 days.
- Send to a webhook: Post to a Slack or Microsoft Teams channel, or send JSON to Make, Zapier, n8n or your own system.
- If / otherwise: Check conditions in the middle of a flow and take one path or the other.
Any title or message can include fields from the event in double curly brackets, so New booking {{event.data.reference}} for {{event.data.travellers}} travellers becomes 'New booking NW-7ERJDH for 2 travellers'.
An example: a big booking for Northwilds
Northwilds wants a person to look at every large trip booking before it goes into the CRM. The flow reads like the sentence you would use to explain it:
- When: A Travel Orbit trip booking is paid.
- Only if: The booking total is over €2,000.
- Ask for approval: The people Northwilds picks get a notification and an email with a link, and approve or decline.
- If approved: A Send to a webhook step sends the booking as JSON to n8n, which adds it to the CRM, and a second one posts it to the team's channel in Teams.
- If declined: Notify people tells the trip lead, in Orbit and by email.
Before switching it on, choose Test the flow with a recent booking. Orbit shows what each step would do, such as who it would notify and with what text, without doing any of it. If the conditions don't match the event, it says so.
Make, Zapier and n8n
Orbit Flows works with the automation tools you may already use. There are two ways to hand an event over:
- A webhook: Under Webhooks, send every event you choose, signed so the tool can check it came from Bifröst Orbit. Use it when the other tool should decide what to do. If the tool is down, Orbit tries again for up to 24 hours.
- A flow step: Send to a webhook with JSON for your own system sends only when the flow's conditions are true, after an approval or an AI step if you want one, and includes what earlier steps did. These messages are not signed, so keep the address to yourself.
The big booking example uses a flow step, because Orbit filters and asks first. In n8n, a Webhook node receives it, and the booking reference is in {{ $json.body.event.data.reference }}. Over 90 kinds of event are listed field by field in the event reference.
Safe to hand to your team
- Never more than its owner: A flow acts as the person who saved it last, with exactly their access, and stops if they leave or lose access.
- Nothing destructive: Actions that delete or erase are never offered, and a flow that starts more than 30 times in a minute is stopped.
- Every run on record: See runs lists every run from the past 30 days, with each step's result. A step that fails is tried again after a minute and after five minutes.
- In the audit trail: Every change to a flow, and every Run now, is recorded under Flows.
- Private networks refused: Webhooks and flows only send to public
https://addresses. - AI in the EU: Write with AI goes through OpenRouter in the EU, to AI providers that keep no data and don't train on it.
Plans
Flows come with any paid satellite plan, and a satellite on trial or with free access counts too. The best plan your organisation has sets the limits: 10 flows on at once and 5,000 runs a month on Starter, 50 flows and 50,000 runs on Growth, and no limit on Enterprise. Write with AI steps need Growth or higher. See pricing for the satellite plans.
Get started
See Orbit Flows for the editor, approvals and templates. The docs walk through every step: Automate work with Orbit Flows, webhooks, and the guides for Make, Zapier and n8n.
Read next
Ask for reviews after every booking, live products, trips and jobs on your pages and why Orbit is free.