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

# Entry points and channels

> How people reach an agent: dashboard chat, MCP, messaging channels, schedules, events, widgets, and API.

An agent is not limited to dashboard Chat. **Entry points** are the ways a run can start. In the agent editor they appear under the **Entry points** tab (channels and triggers that start this agent).

## Ways in (overview)

| Way in | What happens | Auto-reply on that surface? |
| - | - | - |
| **Dashboard chat** | Always on for agents in Flowra Chat | Yes (in Chat) |
| **MCP** | Cursor, Claude, and other MCP clients call the agent | Via the client |
| **Messaging channel** | Someone messages a connected messenger (see list below) | Yes — agent can reply on the same channel |
| **Schedule (cron)** | Runs on a cron expression + timezone | No messaging reply |
| **Event / webhook** | Toolkit event or webhook fires | No automatic reply — use tools for outbound actions |
| **Website widget** | Visitor chats via embed | Yes (in the widget) |
| **API** | Your backend starts a thread / run | Controlled by your app |

In the agent editor, these live under the **Entry points** tab: built-in chat and **Use as MCP**, then **Channels** (messaging + widget) and **Automation** (schedule + events). See [Workflows in the dashboard](/product/workflows-in-dashboard).

Build once; attach the entry points you need. Same agent, same execution log.

```mermaid theme={null}
flowchart LR
  Chat[Dashboard chat]
  Mcp[MCP]
  Msg[Messaging channels]
  Cron[Schedule]
  Ev[Events]
  Wid[Widget]
  Api[API]
  Agent[Agent or workflow]
  Chat --> Agent
  Mcp --> Agent
  Msg --> Agent
  Cron --> Agent
  Ev --> Agent
  Wid --> Agent
  Api --> Agent
```

## Messaging channels

**Channels** are places people can message the agent. When someone messages there, the agent wakes up and can **reply on the same channel**.

Availability follows the product messaging-channel registry (what you see under **Add channel** / **Add entry point**). Current channels:

| Channel | Typical inbound | Reply |
| - | - | - |
| **Telegram** | Bot message / chat | Reply in the same chat |
| **WhatsApp** | Incoming message (connected WhatsApp account) | Reply on the same thread |
| **Slack** | Channel or DM message | Reply in the same conversation |
| **Discord** | New message | Reply in the same channel/DM |
| **Gmail** | New email | Reply in the email thread |
| **Instagram Business** | Business DM | Reply in the same conversation |
| **Instagram Private** | Private account DM | Reply in the same DM thread |
| **LINE** | Message (user / room / group) | Push reply to that chat |
| **Bale** | Bot / chat message | Reply in the same chat |

Also under **Channels** in Entry points: the website **Chat widget** (customer-facing embed — see [Widgets and embeds](/product/widgets-and-embeds)). That is not a messenger toolkit, but it is grouped with channels because people message there and the agent replies.

Public overview of messengers: [flowra.dev/channels](https://flowra.dev/channels).

### Add a messaging entry point

<Steps>
  <Step title="Connect the channel account">
    Open [Connection](/product/connections) and connect the toolkit for that channel (Telegram, WhatsApp, Slack, Instagram Business, …). Replies use **that** connected account. Some channels need [App credentials](/product/app-credentials) on the project first.
  </Step>

  <Step title="Open the agent">
    Go to [Workflows](https://flowra.dev/dashboard/workflows), open the agent, and open the **Entry points** tab.
  </Step>

  <Step title="Add channel">
    Under **Channels**, choose **Add channel** or **Add entry point** → **Messaging**, pick the channel, and complete the connection/config the UI asks for.
  </Step>

  <Step title="Mind who can wake the agent">
    Anyone who can message that channel can wake the agent and get a reply with the connected account. Harden tools (**Actions**), prompts, and **Behavior** (guardrails, usage caps, escalation) for public or shared channels.
  </Step>
</Steps>

Channel conversations create [external users](/product/external-users) automatically (source: **Channel**). Use the End user switcher to inspect that person’s threads. From External Users you can take over a conversation when the agent escalates or when you need to reply as an operator.

Optional: under **Actions** → **Tools**, **Let visitors use my accounts** lets channel (and widget) visitors run selected apps with your connection. Leave it off if each person should connect their own accounts.

## Schedule vs events vs channels

The product distinguishes:

* **Channels** — two-way messaging (inbound + auto-reply), including the website widget
* **Triggers** — only **start** a run (schedule or one-way events)

| Type | UI group | Behavior |
| - | - | - |
| Messaging / widget | **Channels** | Inbound + auto-reply on that surface |
| Schedule | **Automation** | Cron + timezone; no messaging auto-reply |
| Events | **Automation** | Toolkit webhook/poll events; no automatic reply |

Manage enabled trigger **instances** (subscriptions) also at [Triggers](https://flowra.dev/dashboard/triggers). Product schedule walkthrough: [Schedule a daily trigger](/product/try-schedule).

## Built-in: dashboard chat, MCP, and widgets

* **Dashboard chat** is always available for agents — pick the agent in [Chat](https://flowra.dev/dashboard/chat). Each person uses their own accounts via the [external user switcher](/product/external-users).
* **Use as MCP** is always available on the agent. Use **Install** on Entry points (or **Install as MCP** on the list card). See [MCP in the dashboard](/product/mcp-in-dashboard).
* **Widgets** are a separate customer-facing chat surface. Add them under Entry points or configure under [Widgets and embeds](/product/widgets-and-embeds). Widget visitors appear as external users with source **Widget**.

## Related

* [External users switcher](/product/external-users)
* [Workflows in the dashboard](/product/workflows-in-dashboard)
* [Connections](/product/connections)
* [Triggers in the dashboard](/product/triggers-in-dashboard)
* [Widgets and embeds](/product/widgets-and-embeds)
* Developers: [Triggers](/guides/triggers)


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