Execute a Flow

Execute a Flow

Once your flow is created and configured, you need to test it to verify it works correctly before activating it in production.

Test Mode

Test mode runs the flow once with test data, without needing to activate it.

How to test

1. Open the flow in the visual editor
2. Click the Test button (play icon in the toolbar)
3. If the flow starts with a Webhook, the test URL will be shown to send data
4. If it starts with Schedule or Start, you can provide a test JSON
5. Watch the execution: each node lights up as it runs
6. When done, review each node’s result by double-clicking and viewing the Trace tab

Test data for Webhook

If your flow uses a Webhook, you can send test data in several ways:

From an external tool (Postman, curl):

curl -X POST https://us1.floogos.com/webhooks-dev/YOUR_HASH \
  -H "Content-Type: application/json" \
  -d '{"id": 123, "name": "Test Order", "total": 19.90}'

From Shopify or another service: configure the development webhook (URL webhooks-dev/) to receive real events in test mode.

Interpreting test results

After running a test, each node shows its status:

Status	Color	Meaning
Completed	Green	Node executed successfully
Failed	Red	Node failed - check error in Trace
Skipped	Gray	Node was skipped (Decision branch not taken)
Pending	Yellow	Node is waiting (Delay, Merge)

Inspecting data at each node

1. Double-click on any executed node
2. Go to the Trace tab
3. You’ll see:
   • Input (data): data the node received
   • Output (result): data the node returned
   • Config: configuration used for execution
   • Error: error message if it failed
   • Response time: execution time in milliseconds

Resolving errors with FlooIA

If a node fails during testing:

1. Open the failed node (double-click)
2. In the Trace tab, click “Analyze with AI”
3. FlooIA will analyze the input data, node configuration and error message
4. It will show the cause, solution and often a button to apply the fix directly

Common errors FlooIA resolves:

Error	Typical Cause	Solution
Unexpected token '{'	Unresolved {{}} variable in Decision	Fix the field path (e.g. {{billing_address.country_code}} without data. prefix)
Cannot find module	Module name with incorrect case	The engine auto-corrects case
Credentials not found	credentials_id not configured	Create credential and assign it to the node
Timeout	External API taking too long	Increase timeout or add retry

Activate the Flow (Production)

When the test works correctly, activate the flow for automatic execution.

How to activate

1. Make sure all changes are saved
2. Click the Activate button (toggle in the editor header or from the flow list)
3. The flow changes to Online status (green indicator)
4. From now on, it will run automatically based on its trigger:
   • Webhook: each time a request is received at the live URL
   • Schedule: according to the configured schedule
   • DataStoreTrigger: when DataStore changes are detected
   • FormTrigger: when the associated form is submitted

Test vs Live URL difference

	Test URL (webhooks-dev)	Live URL (webhooks)
When used	During development	In production
Requires active flow	No	Yes
Visible in history	Yes (temporary)	Yes (permanent)
Recommended for	Debugging, testing	Shopify, Stripe, real integrations

Execution History

Every execution (test or production) is recorded in the history.

How to access

1. From the editor: click the History icon in the toolbar
2. From the sidebar menu: History section
3. A list of all recent executions is shown

What history shows

Field	Description
Date	When it ran
Status	Completed, failed, in progress
Duration	Total execution time
Nodes executed	How many nodes were processed
Detail	Click to see the complete trace of each node

Execution queue and real-time monitoring

When you run a flow, the execution enters a queue and the system processes it in the background. The editor is not blocked: the response is immediate and you follow progress live.

• Each node lights up as it runs (started, completed, or failed).
• The Monitoring panel shows events in real time until the final event (completed, failed, or cancelled).
• When it finishes, the button returns to Run on its own and the result is saved to History.

Executions are served by priority: webhooks and API calls go first, then scheduled runs, and finally manual runs. Depending on the flow’s concurrency policy, several executions of the same flow may run at once, wait their turn, or be rejected if one is already running.

Stop an execution (Cancel)

To stop a specific execution (running or queued) without deactivating the flow:

1. While the flow is running, a red Cancel button appears next to Run
2. Click Cancel

Cancellation is soft and its effect depends on the state:

State	What cancelling does
Queued (not started yet)	Discarded: it never runs
Running	Stops between nodes: the current node finishes, the next one does not start
Already finished	No effect

Keep in mind:

• Cancelling does not undo what already ran (sent emails, written rows, or completed payments remain).
• It does not count as a failure: a cancelled execution is not retried and does not go to the error queue.
• Any user in your organization with access to the flow can cancel an execution, even one started by someone else.

Cancel vs Deactivate

Cancel stops one specific execution. Deactivate (below) prevents the flow from receiving new executions but does not affect those already running.

Deactivate a Flow

To stop a production flow:

1. Go to the Flows list
2. Click the Activate/Deactivate toggle next to the flow
3. The flow stops receiving executions

Pre-production checklist

• All nodes have complete configuration (no empty required fields)
• External API credentials are configured and tested
• Decision conditions are verified with real data
• Error paths have an alternative route (don’t leave paths without End)
• The complete flow has been tested at least once with real data
• Flow name and description are clear for the team
• Production webhooks (live URL) are configured in external services

Recommendations

• Test with real data before activating
• Review traces of the first production executions to detect issues
• Use Decision for errors: if an external node (API, DB) can fail, add an alternative path
• Monitor history for the first few days after activation
• Use FlooIA to diagnose errors quickly instead of reading logs manually

Related pages

• Create a Flow - How to build flows from scratch
• Edit a Flow - How to modify existing flows