Create a Flow
Create a Flow
Section titled “Create a Flow”Flows are the core of Floogos. Each flow is a sequence of connected nodes that automatically process data: receive information, transform it, and execute actions.
Method 1: Manual Creation (Visual Editor)
Section titled “Method 1: Manual Creation (Visual Editor)”Step 1 - Create the flow
Section titled “Step 1 - Create the flow”- In the sidebar menu, click Flows
- Click the + Create new workflow button (top right corner)
- Enter a descriptive name (e.g. “Sync Shopify to Sage”) and an optional description
- The visual editor opens with an empty canvas

The visual editor. Each box is a node; the line between them is the execution order.
Step 2 - Add the start node
Section titled “Step 2 - Add the start node”Every flow needs an entry point. Drag one of these nodes from the left panel:
| Start Node | When to use |
|---|---|
| Webhook | Receive external data in real time (Shopify, Stripe, forms) |
| Schedule | Run on scheduled times (hourly, daily, weekly) |
| FormTrigger | Start from a Floogos web form |
| DataStoreTrigger | React to DataStore changes |
| Manual / Start | For manual tests or one-time executions |
Step 3 - Add processing nodes
Section titled “Step 3 - Add processing nodes”Drag nodes from the left panel to the canvas. Main categories:
| Category | Typical Nodes | Example |
|---|---|---|
| Flow Control | Decision, Iterator, Merge, Delay | Check if an order is from Portugal |
| Data | DataStore, Variable, EditFields | Save data, transform fields |
| Connections | HTTP Request, SQL Query, MSSQL | Call APIs, query databases |
| Ecommerce | Shopify, WooCommerce, PrestaShop | Get orders, update products |
| Billing | Bill.pt, Fiskaly, Sage, Hub Fiscal | Create invoices, fiscal documents |
| Communications | Email, WhatsApp, Slack | Send notifications |
| Transformation | CSV Create, ZIP Create, JSON | Generate files, compress |
Step 4 - Connect nodes
Section titled “Step 4 - Connect nodes”- Hover over the output point (right side) of a node
- Drag the line to the input point (left side) of the next node
- The connection is created automatically
For Decision nodes: they have two outputs (True / False) that you can connect to different paths.
Step 5 - Configure each node
Section titled “Step 5 - Configure each node”- Double-click a node to open its configuration
- Fill in the required fields (marked with *)
- Use dynamic variables with the
{{field}}syntax to reference flow data:{{id}}- Field from current data{{billing_address.country_code}}- Nested fields{{@NodeName.field}}- Data from a specific node{{#1.field}}- Data from the previous node{{var.myVariable}}- Memory variables
Step 6 - Add End node
Section titled “Step 6 - Add End node”Add an End node at the end of each flow branch to ensure execution closes properly.
Step 7 - Save
Section titled “Step 7 - Save”Click the Save button (disk icon or Ctrl+S).
Method 2: Create with FlooIA (AI Assistant)
Section titled “Method 2: Create with FlooIA (AI Assistant)”FlooIA can generate complete flows from a natural language description.
How to use it
Section titled “How to use it”- In the flow editor, click the AI button in the top toolbar
- Select “Generate Workflow with AI”
- Describe what you want to automate in the text box
- FlooIA will generate the nodes, connections and basic configurations
- Review the result: generated nodes, explanation and notes
- Click Create to apply it to the canvas
Effective prompt examples
Section titled “Effective prompt examples”| Prompt | Result |
|---|---|
| ”Receive Shopify orders, check if from Portugal, create invoice in Bill.pt and save to Hub Fiscal” | Webhook + Decision + Bill.pt + HubFiscal + End |
| ”Every day at 8am, export DataStore orders as CSV and send by email” | Schedule + DataStore Filter + CSV Create + Email + End |
| ”When a form is submitted, save data to DataStore with tag ‘new’ and notify via Slack” | FormTrigger + DataStore Add + Slack + End |
Tips for better FlooIA results
Section titled “Tips for better FlooIA results”- Be specific: “Receive Shopify webhook” is better than “receive data”
- Mention services by name: “Bill.pt”, “Sage”, “Shopify”, “Slack”
- Describe conditions: “if country is PT do X, otherwise do Y”
- Indicate error handling: “if it fails, save log and send alert”
Practical Example: Shopify Invoicing Flow
Section titled “Practical Example: Shopify Invoicing Flow”Recommendations
Section titled “Recommendations”- Name your nodes descriptively (e.g. “Check country” instead of “decision_3”)
- Test first before activating - send test data to verify each step
- Use Decision for error handling: if a node can fail, add an alternative branch
- Save frequently - the editor does not auto-save
- One flow per process - smaller, clear flows are better than one giant flow
Next step
Section titled “Next step”Once created, see Execute a Flow to learn how to test and activate it.