> ## 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, 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 workflow editor they appear under **Entry points** (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)                                       |
| **Messaging channel** | Someone messages Telegram, WhatsApp, Slack, Discord, or Gmail | 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                              |

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

```mermaid theme={null}
flowchart LR
  Chat[Dashboard chat]
  Msg[Messaging channels]
  Cron[Schedule]
  Ev[Events]
  Wid[Widget]
  Api[API]
  Agent[Agent or workflow]
  Chat --> 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**.

Typical channels (availability follows your project’s messaging-channel registry):

| Channel      | Role                                    |
| ------------ | --------------------------------------- |
| **Telegram** | Inbound message → agent → send reply    |
| **WhatsApp** | Inbound message → agent → send reply    |
| **Slack**    | Channel/DM message → agent → send reply |
| **Discord**  | New message → agent → send reply        |
| **Gmail**    | New email → agent → reply in thread     |

### Add a messaging entry point

<Steps>
  <Step title="Connect the channel account">
    Open [Connection](/product/connections) and connect Telegram, Slack, or the toolkit you need. Replies use **that** connected account.
  </Step>

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

  <Step title="Add entry point → Messaging">
    Choose **Add entry point**, pick **Messaging**, select 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 and prompts for public channels.
  </Step>
</Steps>

Channel conversations create [external users](/product/external-users) automatically (source: **Channel**). Use the End user switcher to inspect that person’s connections and threads.

## Schedule vs events vs channels

The product distinguishes:

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

| Type      | UI group  | Behavior                                          |
| --------- | --------- | ------------------------------------------------- |
| Schedule  | Schedule  | Cron + timezone; no messaging auto-reply          |
| Events    | Events    | Toolkit webhook/poll events; no automatic reply   |
| Messaging | Messaging | Inbound + optional auto-reply on the same channel |

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 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).
* **Widgets** are a separate customer-facing chat surface. 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)
* [Triggers in the dashboard](/product/triggers-in-dashboard)
* [Widgets and embeds](/product/widgets-and-embeds)
* Developers: [Triggers](/guides/triggers)