Workflows: recipes as a canvas
A workflow is a recipe drawn as a row of nodes, the way n8n or Zapier draw an automation. Each node is one step of the pipeline, and clicking a node edits that step. Nothing about the engine changes: a workflow is saved as an ordinary recipe, so openleads recipe run <name> and the scheduler run it exactly the same way.
openleads web # then open Workflows (under Automate) in the sidebar#The nodes
| Node | What it does | Settings |
|---|---|---|
| Trigger | When the workflow runs | A schedule in plain English or cron (weekdays 09:00, every 2h, 0 9 * * 1-5), or manual only |
| Find leads | Searches the sources that fit your sentence | Audience (the sentence) and how many leads |
| Verify | Scores every address and branches on the tier | Safe only, or safe and risky |
| Write | Drafts a plain-text email per safe lead | What you are offering, in one line |
| Send | Sends inside your warmup cap | On or off, and whether to start the follow-up sequence |
| Review | Holds risky leads so nothing is sent by accident | Always on |
| Export | Pushes the leads somewhere else | CSV, JSON, Google Sheets, a webhook (n8n, Zapier, Make), Notion, or Airtable |
Nodes that are switched off are drawn dashed, and the run skips them.
#Build one
- Open Workflows and click New workflow.
- Click Find leads and type who you want, for example
marketing agencies in Miami. - Click Trigger and type a schedule, or leave it on manual.
- Click Write and describe your offer in one line.
- Leave Send off for the first few runs. Turn it on once the drafts look right.
- Click Save.
#Copy one
Click Duplicate beside Delete to open an unsaved copy of the current workflow, including your latest edits and export settings. The name starts with <name>-copy; if that name exists, it uses <name>-copy-2, then -3, and so on. You can edit the name and audience before saving. An untitled workflow becomes workflow-copy. The original stays unchanged, and the copy starts with no run history.
Duplicating does not save or run anything. Click Save to persist the copy, or Test run to save it and start a dry run. Duplicate is unavailable while a save or test run is in progress.
#Test it
Test run executes the whole workflow as a dry run. The nodes light up as each step finishes, the counts appear on each node, and the run log shows every phase. No email is sent during a test run, even with Send switched on.
Scheduled runs are real runs. If Send is on, the scheduler sends inside your daily cap. Install the scheduler once with:
openleads schedule onSee Timed runs for how schedules are checked and what happens when your laptop was asleep.
#Push leads into n8n or Zapier
Set Export to webhook and paste your n8n or Zapier webhook URL as the target. Every run POSTs the leads as newline-delimited JSON, so the rest of your automation can pick them up from there.
Note: the dashboard only listens on
127.0.0.1. A webhook export is the one place where lead data leaves your machine, and only to the URL you typed.