Skip to main content

​
Connector Step

A Connector step runs one operation of a connection you have already set up under Account, then Connections. It can call an operation the connection defines, look up the choices a connection offers, or run one step of a task sync: turn a tracker’s event into items, compare an item with its task, write an item to a task, or push a task to the tracker.
You do not need this step to keep a tracker and a Space in step. Connecting a tracker sets up the webhook, the mapping and the task subscription for you, and syncing runs with no flow. Use the step only to add your own logic around a sync, such as extra checks, notifications or a log.
The step is also offered as the connector group on a Quiva Endpoint step. Both run the same six operations.

​
Adding one

Add a Connector step from the Add Node panel. On the Connector tab, choose an operation, then fill in the fields it asks for. A JSON Editor button opens the whole payload as raw JSON. Changing the operation keeps only the fields the new operation also has, so check the payload after you switch.
The step runs with the flow run’s own identity, not yours. The sync operations are refused unless that identity has the admin, root or developer role.

​
The six operations

​
Fields

Give sync_push either task_id or event, not both. Every field accepts a $. path from an earlier step, so event is usually mapped from the trigger. List your bindings with GET /connector/bindings on your gateway to find a binding_id.

​
The result of a sync step

sync_apply and sync_push return the sync’s outcome and, for a skip, a reason. The full list is in Outcomes and reasons.

​
Pattern: signed webhook, normalise, fan out, apply

A tracker’s webhook can carry several changes in one delivery. Split it into items and apply each one in its own run.
The child flow must not use Static steps. The parallel runs share one static map, and concurrent writes to it can fail the run.
sync_apply is idempotent: it creates the task when none is linked and updates it otherwise, and an item already in step writes nothing. Putting sync_plan between steps 3 and 4 lets you gate on what would change.

​
Pattern: task trigger, push

Push a task to the tracker whenever it changes in a Space.
A flow-driven sync and the installed connection can run for the same binding. They converge, because applying and pushing are idempotent and items already in step write nothing. The tracker’s own webhook is registered once, by the connection.

​
Where to go next

Connect a tracker

The no-code way to set up a sync.

The sync block

Field rules, event normalisation, outcomes and reasons.

Webhook trigger

Receive and verify the tracker’s events.

Steps overview

How steps read and store data.