> For the complete documentation index, see [llms.txt](https://docs.textmaddie.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.textmaddie.com/your-dashboard/integrations.md).

# Integrations

Connect Slack to your Text Maddie agent so it can notify your team and ask questions mid-conversation. Set channels, a team directory, and ping rules.

## Slack

Slack is how the agent talks to your team. It posts when something needs a person, and your team can answer without opening the dashboard.

Text Maddie creates and installs the Slack app for you. What you control is where it posts and who it knows about.

### What the agent uses Slack for

**Notifications.** One channel receives the running record of the agent's work: an action item raised or updated, a follow-up scheduled, a line transfer starting and finishing. Delivery problems are not posted here; the agent handles them inside the conversation and tells your team in one line, through a ping, only when its retries are spent. Each line's failure share is on [Lines](/your-dashboard/lines.md#line-health-and-quality).

**Pings.** During a conversation the agent can post to a channel to ask a question or hand something off. A customer asks about an invoice, the agent posts in `#billing`, someone answers, and the agent carries the answer back into the conversation.

**Daily report.** Once a day, a summary of the last 24 hours lands in a channel you choose. The time and the switch live on [Settings](/your-dashboard/settings.md#daily-report).

### Channels

Channels are set once for the organization and shared by every agent. Each channel gets a label, and each agent picks which labels it may use.

{% stepper %}
{% step %}

#### Add the channel to your organization

On the Integrations page, add the channel and give it a label that says what it is for, such as `billing` or `scheduling`.
{% endstep %}

{% step %}

#### Choose which agents may post to it

Per agent, select the labels its ping tool may use. An agent only posts to channels you have selected for it.
{% endstep %}

{% step %}

#### Choose the notifications channel

One label per agent receives automated notifications. Leave it unset and notifications stay in the dashboard only.
{% endstep %}

{% step %}

#### Choose the daily report channel

One label per agent receives the daily report. Leave it unset and the report goes to the first channel in your list. Remove that channel later and the report pauses until you pick another.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Invite the Slack app to any channel you add. It cannot post to a channel it is not in, and the failure is silent from the agent's side.
{% endhint %}

### The team directory

The directory tells the agent who your people are and what they handle, so it pings the right person rather than the whole channel.

Alongside it, **ping instructions** are your policy in plain language. This is where you write the rules:

```
Ping Dana for anything about scheduling or reschedules.
Ping Marcus for pricing questions above $5,000.
Do not ping anyone between 8pm and 7am unless the lead or customer says it is urgent.
```

The directory and the instructions are shared across every agent in your organization.

{% hint style="warning" %}
Keep the directory current. An agent pinging someone who left is a bad look for a lead or customer waiting on an answer.
{% endhint %}

## Your own systems

To trigger the agent from your CRM, scheduler, or anything else you run, use the [Agent API](https://docs.textmaddie.com/api-reference). Mint a key on the [Settings](/your-dashboard/settings.md) page.

For a tool the agent should be able to use during a conversation, such as looking up an order in your system, talk to your Text Maddie contact. We build those.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.textmaddie.com/your-dashboard/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.