---
title: "Connect a project to a project tool"
description: "Hand each new task of a project over to Trello, Asana, Jira or Basecamp: one tool per project, what is created, and when a task is marked done"
category: integrations
section: native-integrations
type: Reference
lastUpdated: 2026-09-30
locale: en
canonical: https://support.talkspirit.com/en/integrations/connect-a-project-to-a-project-tool
---

# Connect a project to a project tool


> **In summary:** open the project’s settings, then the **Integrations** tab, and connect **one** project tool: Trello, Asana, Jira or Basecamp. Each new task created on the project is then created in that tool, once. When the tool confirms, Talkspirit marks the task done, adds an **Open in** link to what was created, and makes the task read-only. A project holds one project tool at a time: to switch, disconnect the first.

A project tool integration hands work over. The project stays where tasks are raised; the team that does the work tracks it in its own tool. Nothing flows back from the tool: later changes on either side stay on that side.

This guide covers what is common to the four tools. Each tool has its own page for its consent screen, its destination and what it receives: see **What’s next?**.

## What each tool receives

One task created on the project becomes one item in the tool. The item differs per tool, because each tool has its own unit of work.

| Tool | What is created | Where | Assignees | Due date |
| --- | --- | --- | --- | --- |
| **Trello** | A card | In a list of a Trello board | Added as card members | Not sent |
| **Asana** | A project | In a team of a workspace | Added as project members | Not sent |
| **Jira** | An issue | In a Jira project, with the issue type you chose | One assignee | Sent |
| **Basecamp** | A to-do list | In the To-dos of a Basecamp project | Not sent | Not sent |

Every item carries the task's title as its name and the task's description as its description. The item does not link back to the Talkspirit task.

Asana and Jira match assignees by **email address**: a person whose account in the tool uses a different address is not assigned. Trello matches them by **name**: see [Connect a project to Trello](/integrations/connect-a-project-to-trello). Only members are sent: a role or a circle assigned to the task is not.

## One project tool per project

A project holds one project tool at a time. Each task can be handed to one place only, so two tools on one project would leave open which of them gets the next task.

While one tool is connected, the **Connect** button of the three others is unavailable, and its tooltip names the tool to disconnect first. If you try anyway, Talkspirit refuses with: *This project is already connected to Trello. Disconnect it before connecting another project tool.* The connected tool is left untouched.

A connection counts as soon as the consent is given, even before a destination is chosen. Only **Disconnect** frees the project.

Notification tools are not project tools. Slack, Microsoft Teams, Talkspirit and the webhook live on the project's **Notifications** tab, several can be connected at once, and none of them counts toward this rule: a project can hold them and one project tool at the same time.

## Before you start

- You are an **owner or editor** of the project. The **Integrations** tab only appears for these two.
- You have an account in the project tool that can create items where you want them to land. Talkspirit creates every item with the account that approved the connection.

## Connect a project

1. Open the project’s settings, then the **Integrations** tab.
2. On the card of your tool, select **Connect**.
3. The tool shows its own consent screen. Sign in if asked, and approve.
4. You return to the project. The card now reads **Choose a destination** and shows the destination picker.
5. Choose each level, from the outermost to the innermost, then select **Confirm destination**.

The card reads **Connected** and names the destination, for example *New tasks go to Marketing → To do*. Tasks created from now on are sent there.

There is no **Test** button for a project tool: a test would create a real item in your tool.

## Which tasks are sent

A task is sent when it is **created** on a connected project that has a destination. Nothing else is sent, and only top-level tasks are sent.

| Not sent | Why |
| --- | --- |
| Changes to a task, and deleted tasks | The tool received one item when the task was created, and nothing after that. |
| A subtask | A subtask is part of its parent's work: only the parent is sent. |
| Tasks created before the connection, or before a destination was chosen | Only tasks created from then on are sent. |

A private task, and every task of a private or secret project, is sent like any other. The notification tools on the **Notifications** tab never receive them.

