Flero platform nodes
Nodes that let a workflow read and manage Flero itself: run statistics, inventories, administration, and triggers that fire on what happens in your Flero instance. They sit in the palette's Flero Nodes section, and only admins can see and use them. Flero Event and Flero Monitor appear under Triggers.
Each node authenticates with a saved credential holding a Flero API key (credentialId). The key's permissions decide what the node may do. Create one under API Keys in Settings.
Flero Analytics
What: Reads execution, failure and AI-spend metrics.
Ports: in input; out output.
Configuration:
| Field | Notes |
|---|---|
operation |
Required: execution_stats (default), workflow_performance, failing_nodes, ai_spend, execution_list or audit_events |
workspaceId, workflowId |
Narrow to one workspace or workflow |
since, until |
The time range |
bucket |
hour or day (default) |
groupBy |
none, workflowId or workflowVersionId |
status |
Filter runs by status |
limit |
Default 20 |
Use when: Sending a weekly digest of failing workflows and AI spend to a Slack channel.
Flero Inventory
What: Lists workflows, node usage, credentials and members.
Ports: in input; out output.
Configuration: operation (workflows default, node_usage, credentials, members), workspaceId, includeArchived (default off).
Flero Admin
What: Administers the instance from a workflow: folders, members, workflow lifecycle, variables, and stopping runs.
Ports: in input; out output.
Configuration:
| Field | Notes |
|---|---|
operation |
Required: create_folder (default), rename_folder, delete_folder, invite_member, update_member_role, remove_member, copy_workflow, update_workflow, delete_workflow, restore_workflow, execute_workflow, set_variable, delete_variable or stop_execution |
workspaceId |
The workspace to act on |
confirm |
Must be on for delete_folder, remove_member, delete_workflow and delete_variable. Default off. |
folderId, name, color |
For folder operations |
email, userId, role |
For member operations. Roles: admin, editor, viewer (default). |
workflowId, status, input |
For workflow operations |
variableName, variableValue, isSecret |
For workspace variable operations |
executionId |
For stop_execution |
The destructive operations refuse to run unless confirm is on, so a mis-wired workflow can't delete things by accident.
Knowledge Query
What: Asks the Flero knowledge graph a question and returns matching facts for the next node.
Ports: in input; out output.
Configuration: question (required), scopeHint (all default, system, organization, workspace, personal), limit (default 25).
Use when: Grounding an AI Agent's answer in what your organisation has recorded in Flero.
Flero Event
What: A trigger that starts a run when a run in your Flero instance fails or completes.
Ports: out output (no input).
Configuration:
| Field | Notes |
|---|---|
event |
Required: execution_failed (default), execution_completed or execution_finished |
workflowId, workspaceId |
Narrow to one workflow or workspace |
ignoreTriggerSpawned |
Ignore runs that a trigger started, including this one. Default on. Off, a failing workflow that listens for failures can retrigger itself. |
ignoreSelf |
Ignore this workflow's own runs. Default on. |
Use when: Posting every failed run, with its error, to an on-call channel.
Flero Monitor
What: A trigger that checks a metric on a schedule and starts a run when it crosses a threshold.
Ports: out output (no input).
Configuration:
| Field | Notes |
|---|---|
check |
Required: failure_rate (default), failed_executions, no_successful_runs, ai_spend, node_failures or avg_duration |
threshold |
Required |
comparison |
above (default) or below |
windowMinutes |
The period measured. Default 60. |
minimumSample |
Runs needed before a rate or average counts. Default 5. |
requireConsecutive |
Checks in a row that must cross the threshold. Default 1. |
workflowId, nodeId, workspaceId |
What to watch |
pollInterval |
How often to check. Default 15m. |
Flero Event or Flero Monitor? Flero Event reacts to a single run within seconds and can tell you which run failed. Flero Monitor notices trends and things that stop happening, such as a scheduled workflow that no longer succeeds.
Related
Found something out of date? This page lives in the Flero docs content set.