Building workflows
From an empty workflow to one that is tested and ready to run on a full list. New to the object model? Read Core concepts first.
1. Create a workflow
Create the workflow and name it after the motion it runs, for example LinkedIn to email plus number. The main sheet is created automatically, and you can switch between the Floq view (the step canvas) and the Data view (the rows) at any time.
The workflows list is managed like the campaigns list: folders, search, sort, drag and drop to reorder, and a right-click context menu for rename, duplicate, and archive.
2. Define the inputs
Inputs are the typed fields the workflow expects before it runs, for example Person LinkedIn URL (type: url). Keep them minimal: every input is something a runner has to provide. Inputs can be filled in the app, auto-ingested from the page when the workflow runs as a shortcut in the extension, or set programmatically over MCP.
3. Add and configure actions
Build the motion step by step. Each action takes fields from the inputs or from earlier steps' columns, and writes its results to new columns. A typical enrichment chain:
- A scrape step pulls first name, last name, company, and domain from the LinkedIn URL.
- A Work Email Waterfall takes the name, domain, and LinkedIn URL and returns a verified email.
- A phone waterfall does the same for a mobile number.
Two configuration ideas do most of the work:
- Waterfalls try multiple data providers in order and return the first or best hit, so you pay only for the provider that actually returns a result. Order providers best-first (highest hit rate and lowest cost first) and turn verification on so only good data comes through. See Actions for the catalog.
- Conditional runs skip an action for rows that don't meet a condition, so you don't spend credits enriching accounts you'd never contact.
4. Set the output node and the endpoint
- The output node marks which fields are the result of the workflow, the fields a rep sees in the extension panel or a caller reads back over MCP.
- The endpoint is what happens after the output: look up the record in your CRM and create or update it, enroll the lead in a sequence, post to Slack, or push to a campaign. Endpoints run after the result is surfaced, so people aren't left waiting on them.
5. Test before you scale
Run just a few rows first, 3 to 5 real examples, and check the results come back correct and verified before running wide.
Careful
Per-row provider calls cost credits, so never run an untested workflow across a full list. Testing on 20 rows instead of 2,000 makes mistakes cheap.
6. Ship it
A finished workflow can go three ways, and they compose:
- Keep it as a builder tool and run it from the app.
- Publish it as a shortcut so every rep can run it with one click.
- Wire its endpoint into your stack: CRM, outreach tool, Push to Campaign, or CSV.
For the cost and reliability habits that separate clean builds from credit burners, read Best practices.