Skip to main content
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)

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. Build once; attach the entry points you need. Same agent, same execution log.

​
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: Also under Channels in Entry points: the website Chat widget (customer-facing embed — see 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.

​
Add a messaging entry point

1

Connect the channel account

Open Connection and connect the toolkit for that channel (Telegram, WhatsApp, Slack, Instagram Business, …). Replies use that connected account. Some channels need App credentials on the project first.
2

Open the agent

Go to Workflows, open the agent, and open the Entry points tab.
3

Add channel

Under Channels, choose Add channel or Add entry point → Messaging, pick the channel, and complete the connection/config the UI asks for.
4

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.
Channel conversations create 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)
Manage enabled trigger instances (subscriptions) also at Triggers. Product schedule walkthrough: Schedule a daily trigger.

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

  • Dashboard chat is always available for agents — pick the agent in Chat. Each person uses their own accounts via the external user switcher.
  • 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.
  • Widgets are a separate customer-facing chat surface. Add them under Entry points or configure under Widgets and embeds. Widget visitors appear as external users with source Widget.