Skip to main content

Bit connections

A bit connection links one step to a possible next step. Connections are what turn separate bits into a process: a flow is its starting bit and every bit you can reach from it by following connections. A step with one connection simply continues; a step with several is a decision point, where whoever runs the flow chooses the path.

How connections work​

  • A connection lives in the source bit. It appears in the bit's content as a next-step card, with a Continue button that moves the run to the connected bit.
  • Connections belong to the bit, not to one flow. Because a flow is everything reachable from its starting bit, a bit's connections are the same in every flow that includes it. Adding or removing a connection changes every flow that uses that bit.
  • Loops are allowed. A connection can lead back to an earlier step, for example to redo a check, and two connections may lead to the same bit.

Making a connection​

  1. In the bit editor, place the cursor where the card should go and choose Connect in the toolbar, or type a slash and choose Connect.
  2. In Add Connection, either:
    • Search Existing bits, pick one, choose which of its details to show on the card, and choose Add; or
    • Create New: give the new bit a title and, optionally, a description, abstract and categories, and choose Create Bit. The new bit is created and connected in one step.

The card is inserted where your cursor was.

Connection settings​

Select a connection card and open its properties:

  • Label. A short name for the path, such as "Approved" or "Escalate". At a decision point, labels are how whoever runs the flow tells the paths apart, so name each one by the situation it is for.
  • Display options. What the card shows: Content Preview (a preview of the next step, opened in place; on by default), the next bit's Description, Categories and Time to Read.
  • Availability. Whether the connection can always be taken, or only after a certain answer. See below.

Put the reasoning for each path in the step's own content as well ("If the customer is eligible, continue to approval; otherwise, escalate"), so the choice is clear at the moment it is made.

Conditional connections​

By default a connection is Always enabled. Choose Enabled only when to make it depend on an answer given in the same step:

  • Pick the element the condition reads. Radio buttons, dropdowns and checklist items can control a connection.
  • For radio buttons or a dropdown, tick the accepted options. The connection opens when any one of them is chosen.
  • For a checklist item, choose whether it must be checked or unchecked.

Each connection has one condition, based on one element. To combine conditions, give each path its own connection with its own condition, or split the decision across two steps.

While running the flow:

  • A connection whose condition is not met stays visible but cannot be taken, and shows what it needs, for example "Available when Eligibility is Yes". Its preview still works.
  • Until the controlling question is answered, the step asks for it: "Answer Eligibility to continue."
  • If the answer given matches no connection, Floxar says so and suggests changing the answer, or pausing or transferring the trail and telling an editor that the step needs a path for that answer.

While editing: Floxar checks the step's conditions and lists problems above the content, such as an answer that would leave no way forward, or a condition that accepts every option and so only waits for an answer. Selecting a problem takes you to the element concerned. Deleting an element that conditions depend on asks you to confirm, because those connections would no longer work.

Required answers come first​

Marking an element as required holds every connection on the step, conditional or not, until that element is answered. Only then do the conditions decide which connections are open. So a step with a required text field and a conditional choice needs both: the text answered, and a choice that opens a path. See Required elements.

The last step and the start of a flow​

  • A bit with no connections ends the flow. Whoever runs it sees that it is the last step and can complete the trail.
  • A flow starts at its starting bit, chosen in the flow's settings. See Building flows.

Seeing what leads to a bit​

A bit's page has a Bits that lead here section listing every bit that connects to it, across all flows. Check it before changing or archiving a bit that others lead to.

Removing a connection​

Delete the card from the source bit's content. Since connections belong to the bit, the path disappears from every flow that uses it. If the bit a connection leads to is archived, the card shows as a broken connection, and the source bit cannot be saved until you delete the card.

AI agents and connections​

An AI agent running a flow sees each connection's label and the step it leads to, and chooses the path the way a person does, from the step's content and the answers given. Required answers hold an agent exactly as they hold a person. Conditions on connections guide people in the app but do not bind an agent, so when a path must never be taken without a certain answer, also say so in the step's content.

Last reviewed: 2026-10-06