## The hand-off

Once the tool confirms that the item exists, Talkspirit:

- marks the task **done**, and moves it to the project's column for completed tasks when the project has one. On a project without such a column, the task stays in its column;
- shows at the top of the task *This task continues in Trello.* (with the name of your tool) and an **Open in Trello** link to the item it created.

The task then becomes read-only in Talkspirit. Its title, description, fields and files can no longer be edited, comments can no longer be added, and it can no longer be completed, moved or archived. It cannot be reopened either, not even from the project’s list view: unticking it, or dragging it into a column that would reopen it, is refused. Its subtasks and its progress stay editable.

The task is marked only once the tool has confirmed. Until then it stays where it was created, so a task never reads as done while its item does not exist.

**A human edit wins.** If someone changes the task's status, moves it to another column or archives it before the tool confirms, Talkspirit adds the link but does not move the task.

If the tool refuses the item, the task stays where it was created, as if the project had no integration. It is not sent again.

The project's activity feed does not record the hand-off.

## Change, reconnect or disconnect

| Control | What it does |
| --- | --- |
| **Change destination** | Opens the picker again. The connection is kept; no new consent is needed. |
| **Reconnect** | Runs the tool's consent again. The destination is kept. Use it when the tool no longer accepts the connection. |
| **Disconnect** | Stops sending anything from this project and deletes the destination. Items already created in the tool stay there. |

## When tasks are not handed over

When sending stops, the card reads **Interrupted** instead of **Connected**, and an alert titled **Sending was interrupted** says why and what to do. The alert names your tool; the examples below use Trello.

| The alert says | What it means | What to do |
| --- | --- | --- |
| *5 deliveries failed in a row.* | The tool refused five tasks in a row, so sending stopped for this project | Select **Change destination** and choose the destination again, or **Disconnect** the tool and connect it again |
| *Access to Trello was withdrawn.* | The authorisation was withdrawn in the tool | **Disconnect** the tool and connect it again. **Change destination** is not offered |
| *Trello refused our own credentials.* | A fault on Talkspirit's side, not in your configuration | Nothing you change on the card fixes it. Contact Talkspirit support |

Tasks created while sending was interrupted are not sent later.

Two situations do not interrupt sending:

| What you see | Likely cause | What to do |
| --- | --- | --- |
| One task was not marked done, the next ones were | The tool was busy and refused that one request | Create the item in the tool by hand. The following tasks are not affected |
| The card reads **Choose a destination** | The consent was given but no destination was confirmed | Choose one, then **Confirm destination** |

## FAQ

**Can a project send its tasks to two tools?**
No. One project tool per project. Disconnect the first to connect another.

**Does an edit in Talkspirit update the item in the tool?**
No. The tool receives the task once, when it is created.

**Does closing the item in the tool change the task in Talkspirit?**
No. Nothing comes back from the tool.

**Why is a task marked done when nobody finished it?**
It was handed over: the work continues in the tool. The **Open in** link at the top of the task is what tells a handed-over task apart from one a person completed.

**Who can connect a project?**
An owner or editor of the project, with an account in the tool that can create items at the chosen destination.

**Does disconnecting delete anything?**
It deletes the connection and the destination. Tasks in Talkspirit and items in the tool are untouched.

## What’s next?

- [Connect a project to Trello](/integrations/connect-a-project-to-trello): the Trello authorisation, choosing the board and the list, and what a card carries.
- [Connect a project to Asana](/integrations/connect-a-project-to-asana): choosing the workspace and the team, and how assignees become project members.
- [Connect a project to Jira](/integrations/connect-a-project-to-jira): choosing the site, the Jira project and the issue type, the assignee and the due date.
- [Connect a project to Basecamp](/integrations/connect-a-project-to-basecamp): choosing the account and the Basecamp project, and the To-dos tool.
- [Circle and project integrations](/integrations/circle-and-project-integrations-overview): the chat tools a circle or a project can notify.