Configuration
id
: Unique node identifiersystem_prompt
: Instructions for the agent’s behaviorprovider_model_name
: AI model to usetemperature
: Model creativity, 0.0-1.0 (default: 0.0)max_iterations
: Maximum tool calls/responses (default: 80)max_tokens
: Maximum tokens per response (default: 8192)reasoning_effort
: For o1 models - low, medium, high (optional)webhooks
: Custom API tools (optional)mcp_servers
: MCP server tools (optional, HTTP streamable only)
Built-in tools
send_notification_to_user
send_notification_to_user
Send a message to the user without waiting for a response.Parameters:
message
(string, required): The text message to send
send_media
send_media
Send media files to the user via WhatsApp.Parameters:
media_url
(string, required): URL of the media filemedia_type
(string, required): “image”, “video”, “audio”, or “document”caption
(string, optional): Caption for the media
get_execution_metadata
get_execution_metadata
Access flow execution context and variables.Parameters: NoneReturns: Flow variables, execution context, and metadataUsage: Access stored data and flow state information
get_whatsapp_context
get_whatsapp_context
Get WhatsApp conversation details.Parameters: NoneReturns: Phone number, conversation ID, and contact informationUsage: Access user contact details for personalization
save_variable
save_variable
Store data for use in later flow steps.Parameters:
key
(string, required): Variable namevalue
(any, required): Value to store
get_variable
get_variable
Retrieve previously stored data.Parameters:
key
(string, required): Variable name to retrieve
get_current_datetime
get_current_datetime
Get the current date and time.Parameters: NoneReturns: Current timestamp in ISO formatUsage: Time-based logic and timestamp generation
complete_task
complete_task
Complete the agent’s task and continue the flow.Parameters: NoneUsage: Signal task completion and advance to next step
handoff_to_human
handoff_to_human
Transfer the conversation to a human agent.Parameters:
reason
(string, optional): Reason for handoff
Dynamic webhook tools
Dynamic webhook tools
Custom tools for external API integration.Parameters: Defined by webhook configurationUsage: Call external APIs, fetch data, trigger actions
Examples
Customer support agentWhen the webhook performs a POST, describe the expected payload with
body_schema
. The LLM fills that structure automatically; only use body
for fixed values or when you already have the exact JSON stored in variables.How it works
- Starts conversation: Uses system prompt and conversation history
- Tool access: Can call built-in tools and custom webhooks
- Multi-turn: Continues until calls
complete_task
or needs user input - Message injection: New user messages are automatically injected during conversation
- Flow control: Returns
next
edge when task completed,wait
when needs input