A work tracker is where a team's tasks already live: Asana, ClickUp, HubSpot, Jira or Trello. Here it means one of those reached through a connection your organization made — a token a member pasted once — rather than a copy of your work kept somewhere else.
One connection, two ways in
- A project room keeps its own tasks in step with one project, list or pipeline: a task made in the room appears in the tool, and a change made in the tool comes back.
- The API reaches the same connection directly: Asana at /asana/v1, ClickUp at /clickup/v1, HubSpot at /hubspot/v1 and Jira at /jira/v1, seven operations each, on the same key as the LinkedIn API.
The four are one API four times over. What differs is each tool's own word for the place tasks sit — Asana and Jira call it a project, ClickUp calls it a list, HubSpot calls it a pipeline — and all four name it project_id. A task is the same five fields whichever tool it came from: title, notes, status (open, doing or done), assignee and due.
Trello is a room's to link and has no API of its own here. Everything a room does with Trello it does through the same sync engine; it is the gate that is missing, not the tool.
Questions people ask
Where does the token go?
On the rooms page, signed in, under the room's task tools. It never goes through the API: POST /asana/v1/connections/link and the other three answer 403 with the address of that page, because a secret does not belong in an API call an assistant is holding.
Can I reach somebody else's connection?
No. A connection belongs to one organization, and one that is another's is answered exactly as one that does not exist — 404, never 403, and the same words either way, so an id cannot be probed. A project id is looked up in the tool on every call rather than trusted.
Whose name is on the work?
The member whose token the connection is. A task made through the API is made by them in the tool, as it would be if they had typed it there.