How a workflow is shaped
Every workflow has one trigger and one or more actions. Optional conditions branch the flow. Optional delays sit between steps so a post does not fire the instant a lead converts.
- 1.
Trigger
Starts the flow — a time schedule, a form submission, a CRM change, or an external webhook.
- 2.
Condition
Branches the flow on a value you care about — lead score threshold, geography, pricing tier.
- 3.
Action
Does the work — generate content, draft an email, create a post, ping Slack, update a record.
- 4.
Delay
Holds the flow for a duration or until a specific time — useful for drip sequences and off-hours sending.

What connects
MITPO integrates with the tools most early-stage teams already use. The current list favors breadth over depth — enough to get a real workflow running without forcing a rewrite of your stack.
Categories available today
Each category has 2–5 providers. New integrations land via the Changelog.
- Social
- Bluesky, LinkedIn, Meta (Facebook + Instagram)
- Email + CRM
- Webhooks to any tool that accepts an inbound hook; native Slack + Discord notifications
- Data + triggers
- Schedule (cron), webhook inbound, scheduled prompt
- 27+ integrations available in the picker as of the last changelog.
Common patterns
Most effective workflows fall into a small set of patterns. Use these as templates rather than building from scratch.
Three workflows that earn their keep fast
Each of these can be built in under ten minutes and pays back across the first week.
When not to automate
Workflows amplify what you already do. If a process is unclear or one-off, resist the urge to automate it first. Automating a broken process makes the output worse, faster.
- First prove the workflow manually — if it works consistently by hand, then automate.
- Do not automate creative decisions that require judgment (e.g. final approval before a big launch).
- Use the "dry run" mode to watch a workflow behave before you let it write to the world.


