# Automate work with Orbit Flows

> Build flows in Orbit Flows that act when something happens in any satellite, on a schedule or by hand: check conditions, notify people, ask for approval, write with AI, wait, branch, do things in the satellites and post to Slack, Teams or your own system.

Source: https://docs.bifrostorbit.com/orbit/admins/flows/

Orbit Flows does work for you when something happens in your satellites, with no code. Each automation is a flow. For example, Northwilds tells the trip lead in Orbit and in Microsoft Teams whenever a Travel Orbit booking over €2,000 is paid, and posts every one-star Presence Orbit review to the support channel.

Each flow has three parts:

- **When:** what starts it. An event in any satellite, a schedule, or someone choosing **Run now**.
- **Only if:** conditions that must be true, such as a booking total over 2,000. Leave them empty to run every time.
- **Then:** the steps, from top to bottom.

Owners and admins make and change flows under **Flows** in the organisation.

## Who can use flows

Flows come with a paid satellite plan. A satellite on trial or with free access counts too. The best plan your organisation has sets the limits:

| Plan | Flows on at once | Runs a month |
| --- | --- | --- |
| Starter | 10 | 5,000 |
| Growth | 50 | 50,000 |
| Enterprise | No limit | No limit |

A run is one time a flow starts and its conditions are true. A flow that starts more than 30 times in a minute is stopped, in case it is starting itself, for example by changing what it waits for; saving it starts it again. When the month's runs are used up, flows stop until the next month or until you choose a bigger plan, and the list says so. Nothing is deleted.

## Make a flow

1. Open **Organisations**, choose your organisation, then **Flows**, and choose **New flow**. Pick a template to start from, such as **Answer bad reviews with care** or **Follow up no-shows**, or start from scratch.
2. Give it a **Name**, such as Tell the team about big bookings.
3. Under **When**, choose:
   - **An event happens**, then tick the events, such as `travel.booking.created`, or **Everything from** a satellite. Tick **Only from production** to leave out events from staging in CMS Orbit.
   - **On a schedule**, then every day or every week, the time and the time zone.
   - **Only when run by hand**, for flows you start yourself.
4. Under **Only if**, choose **Add a condition** for each check. Pick a field, such as `event.data.total`, from the list, or type one, then a comparison and a value. The list offers the fields the chosen events have. With more than one condition, choose whether all or any must be true.
5. Under **Then**, add steps with **Add a step**. Each can be moved up or down or removed.
6. Choose **Save flow**.

## Steps

- **Notify people** sends a notification in Orbit's bell to owners, admins, everyone in the organisation or people you pick by name, with a title and a message. Tick **Also send an email** to email them too. Flows only ever notify people in your organisation.
- **Wait** pauses the flow for minutes, hours or days, up to 30 days, then carries on.
- **Post to Slack** and **Post to Microsoft Teams** post a message, and a link if you add one, in the channel your organisation connected under [Connections](https://docs.bifrostorbit.com/orbit/admins/connections/). For example, the message `Published: {{event.data.name}}` with the link `{{event.data.url}}`. Connect Slack or Teams first; until then the step says so and a run stops there with the reason. These steps need Growth or higher.
- **Send to a webhook** posts a message to an address:
  - **Slack** and **Microsoft Teams**: paste the address of an incoming webhook from the channel's settings. The message is posted as it is. To post with your organisation's connection instead, use **Post to Slack** or **Post to Microsoft Teams**.
  - **JSON for your own system**: sends the flow, the run, the whole event, the earlier steps and the message. These requests are not signed; for signed messages to your own systems, use [webhooks](https://docs.bifrostorbit.com/orbit/admins/webhooks/).
  - Addresses on private or internal networks are refused.
- **Do something in a satellite** uses one of the satellite's actions, the same ones AI assistants use over MCP. For example, create a draft page in CMS Orbit, add a note to a Travel Orbit booking, or move a Careers Orbit application to another stage.
  1. Choose the satellite. For CMS Orbit, Commerce Orbit and Travel Orbit, also say which website, shop or brand the flow works in. It is filled in from the event, such as `{{event.tenant.spaceId}}` for CMS Orbit, so it is usually right already; for a schedule or a flow run by hand, paste the id from the satellite instead.
  2. Choose **Choose an action** and pick one. Actions that only read say so; actions that delete or erase are never offered.
  3. Fill in its fields. Any field can use details from the event or an earlier step.

  The action runs as the flow's owner, the person who saved the flow last, with exactly their access in that satellite. If they leave the organisation or lose access, the step fails and says why. What it does shows in the satellite's own history and audit log as the flow, for its owner. What the action returns can be used by later steps, as `{{steps.<step id>.<field>}}`.
- **Write with AI** writes a short text from your instructions, such as a reply to a review or a summary of a booking, which later steps can use as `{{steps.<step id>.text}}`. Choose short, medium or long. Instructions can include details from the event. It needs the Growth plan or higher. The text is written through OpenRouter in the EU by AI providers that keep no data and don't train on it; don't put anything into the instructions that the provider shouldn't see.
- **Ask for approval** asks owners, admins, everyone or people you pick to approve or decline, then carries on with the steps under **If approved** or **If declined**. They get a notification and an email with a link, and can add a note. Choose how long to wait and what happens if nobody answers in time: approve or decline. The flows page lists approvals that are still waiting.
- **If / otherwise** checks conditions in the middle of a flow and runs one list of steps when they are true and another when they aren't. Each list can hold any steps, including another **If / otherwise**.

## Put details into the text

Any title or message can include fields from the event in double curly brackets. For example, `New booking {{event.data.reference}} for {{event.data.travellers}} travellers` becomes "New booking NW-7ERJDH for 2 travellers". The fields each event has are in [Webhooks from Orbit](https://docs.bifrostorbit.com/orbit/developers/orbit-webhooks/). A later step can use what an earlier one did, as `{{steps.<step id>.title}}`.

## Test before you switch it on

Under **Test**, choose a recent event of the kind the flow waits for, or test without one, then choose **Test the flow**. Orbit shows what each step would do, such as who it would notify and with what text, without doing anything. If the conditions don't match the event, it says so.

## Follow the runs

**See runs** on a flow lists every run from the past 30 days, with what started it: an event, the schedule or **Run now**. Open one to see each step: done, waiting, failed or skipped, with the reason when one failed. A waiting run says when it carries on, and **Cancel this run** stops it.

A step that fails, such as a webhook address or a satellite that doesn't answer, is tried again after a minute and then after five minutes. If it fails a third time, the run stops there.

## Use Make, Zapier or 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**, sends 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.
- **Send to a webhook** in a flow, 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.

Step-by-step guides: [Make](https://docs.bifrostorbit.com/orbit/admins/flows-make/), [Zapier](https://docs.bifrostorbit.com/orbit/admins/flows-zapier/) and [n8n](https://docs.bifrostorbit.com/orbit/admins/flows-n8n/).

## Change, turn off or remove a flow

- Open a flow to change it. Runs already under way finish the way the flow was when they started.
- **Turn off** in the flow's menu stops new runs; runs under way carry on. **Turn on** starts it again.
- **Run now** starts a flow straight away, whatever its trigger.
- **Remove** stops the flow at once and cancels runs under way.

Every change, and every **Run now**, is in the organisation's [audit trail](https://docs.bifrostorbit.com/orbit/admins/audit-trail/), under **Flows**.
