1. Support
  2. Integrations
  3. Agent
AI 17 nodes

Agent

AI integration · 17 node(s).

00Overview

Every field below is exactly what you see in the Flomation editor. Fields marked ● live picker let you choose from a list pulled live from your account — no IDs to look up.

01Connecting Agent

Agent nodes have no credential fields — there is no API key or secret to add as an environment secret. Fill in each node's own fields, listed below, and run the flow.

02Add

Add to Conversation

agent/add_to_conversation · Action

Store a message and return conversation history

FieldTypeDetails
Conversation IDstringRequired${conversation_id}
Agent IDstringRequired${flow.agent_id}
Message ContenttextRequired
RolestringRequiredchoices: User (inbound), Assistant (outbound)
Channel Typestring${channel_type}
Senderstring${from}
History Limitinteger30

Returns: tool_result, conversation_history, raw_history, message_id, success, error

03Create

Create Schedule

agent/create_schedule · Action

Create a recurring scheduled task for the agent

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstring${flow.agent_user_id}
Conversation IDstring${flow.conversation_id}
Schedule namestringRequired
What to do when the schedule firesstringRequired
ModestringRequiredchoices: Daily, Weekly, Interval
Time of day (HH:MM, for daily/weekly)string
Days of week (comma-separated, for weekly)string
Interval value (for interval mode)string
Interval unitstringchoices: Minutes, Hours, Days
Timezone (IANA)stringEurope/London
Source channel typestring${flow.channel_type}

Returns: tool_result, schedule_id

04Delete

Delete Schedule

agent/delete_schedule · Action

Delete a scheduled task by name

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Schedule name to deletestringRequired

Returns: tool_result

05Forget

Forget Memory

agent/forget · Action

Delete a specific memory from an agent's store

FieldTypeDetails
Memory IDstringRequiredUUID of the memory to delete

Returns: success

06Fulfill

Fulfil Commitment

agent/fulfill_commitment · Action

Mark an agent commitment as fulfilled after the follow-up has been delivered

FieldTypeDetails
Commitment IDstringRequired${trigger.commitment_id}

Returns: success

07Get

Get Calendar

agent/get_calendar · Action

Return the user's upcoming Google Calendar events. Use when the conversation hints at scheduling — where they are, where they need to be, whether they're running late.

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstringRequired${flow.agent_user_id}
How many hours ahead to look (default 24, max 168).integer24

Returns: tool_result, events, event_count, no_calendar, success, error

Get Conversation

agent/get_conversation · Action

Fetch the full message history of a previous conversation the agent has had with this user. Use when a summary in your Recent Conversations section looks relevant.

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstringRequired${flow.agent_user_id}
Conversation ID — pass the conversation_id verbatim from the Recent Conversations section.stringRequired00000000-0000-0000-0000-000000000000
Maximum messages to return (defaults to 200; max 500). Messages are read in sequence order from the start of the conversation.integer200

Returns: tool_result, messages, message_count, returned_count, ended_at, was_truncated, success, error

08List

List Identities

agent/list_identities · Action

List all known channel identities for the current user

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstringRequired${flow.agent_user_id}

Returns: tool_result, identities, count

List Schedules

agent/list_schedules · Action

List all scheduled tasks for the agent

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}

Returns: tool_result, schedules, count

09Process

Process Extraction Output

agent/process_extraction · Action

Parse a structured extraction JSON payload and write memories, pending actions, and commitments

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Extraction JSONstringRequired${node.ai.response}
Agent User IDstring${trigger.agent_user_id}
Conversation IDstring${trigger.conversation_id}
Source Message IDstring${trigger.message_id}
Channel Typestring${trigger.channel_type}

Returns: memories_written, memories_flagged, memories_discarded, pending_actions_written, commitments_written, confirmations_processed, errors

10Read

Read Agent State

agent/read_state · Action

Read a persistent state value from an agent's key-value store

FieldTypeDetails
Agent IDstringRequiredID of the agent
State KeystringRequiredconversation_history

Returns: value, exists

11Recall

Recall Memories

agent/recall · Action

Fetch an agent's memories about a specific user

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstringRequired${flow.agent_user_id}
Pinned onlybooleanfalse
Limitinteger20
Semantic search querystring
AWS region for embeddingsstringus-east-1

Returns: memories, count

12Remember

Remember Fact

agent/remember · Action

Store a durable fact, preference, or piece of feedback in an agent's memory

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstring${flow.agent_user_id}
ScopestringRequiredchoices: User-specific, Agent-global
Memory TypestringRequiredchoices: Preference (auto-pinned), Feedback (auto-pinned), Fact, Relationship, Task, Session summary
TitlestringRequiredShort handle for the memory
BodystringRequiredThe fact itself
Pinned (always included in system prompt)booleanfalse
Confidence (0.0–1.0, defaults 1.0)string1.0
AWS region for embeddingsstringus-east-1

Returns: memory_id

Search Conversation History

agent/search_conversation · Action

Full-text search your entire message history with this user (all channels) to recall something outside your current context. Provide a search query.

FieldTypeDetails
Agent IDstringRequired${flow.agent_id}
Agent User IDstringRequired${flow.agent_user_id}
Search query — words or a phrase to find in past messages.stringRequiredthe demo wallpaper image
Max resultsinteger20

Returns: tool_result, results, match_count, success, error

14Send

Send Agent Message

agent/send_message · Action

Send a message through an agent's communication channel and record it

FieldTypeDetails
Agent IDstringRequiredID of the agent
ChannelstringRequiredchoices: Telegram, Email, Webhook
RecipientstringRequiredChat ID, email address, or webhook URL
MessagetextRequiredMessage content

Returns: message_id, success

15Set

Set Reminder

agent/set_reminder · Action

Schedule a follow-up. The platform resolves the timing and returns the exact date it stored.

FieldTypeDetails
When to fire, in plain English: a duration ("in 72 hours", "in 30 minutes"), a relative day ("tomorrow at 9am", "next Monday"), or a date ("1 October", "25 December at 09:00"). Never work the calendar date out yourself — pass what was asked for and use the date this returns.stringRequiredin 72 hours
What to remind about, written so it still makes sense on its own days laterstringRequiredPull the updated campaign numbers and compare the click-to-view ratio
What sort of follow-up this isstringchoices: Reminder, Follow-up, Monitor, Chase
Leave empty for a one-off. Set it only when the follow-up was asked for repeatedlystringchoices: One-off, Daily, Weekdays, Weekly, Monthly
Agent IDstringRequired${flow.agent_id}
Agent User IDstring${flow.agent_user_id}
Conversation IDstring${flow.conversation_id}

Returns: tool_result, success, commitment_id, due_at, due_at_friendly

16Write

Write Agent State

agent/write_state · Action

Write a persistent state value to an agent's key-value store

FieldTypeDetails
Agent IDstringRequiredID of the agent
State KeystringRequiredconversation_history
ValueobjectRequired

Returns: success

17Notes & Limitations

Behaviours and constraints worth knowing before you build with these nodes.

  • Memories are scoped to a single user, so a fact stored for one person is not returned when the agent recalls memories while serving a different user.
  • Scheduled tasks are addressed by their name, so the name you set when creating one is the handle you must supply later to delete it.
  • Adding a message to a conversation also returns the full running history, so the same step doubles as a read of the thread.
  • Retrieving calendar events requires the user's Google Calendar to be connected first and returns only upcoming events, not past ones.