Orbit Flows and Orbit Exchange
When something happens, the right thing follows.
Every satellite announces what happens: a booking paid, a page published, a one-star review, a candidate hired. Orbit Exchange carries it. Orbit Flows acts on it, with no code: tell the right people, ask for approval, write a reply with AI, or hand it to Make, Zapier, n8n and your own systems.
The flows Northwilds uses, under Flows in its organisation in Orbit. A reply to a 2-star review is waiting for someone to approve it.
- Approvals waiting for an answer
- What starts each flow
- When it last ran
Orbit Flows
Build a flow the way you would explain it
A flow has three parts. When says what starts it: an event in any satellite, a time of day or someone choosing Run now. Only if checks what matters, such as a booking over 2,000 or a review under three stars. Then lists the steps, top to bottom, with branches for approved and declined.
Here, a review under three stars in Presence Orbit gets a reply written with AI, and an owner or admin approves it before anyone posts it. Test a flow against a real recent event before you switch it on. Orbit shows what each step would do, without doing it.
- Only if, then step by step
- A reply written with AI
Orbit Flows and Orbit Exchange
Every satellite, one set of events
90+
kinds of event
From travel.booking.created to presence.review.received, each listed field by field in the event reference.
0
lines of code
A flow is When, Only if and Then, and templates that already work are there to start from.
24 h
of retries
If Make, Zapier, n8n or your own system is down, Orbit keeps trying for a day.
30 days
of runs on record
Every step's result, and every webhook delivery, ready to check or send again.
Steps
Everything a flow can do
Approvals
A person says yes before the flow carries on
An Ask for approval step asks owners, admins, everyone or people you pick. They get a notification and an email with a link, read what the flow wants to do and approve or decline, with a note if they like.
- Two paths: the steps under If approved or If declined run next, such as telling the team to post the reply.
- Nobody answers? Choose how long to wait and whether the flow approves or declines by itself when the time runs out.
- Nothing forgotten: the flows page lists every approval still waiting.
- Who can decide, and by when
- Approve or decline, with a note
Orbit Exchange
Every event, from every satellite, in one shape
Orbit Exchange is the bridge between your satellites. When something changes, the satellite announces it as an event with a fixed, versioned shape, so the other satellites, your flows and your own systems can all act on it, without the products being wired to each other.
Over 90 kinds of event, from travel.booking.created to presence.review.received, are listed field by field in the event reference.
Make, Zapier and n8n
Use the automation tools you already know
Add a webhook under Webhooks in Orbit and point it at Make, Zapier, n8n or your own code. Choose the events, such as every paid booking or every new order, and Orbit sends each one as it happens, signed so the receiver can check it came from you.
If a tool is down, Orbit tries again for 24 hours. A delivery log shows the last 30 days, and anything that failed can be sent again.
In three steps
Connect Make, Zapier or n8n
Step-by-step guides
Set it up in your tool, with screenshots
Each guide shows where to find the address, whether to use a webhook or a flow step, which fields to map and how to check the signature in that tool.
Templates
Start from a flow that already works
Safe by design
Automation you can hand to your team
Questions
About Orbit Flows
Which plans include Orbit Flows?
Flows come with any paid satellite plan, and a satellite on trial 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.
Do we still need Make, Zapier or n8n?
Not for work inside Bifröst Orbit: flows notify people, ask for approval, write with AI, wait and act in the satellites without another tool. When your other systems should decide, send events to Make, Zapier, n8n or your own code with a signed webhook, or from a flow step.
Can a flow do more than the person who made it?
No. A flow acts as its owner, the person who saved it last, with exactly their access, and stops if they leave or lose access. Flows can't delete or erase anything in a satellite, and every change to a flow and every Run now is in the audit trail.
Let your tools work together.
Flows and webhooks come with every paid satellite plan, including the 14-day trial.