> For the complete documentation index, see [llms.txt](https://angoor-ai.gitbook.io/angoor-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://angoor-ai.gitbook.io/angoor-ai/basics/configuration/channels.md).

# Channels

The Channel Management section enables you to integrate communication platforms and create custom API channels for connecting third-party software to your angoor.ai workflows, managing how external triggers activate your automated flows.

## Channel Management Dashboard

The main dashboard displays all available channels across your workspace:

* **Channel Name:** Identifier for each channel with visual indicators for channel type
* **Creator:** Channel source (Angoor for native integrations, Internal for custom channels)
* **Owner:** Account or team responsible for channel management
* **Subscriptions:** Number of active connections or subscribers using the channel.

<figure><img src="/files/3NV0UoAXWVeuF9lKt7JK" alt=""><figcaption></figcaption></figure>

### **Channel Types**

* **Integration Channels:** Pre-built connectors for platforms like WhatsApp and Instagram added through the integrations menu
* **Custom API Channels:** User-created channels for connecting third-party software with custom triggers

## Creating Custom Channels

**Step 1**: Click "New" to create a custom channel and enter a descriptive name for your third-party integration.

**Step 2:** Configure the subscription settings including name, trigger type (On Trigger or Scheduled), and activation method.

**Step 3:** Copy the generated API Key and API URL to configure in your third-party software for sending payloads.

**Step 4:** Attach a form to capture and structure incoming payload data from the external trigger.

**Step 5:** Set up flow hierarchy to determine which workflows execute when the channel receives a trigger.

<figure><img src="/files/dJy3GuttmIlZ31iZJFgw" alt=""><figcaption></figcaption></figure>

## Configuration Tab

<figure><img src="/files/gfbfSAD4D6kKveV3QRpD" alt=""><figcaption></figcaption></figure>

### **Subscription Setup**

&#x20;Define how your channel receives and processes external triggers:

* **Subscription Name:** Identifier that appears in the flow builder trigger menu
* **Trigger Type**:
  * **On Trigger:** Activates immediately when receiving API payload
  * **Scheduled:** Processes payloads at defined intervals

### **API Integration**&#x20;

&#x20;Technical details for connecting external software:

* **API Key:** Unique authentication token for secure payload delivery.
* **API URL:** Endpoint where third-party software sends trigger data.
* **Sample cURL Command:** Pre-formatted example for testing integration.

## Hierarchy Tab

<figure><img src="/files/yjB4JcaujbMwbPs7flb6" alt=""><figcaption></figcaption></figure>

### **Flow Prioritization**&#x20;

&#x20;Control execution order when multiple flows use the same trigger.

### **User Groups Priority**&#x20;

Specify which user groups get higher priority for trigger processing:

* Helps segment customers for differentiated service levels.
* Ensures VIP or priority groups receive faster response.

### **Flows Execution Order**&#x20;

&#x20;Define which flows execute first when triggered:

* **Top Priority:** Only the top flow will execute.
* **All Flows:** All connected flows execute based on order.
* Flows not in the priority list execute last.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://angoor-ai.gitbook.io/angoor-ai/basics/configuration/channels.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.