Skip to main content
If your services team runs in Kantata (formerly Mavenlink) and your activation work runs in Thread, the gap between “deal closed” and “project staffed” is where weeks get lost. Connecting Kantata closes it: agents can stand up the project, apply your project template, add resources, and keep the delivery record linked to the account — with every state-changing step riding your approval settings.

​
What you can build

Project creation on close

A workflow or Motion play stands up the Kantata workspace the moment the deal closes — template applied, dates set, lead assigned.

Role-based resourcing

Agents read skills, availability, and capacity, then add resources and allocations by role — not by who replied first to a Slack message.

Delivery visibility

Agents read workspaces, stories, and time entries so onboarding status reflects what delivery is actually doing.

Linked records

Projects link back to the account and its CRM opportunity, so finance and delivery share one ID.

​
Connect Kantata

1

Get a Kantata API token

In Kantata, create an API (OAuth) token for the account Thread should act as. Kantata tokens don’t expire, so treat the value like a password.
2

Paste it in Thread

Go to Connectors → Kantata, paste the token, and connect. The token is stored encrypted. One Kantata account per Thread organization.
3

Test the connection

Use the connection test on the connector page to confirm reads work end to end.

​
What agents can do

Reads: workspaces (projects) and their detail, stories (tasks/milestones), users, skills and skill memberships, project templates and their assignments, resource assignments and allocations, user capacity, time entries, custom fields, and external links. Writes (approval-gated): Like every state-changing action an agent takes, these follow per-action autonomy — anything not opted out of approval lands in your Inbox first.

​
Tips from the field

One template per segment

Enterprise vs SMB usually need different role mixes. Branch by ARR and pick the template up front.

Map roles, not people

Role-based allocations survive team changes. Hardcoded names don’t.

Link to the opportunity

The external link on the Kantata workspace keeps finance and delivery on one ID.

Notify the PM

Add a Slack or email step right after project creation so the PM isn’t surprised.

​
Troubleshooting

Confirm the token was copied whole and belongs to a user with API access. Reconnecting with a fresh token replaces the old one.
Template role placeholders only fill when resources are added — check that the resourcing step ran, and that the roles in the template match what the agent was asked to staff.
Disconnecting stops new Kantata activity but doesn’t affect existing Kantata projects. Reconnect anytime with a new token.

​
Next steps

Salesforce

The most common upstream trigger for Kantata project creation.

Motion agents

Where Kantata tools show up in agent runs and approvals.