Connection

What Is a Connection?

A Connection tells the platform that two parts of the Project should work together in a specific way. It is more than just drawing a line between two things. A proper Connection includes:

• Which two participants (Entities or Assets) are linked
• Which objects are allowed to flow
• Which direction the flow supports
• What configuration rules apply
• Whether the flow is one-way or two-way

Why Do Connections Matter?

Connections are how project structure becomes operational behavior. Without Connections, components may exist in the same Project but remain isolated. A Connection makes the relationship explicit. It answers questions such as:

• Can this Connector send invoices to that System?
• Should this Automation receive updates from that Connector?
• Is data allowed to flow in one direction or both?

Connection Directions

A Connection may be:

• Unidirectional: A → B (data flows one way)
• Bidirectional: A ↔ B (data flows both ways)

Different objects may support different directions inside the same broader relationship. For example, orders might flow from System A to System B, while payment confirmations flow back from B to A.

Real-World Example

A Booking Connector may connect to an Invoicing Connector. The Connection may allow:

• Completed jobs to flow from Booking to Invoicing
• Payment status to flow from Invoicing back to Booking

That is a Connection with defined object flows and direction rules.

Connection vs. Connector

This is a common question. The Connector is the active Asset — it does the integration work. The Connection is the configured relationship — it defines how participants exchange supported objects. Think of the Connector as the road, and the Connection as the traffic rules that say what may travel that road and in which direction.

What a Connection Is Not

A Connection is not automatically the same as a Connector. The Connector is the active Asset. The Connection is the configured relationship between participants that governs what flows where.