> For the complete documentation index, see [llms.txt](https://docs.zbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/azure-communication-services.md).

# Azure Communication Services

Integrate Azure Communication Services with ZBrain to enable voice, video, chat, SMS, and email interactions via AI APIs.

The Azure Communication Services piece in ZBrain Flow provides integration with Microsoft's cloud communication platform, allowing you to send emails directly from your workflows. This connector enables you to automate email communications without manual intervention. This piece is ideal for organizations looking to streamline their email processes, automate routine communications, and ensure reliable message delivery as part of their broader business workflows.

## **How to Use Azure Communication Services in ZBrain Flow** <a href="#how-to-use-azure-communication-services-in-zbrain-flow" id="how-to-use-azure-communication-services-in-zbrain-flow"></a>

**Configuration Steps:**

* Click on the '+' button in the Flow and search for Azure Communication Services.
* Select Azure Communication Services.
* The primary action available is:
  * **Send Email** – Deliver email messages through Azure's communication infrastructure.
* If this is your first time connecting to Azure Communication Services, you'll first need to create your Azure Communication Services connection. For this:
  * Click on the connection dropdown and select 'Create connection'.
  * In the popup window that appears, you'll need to:
    * Enter a descriptive 'Connection Name' to identify this Azure connection
    * In the 'Connection string' field, paste your Azure Communication Services connection string
    * Click 'Save' to store this connection
* Next, specify sender and recipient information in the respective ‘Sender Email (From)’ and ‘To’ fields. Click ‘Add Item’ in the ‘To’ field if you need to send the email to multiple individuals.
* Optionally set additional options like ‘CC’, ‘BCC’, and ‘Reply To’ addresses. To include multiple recipients in the CC or BCC fields, click ‘Add Item’ for each additional address.
* In the 'Subject' field, enter the email subject line.
* From the 'Content Type' dropdown, select the format of your email:
  * 'HTML' - for rich formatting with HTML tags
  * 'Text' - for plain text emails
* In the 'Content' field, enter the body of your email:
  * If you selected HTML, you can use HTML tags for formatting (headings, lists, links, etc.)
  * If you selected Text, enter plain text without formatting


---

# 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.zbrain.ai/zbrain-documentation/zbrain-builder/flows/flow-components/azure-communication-services.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.
