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

# Communication

Communication Steps connect your AirOps workflows with email and messaging platforms, enabling automated notifications, outreach, and team coordination. These integrations bridge the gap between AI-powered automation and your communication channels.

The Communication Steps include:

1. [**Gmail**](/integrations/overview/communication/gmail.md) -- send emails with workflow-generated content
2. [**Slack**](/integrations/overview/communication/slack.md) -- send notifications and share content with teams through Slack channels

Communication Steps transform how you share information and coordinate with your team by integrating workflow outputs directly into your existing communication tools. These connections allow you to automate routine communications, send personalized outreach, notify team members of important events, and share AI-generated content with stakeholders.

By incorporating these integrations into your workflows, you can build automated systems that send personalized email campaigns, notify teams of workflow completions, share generated content for review, and keep stakeholders informed about important updates.

{% hint style="info" %}
Note: Communication Steps typically require authentication with the respective platforms. You'll need appropriate access permissions for each service you wish to connect.
{% endhint %}


---

# 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.airops.com/integrations/overview/communication.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.