Skip to main content
Saving and running workflows requires a paid plan. Free workspaces can build one in the editor but must upgrade to save or run it.
A workflow turns a repeated sequence of actions into something that runs without you: scrape a source, filter the results, enrich them, save leads, enroll into a campaign, post to a webhook. Build them in Data → Workflows.

​
Triggers

​
Limits

​
Running one over the API

Execution history is at GET /api/workflow-executions, including per-step status and output for debugging a run that did not do what you expected.

​
Inbound webhooks

Each webhook-triggered workflow gets its own URL. POST JSON to it and the payload is available to the workflow’s steps — that is how you wire ManyPI into a CRM, a form, or another automation tool.

​
Outbound webhooks

Separately, Dashboard → Webhooks notifies your systems when something happens in ManyPI — a scraper run finishing, for example — so you do not have to poll.

Integrations

Webhooks, Zapier-style polling, MCP connectors and database connections.