---
title: "Circle and project integrations: activity in your chat tool"
description: "How a circle or a project sends its activity to a chat channel: one connection per circle, four notification families, the project’s Tasks family, and how to spot a silent failure"
category: integrations
section: native-integrations
type: Reference
lastUpdated: 2026-09-30
locale: en
canonical: https://support.talkspirit.com/en/integrations/circle-and-project-integrations-overview
---

# Circle and project integrations: activity in your chat tool


> **In summary:** each circle connects to its own chat channel from the circle’s settings, under **Integrations**. Nothing is sent until an administrator connects one. Four families of notifications are on by default, and each can be switched off. The card shows whether messages are actually arriving, not only whether the connection exists.

A circle integration sends that circle's governance activity to a channel in your chat tool, so members read a new role or a published policy where they already work, without opening Talkspirit.

## One connection per circle

The connection belongs to the circle, not to your organisation. A circle with no connection produces nothing at all: no message, no call to the chat tool.

This makes the rollout self-gating. The feature reaches a team only when an administrator of that circle turns it on, one circle at a time. Two circles can post to the same channel if you want their activity read together.

Each circle keeps its own event settings, so a circle that only wants goals can switch the other three families off without affecting anyone else.

## What gets sent

Four families, all on by default. The labels below are the ones on the card.

| Family | What it covers | Messages |
| --- | --- | --- |
| **Governance** | A role or circle created, updated, deleted, or turned from one into the other. A policy published, updated or deleted. A proposal submitted, adopted, rejected or withdrawn. A tension raised or closed. | 19 |
| **Assignments** | A member assigned to a role or circle, or removed from one. Elections name the role and the date the term runs to. | 2 |
| **Goals** | A goal owned by this circle created or updated. Metrics and checklists owned by this circle, created or updated. | 7 |
| **Meetings** | A governance meeting that has finished, and a meeting about to start. | 2 |

A goal owned by a person or a role posts nothing: there is no circle, so there is no channel to send it to. Private goals post nothing either, because the channel is not scoped to the goal's access rules.

## Turning one on

Open the circle’s settings, then the **Integrations** tab, and use the card for your chat tool. The steps differ per tool because the consent screen belongs to the tool, not to Talkspirit: see [Connect a circle or a project to Slack](/integrations/connect-a-circle-or-a-project-to-slack).

Every card offers the same four controls once connected:

| Control | What it does |
| --- | --- |
| **Test** | Sends a message to the channel now and records the result on the card. The only way to prove the channel works. |
| **Reconnect** | Runs the consent flow again. Existing role groups are adopted rather than duplicated. |
| **Disable** | Removes the connection and the stored credentials. The channel and the event settings are deleted. |
| **What to send** | The four toggles above. |

## Knowing it actually works

A connection can exist and still deliver nothing: the credentials are valid, but the channel refuses the message. The card distinguishes the two:

| The card says | What it means |
| --- | --- |
| **Connected** | Credentials are live and nothing has failed. |
| **Not delivering** | Credentials are live, and messages are being refused. The card names the cause and what to do about it. |
| **Interrupted** | Talkspirit gave up after five consecutive failures and stopped sending for this circle. |
| **No channel** | The app was installed but no channel was chosen, so nothing can be delivered. |

**Not delivering** distinguishes two situations that read differently to an administrator: a connection that has *never once* delivered, and one that worked before and is failing now.

> **Important:** a confirmation message is posted the moment you connect, so a channel that refuses the bot says so immediately instead of staying silent until the first real governance event is lost.

One state needs nothing from you: **Notifications are paused on our side** means a fault in Talkspirit, not in your configuration. Our team is alerted automatically, your settings are untouched, and the failure does not count towards the five-failure cutoff.

## A project carries its own connection

A project belongs to no circle, so it cannot borrow a circle's channel. It connects on its own, from the project’s settings, under **Notifications**. You need the access level that manages the project: owner or editor.

The **Notifications** tab offers the same four cards as a circle: Slack, Microsoft Teams, Talkspirit and the webhook. A project can use several of them at once, and each card has its **Test** button. A project tool (Trello, Asana, Jira or Basecamp) is connected from the separate **Integrations** tab.

A project's connection carries the **Tasks** family and nothing else: a task created or deleted, a task whose status, priority or due date changes, and the project renamed or deleted. Subtasks are not sent. A circle's connection never carries tasks, and a project's never carries governance activity.

A private task is not sent, and neither is a task created on a private or secret project: the channel is open to whoever the person who connected it chose, not to the project's members.

## What is not sent

- **An organisation-wide view.** There is no single page listing which circles are connected. You see the integration on the circle you are looking at, and nowhere else.
- **Meeting duration.** The meeting message names the meeting type, not a duration.

## FAQ

**Does connecting a circle expose private information to the channel?**
Only that circle's governance activity is sent, and only for the families you leave switched on. Private goals and goals owned by a person or a role are never sent.

**Can two circles post to the same channel?**
Yes. Each keeps its own event settings.

**Does disconnecting delete anything in Talkspirit?**
No. It removes the connection, the stored credentials, the channel and the event settings for that circle. Nothing in your structure changes.

**Who can connect a circle?**
An administrator of the circle in Talkspirit, who is also able to install an app in your chat workspace. Both are needed: the consent screen belongs to the chat tool.

**Why did notifications stop without anyone changing anything?**
Most often the channel changed underneath the connection: archived, deleted, or the bot removed from it. The card names which, and **Test** confirms once it is fixed.

**Does an integration slow anything down?**
No. Messages are sent in the background, and a circle with no connection makes no call at all.

## What’s next?

- [Connect a circle or a project to Slack](/integrations/connect-a-circle-or-a-project-to-slack): the Slack consent flow, channel permissions, and tagging roles from Slack.
- [Connect a circle or a project to Microsoft Teams](/integrations/connect-a-circle-or-a-project-to-microsoft-teams): the Microsoft consent flow, choosing the team and the channel, and reading the card when delivery stops.
- [Connect a circle or a project to a Talkspirit group](/integrations/connect-a-circle-or-a-project-to-a-talkspirit-group): creating the incoming webhook, pasting its URL on the circle, and finding which group receives the posts.
- [Send a circle’s or a project’s events to your own webhook URL](/integrations/send-circle-or-project-events-to-your-own-webhook): pasting a URL on the circle, the JSON each event carries, and the events that are not sent.
- [Connect a project to a project tool](/integrations/connect-a-project-to-a-project-tool): hand each new task of a project over to Trello, Asana, Jira or Basecamp, one tool per project.