Flow Start

Entry point for both Workflow and Agent flows.

Overview

The Flow Start node is the entry point for every flow. It comes in two variants:

Workflow - supports four trigger types: Chat, Manual, Schedule, and API.
Agent - conversational flows where the only trigger type is Chat.

Both variants share the same Chat configuration when the Chat trigger is selected.

Trigger Types (Workflow)

Trigger	Description
`Chat`	Triggered by user interaction in a chat interface
`Manual`	Triggered on demand via keyboard shortcut
`Schedule`	Triggered automatically on a recurring time-based rule
`API`	Triggered by an inbound HTTP request to a public endpoint

Agent flows only support the Chat trigger.

Chat Configuration

When Chat is selected (or when using an Agent flow), the following settings are available:

Chat Settings

Setting	Type	Default	Description
`Allow File Upload`	Toggle	Off	Permits users to attach files to messages
`Allow Image Upload`	Toggle	Off	Permits users to send images in chat
`Allow Voice Input`	Toggle	Off	Permits users to submit input via voice

Capabilities

Capability	Description
`Generate Images`	Enables the agent to produce images on demand
`Deep Thinking`	Activates extended reasoning for complex queries
`Web Search`	Allows the agent to retrieve information from the web

Welcome Message

The initial message displayed when a user opens the chat.

Default: Hi! How can I help you today?

Input Placeholder

Placeholder text shown inside the chat input field.

Default: Ask anything...

Suggested Prompts

Predefined prompt suggestions presented as quick-start options. Click + to add entries.

Manual Trigger

Press Ctrl + Enter to execute the flow manually. An Input JSON editor is provided for supplying JSON-formatted input data at execution time.

Schedule Trigger

Two scheduling modes are available:

Specific Times

Execute the flow at a defined time on selected days:

Field	Description
`Time`	Hour, minute, and AM/PM selectors
`Repeat`	Repeat frequency (e.g., Weekly)
`Days`	Day-of-week selectors: M, T, W, T, F, S, S
`Timezone`	Timezone for schedule evaluation

Interval

Execute the flow at a fixed recurring interval:

Field	Description
`Run every`	Interval duration (e.g., 30 minutes)
`Timezone`	Timezone for schedule evaluation

Timezone Options

Auto-detected (default), UTC, Eastern Time (ET), Central Time (CT), Mountain Time (MT), Pacific Time (PT).

API Trigger

Expose the workflow as an HTTP endpoint accessible from external systems.

Configuration

Field	Description	Default
`Endpoint URL`	Base URL with editable path	-
`Allowed Methods`	GET, POST, PUT, PATCH, DELETE	-
`Rate Limit`	Max requests per minute	60
`Timeout`	Request timeout in seconds	30
`Require Authentication`	Require `x-api-key` header	On

IP Whitelist (optional)

A list of allowed IP addresses or CIDR ranges. Click + to add entries.

CORS Origins (optional)

A list of allowed CORS origins. Click + to add entries.

API Keys

Manage API keys for endpoint authentication. Click + Create Key to generate a new key with a custom name.

Examples

Customer Support Agent

Flow Type: Agent
Welcome Message: "Hi! I'm your support assistant. How can I help?"
Input Placeholder: "Describe your issue..."
Suggested Prompts:
  - "Check my order status"
  - "Request a refund"
  - "Talk to a human agent"
Capabilities: Web Search (enabled)

Daily Report Generation

Flow Type: Workflow
Trigger: Schedule
Time: 9:00 AM
Repeat: Weekly
Days: M, T, W, T, F
Timezone: Eastern Time (ET)

Webhook Integration

Flow Type: Workflow
Trigger: API
Endpoint: /process-order
Methods: POST
Rate Limit: 100/min
Authentication: Required

Best Practices

Use Schedule triggers for recurring tasks like reports or data syncs
Use API triggers for integrations with external systems
Set appropriate rate limits to protect your workflows
Enable authentication for all production API endpoints
Write a clear welcome message that sets expectations for chat flows
Only enable capabilities the agent actually needs