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 - Manual run (you click Run), Schedule (on the days you choose), or Advanced trigger (a secure link your form, CRM, or another app calls).
- 2.
Condition
Branches the flow on a value you care about with "Only if" - for example a lead score threshold, geography, or pricing tier.
- 3.
Action
Does the work - draft a social post, generate an image, send an email, send a Slack update, add a contact to your CRM.
- 4.
Delay
Holds the flow for a number of days or until a chosen date - 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
New integrations land via the Changelog.
- Social
- LinkedIn, Facebook, and X (Instagram once Meta’s review is done)
- Email + CRM
- Send email, Slack updates, HubSpot, Mailchimp, Klaviyo, SendGrid, Customer.io, Airtable, and Google Sheets, plus "Send to another app" for Make, Zapier, n8n, or any tool with a webhook link
- Triggers
- Manual run, Schedule, and Advanced trigger
- Browse the full directory of supported tools at mitpo.io/integrations.
Common patterns
Most effective workflows fall into a small set of patterns. Start from a recipe rather than building from scratch: six are ready to run today and four more are marked coming soon.
Three recipes that earn their keep fast
Each can draft the work and wait in Needs review for your okay before anything goes out.
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 "Test run" to watch a workflow behave before you switch it to Live.

