This is different from an API integration, which is a set of credentials you hand to your own client to read and write tasks. Connecting a tracker creates and manages an integration for you, and you never see its secret. If you want to build the sync yourself, use task sync with an integration. To add your own steps around a connected tracker, see the Connector step.
Connect a tracker
Click Connect on the tracker’s card. The wizard shows the steps for that tracker. The exact steps and help text come from the tracker’s own setup, but they follow the same shape.1
Token
Paste the tracker’s API token. The tracker’s help text tells you where to get it. Create a dedicated member in the tracker for the connection and generate the token as that member, so the connection’s writes are attributed to it and your own edits are never mistaken for echoes. Click Test connection to check the token before you go on.
2
Space
Choose the Space to keep in step. A connection covers one Space.
3
Choices
Pick what to sync, such as the workflow or project, and an optional team to narrow it further. Only items in that scope sync.
4
Status map
Map each state in the tracker to one of your Space’s statuses. Each status role then maps back to one tracker state, so a task moved on either side lands somewhere sensible. Every state needs a status, and the Space needs a status for each role the sync uses.
5
Owners
Owners are matched by email. A member with no match stays unmapped and their ownership is not synced.
6
Priority and estimate
Priority is matched by name, and the tracker’s estimate becomes a time estimate using the conversion the step asks for. If the tracker has no priority field to match, priority is not synced.
7
Connect
Review the summary and click Connect. Everything is set up in one go: an integration for the sync, the tracker’s webhook, and a task subscription.
The first connection on an account can take up to five minutes while your gateway is prepared. Keep the wizard open. If it takes longer, close it and check the card in a few minutes.
The connection card
A connected tracker shows a card with a status pill:
The card shows the workspace and member the connection acts as, and the Space it syncs.
Activity
A refused call is not a failed sync. The call was rejected before anything ran, so the tracker was not changed. If your tracker’s changes are not arriving and the count keeps going up, try Repair.
Logs and actions
Repair
Use Repair when the card says Needs repair, or when changes stop flowing and Test connection passes. It is safe to run at any time: each setup step first checks whether it is already done and only redoes what is missing, such as a webhook someone deleted in the tracker.Disconnect
Disconnect stops syncing and removes the tracker’s webhook, the task subscription and the integration. Tasks and items already synced are kept on both sides, and the API token stays saved. If the disconnect does not finish, the card says Disconnect incomplete and the button becomes Retry disconnect.Reinstall needed
A connection made before the sync engine was introduced was built from flows and cannot be repaired or upgraded. The card says Reinstall needed. Click Disconnect, then connect again. Tasks and items already synced are kept on both sides.The new connection does not use flows. Any sync flows an older connection created are no longer needed once you disconnect it.
Where to go next
Task sync
Build your own sync with the API, or compare with the no-code option.
Connector step
Add your own steps around a sync.
API integrations
Credentials for your own client.
Author a tracker definition
Teach the platform a new tracker.