--- title: "Connect a circle or a project to a Talkspirit group" description: "Post a circle’s governance activity or a project’s tasks to a Talkspirit group: create an incoming webhook, paste its URL on the circle or the project, and read the card" category: integrations section: native-integrations type: Tutorial lastUpdated: 2026-09-30 locale: en canonical: https://support.talkspirit.com/en/integrations/connect-a-circle-or-a-project-to-a-talkspirit-group --- # Connect a circle or a project to a Talkspirit group > **In summary:** create an **incoming webhook** in **Administration → Tools → Integrations** and choose the group there. Then open the circle’s settings, then the **Integrations** tab, select **Enable** on the **Talkspirit** card, paste the URL and **Confirm**. There is no sign-in and no consent screen: the URL is the whole connection. Messages land in the group's **newsfeed**, not in a chat conversation. This guide covers the Talkspirit card. What a circle integration sends, and how to read the card, is the same for every destination: see [Circle and project integrations](/integrations/circle-and-project-integrations-overview). Unlike Slack and Microsoft Teams, this connection is made in two places. You choose the group in your Talkspirit **Administration**, where groups are managed. You then give the resulting URL to the circle. ## Before you start - You are an organisation administrator. Creating an incoming webhook is done from **Administration**, which only organisation administrators can open. An administrator of the circle can paste the URL, but needs an organisation administrator to create it. - The group has the **Newsfeed** app enabled. The group list only offers groups with a newsfeed, and in which you are allowed to set up integrations. - Your plan still allows a new integration. When the limit is reached, **Add** is unavailable and says so. ## Step 1: Create the incoming webhook 1. Open **Administration → Tools → Integrations**. 2. Select **Incoming webhook**. 3. On the **Add** tab, under **Publish in**, choose the group. This is the group whose newsfeed will receive the circle's messages. 4. In the label field, name the webhook after the circle so you recognise it later. Left empty, it is named **Incoming webhook**. 5. Select **Add**. Talkspirit shows the URL under **You can send your data to the following Webhook URL**. Copy it. > **Important:** treat this URL like a password. Anyone who holds it can post in the group. ## Step 2: Paste the URL on the circle 1. Open the circle’s settings, then the **Integrations** tab. 2. On the **Talkspirit** card, select **Enable**. A **Webhook URL** field opens: there is no consent screen to go through. 3. Paste the URL and select **Confirm**. The card now reads **Connected** and states: "The webhook URL is stored. Posts go to the group you chose in Talkspirit." If the URL is refused, the reason appears under the field and the form stays open. The card refuses a malformed address, and any address that points to an internal network. ## Check it works Nothing is posted when you select **Confirm**. This differs from Slack, which posts a confirmation message straight away. Select **Test** on the card. It sends a message to the group now and records the result on the card. Look for it in the group's **newsfeed**. It can take up to a minute to appear: Talkspirit accepts the message first and publishes it just after. Wait and reload before concluding that nothing arrived. ## Where the posts go The card cannot show which group receives the posts. The group is chosen in **Administration**, and the URL never tells the circle which one it is. To find out, open **Administration → Tools → Integrations → Incoming webhook**, then the **Manage** tab. Each webhook shows **Published in**, followed by its group, and its URL. Match the URL with the one you pasted. To post to another group, create a new incoming webhook for that group. On the circle's card, select **Change the webhook URL**, paste the new URL and **Confirm**. Then remove the old webhook from the **Manage** tab, so that nobody can keep posting through it. ## What gets sent A new connection sends the four families described in [Circle and project integrations](/integrations/circle-and-project-integrations-overview), all switched on, as Slack and Teams do. Switch any of them off under **What to send** on the card. ## Circles connected before the migration to Talkspirit **A circle that was already posting to a Talkspirit group from the previous platform sees no change.** Its connection is carried over with the same URL. It keeps posting to the same group, and it keeps sending only what the previous platform sent: the meeting report. On the card, this reads as **Meetings** switched on and the other three families switched off. On a carried-over connection, **Meetings** covers the meeting report only; the messages for a meeting that has finished and a meeting about to start stay off. - To add Governance, Assignments or Goals, switch them on under **What to send**. - To receive everything a new connection sends, select **Disable**, then connect again with the same URL. A new connection starts with the four families on. A connection that had already stopped delivering on the previous platform is not carried over. The card then shows **Enable**: follow the two steps above. ## When delivery stops The URL is this connection's only credential, so replacing it is the repair. There is no **Reconnect** button, because there is no account to reconnect. | What the card says | What it means | What to do | | --- | --- | --- | | **Sending was interrupted** | Five deliveries in a row were refused, so sending stopped for this circle, for example because the incoming webhook was deleted in Talkspirit. | Create a new webhook if needed, select **Change the webhook URL**, paste it and **Confirm**, then **Test**. A new URL clears the failure count. | | **Connected, but nothing has ever been delivered** | The URL was stored, and every attempt since has been refused. | Check that you copied the whole URL, then paste it again. | | **Recent notifications were not delivered** | Delivery worked before and is failing now. | Check that the webhook still exists on the **Manage** tab. | | **Notifications are paused on our side** | A fault in Talkspirit, not in your configuration. | Nothing. Our team is alerted automatically and your settings are untouched. | ## On a project A project connects Talkspirit from its settings, under **Notifications**, with the same card and the same two steps. You need to be an owner or editor of the project. A project holds one Talkspirit destination: pasting a new URL replaces the previous one. The group receives the project's tasks, as described in [Circle and project integrations](/integrations/circle-and-project-integrations-overview). ## What this integration does not do - **Choose the group from the card.** The group is chosen when the incoming webhook is created, in **Administration**. The card has no group picker. - **Show the group's name.** Find it on the **Manage** tab of the incoming webhook, as described above. - **Post in a chat conversation.** Messages go to the group's newsfeed. - **Tag a role, or answer a command.** Both are Slack features. ## What’s next? - [Circle and project integrations](/integrations/circle-and-project-integrations-overview), what is sent, the event families, and reading the card - [Connect a circle or a project to Slack](/integrations/connect-a-circle-or-a-project-to-slack) - [Connect a circle or a project to Microsoft Teams](/integrations/connect-a-circle-or-a-project-to-microsoft-teams)