> ## Documentation Index
> Fetch the complete documentation index at: https://docs.appeeky.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations and delivery

> Where briefings and alerts go, and the tools the Co-founder can work in.

Briefings go to your account email by default. Connect more tools in **App Co-founder → Integrations** to get briefings where you work, chat from there, and let the Co-founder open issues or post updates.

| Tool | Briefings | Chat | Approvals | What else |
| - | - | - | - | - |
| **Email** | ✓ (default) | | ✓ | Alerts when no chat app is connected |
| **Slack** | ✓ | ✓ | ✓ | Post summaries to a channel |
| **Telegram** | ✓ | ✓ | ✓ | Alerts on your phone |
| **Appeeky mobile app** | | | | Alert push notifications |
| **Linear** | | | | Create, update and comment on issues |
| **GitHub** | | | | Open issues and, in write mode, pull requests |
| **Notion** | | | | Mirror decisions and the public diary to a database; sync pages into your knowledge base |
| **Webhook** | ✓ | | | The full briefing as JSON to your own endpoint |

Coding agents have their own page: [Coding agents](https://docs.appeeky.com/docs/cofounder/coding-agents.md).

> [!NOTE]
>
> If you track several apps, email and Telegram combine their briefings into one daily digest instead of one message per app.

***

## Email

Every briefing is emailed to your Appeeky account address, with one-click approve and reject links for up to five pending decisions and knowledge suggestions. No setup needed.

## Slack

Connect Slack in **Integrations**, then in **Settings → Delivery → Slack daily brief** turn on **Post daily brief to Slack** and pick the **Briefing channel**. Invite the bot to that channel first.

Reply in the briefing's thread to ask follow-up questions. In write mode you can also say things like "reply to that review" or "open a Linear issue".

## Telegram

In **Integrations → Telegram**, open the one-time pairing link to connect your account to **@AppeekyCofounderBot**. Briefings and alerts arrive as messages; reply to the bot to ask questions or approve actions. Send `/disconnect` at any time to unpair.

## Linear

Connect a workspace and the Co-founder opens issues for the prioritized actions in each briefing, picking the right team. You can pin a default team. From chat it can also search issues, comment and change their state.

## GitHub

Install the GitHub App on the repositories you choose. The Co-founder acts as `app-co-founder[bot]`: it opens issues for actions and, in write mode, pull requests in the repo you pick. GitHub releases also feed [release intelligence](https://docs.appeeky.com/docs/cofounder/capabilities.md#releases).

## Notion

Connect Notion and pick a database. The Co-founder mirrors its decision log there and, optionally, your public diary. Notion pages can also be synced into your [knowledge base](https://docs.appeeky.com/docs/cofounder/knowledge-base.md#keep-notion-pages-in-sync).

## Webhook

Add an HTTPS URL and the full briefing is POSTed as JSON after every scheduled or manual run. It works in read mode and fits tools like Zapier or n8n.

Set an optional shared secret: it's sent as the `X-Cofounder-Secret` header so you can verify the request.

> [!TIP]
>
> To send events **to** the Co-founder instead, such as a support backlog spike, use your [custom webhook](https://docs.appeeky.com/docs/cofounder/api.md#custom-webhook). Each event becomes a signal that can trigger an alert.

***

## Connection health

The Integrations page shows when a connection breaks, for example an expired token or a missing permission. Reconnect from the same page; you can snooze a warning you're already handling.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.