What is a Mirgent workflow?
A workflow is a visual graph of triggers and actions that runs on a schedule (or on event). It's how you turn Mirgent's primitives, posting, lead discovery, AI drafting, approval, into automations bigger than any single feature.
If you've used Zapier or n8n the model is identical. Triggers fire; nodes execute downstream; approval gates pause for human review. The difference: Mirgent's nodes are social-specific (deep posting and engagement actions, not generic API glue).
Scheduling
Cron-driven scheduling for any cadence
Lead Discovery
AI-drafted lead replies before they post
AI Agents
Mix AI agents into multi-step pipelines
Analytics
Audit every run with input/output logging
Step 1: pick a trigger
Triggers determine when a workflow fires and what data is available downstream.
TIME_SCHEDULE (cron)
Standard cron expression. Daily 9am: '0 9 * * *'. Every 2 hours: '0 */2 * * *'. Mondays only: '0 9 * * 1'. Most useful for content cadence and recurring lead scans.
RSS_NEW_ITEM
Fires whenever a connected RSS feed publishes a new item. Item title, body, link, image all available as variables. Use for blog-to-social fanout.
WEBHOOK
Fires when an external system POSTs to a Mirgent-issued URL. Stripe payments, Typeform submissions, GitHub releases, anything that can send a webhook.
Start with TIME_SCHEDULE for your first workflow. It's the easiest to debug, you control exactly when it runs and can re-run on demand.
Step 2: drop action nodes
Pick from 30+ action nodes. Most-used: POST, CROSS_POST, SEARCH_LEADS, GENERATE_AI, FORMAT_TEXT, REQUEST_APPROVAL, CONDITIONAL_BRANCH.
POST → target one platform
Single-platform post with content, media, and metadata. Variables from the trigger flow in via {{ rss.title }}, {{ webhook.email }}, etc.
CROSS_POST → fan out
Same content to multiple platforms with per-platform formatting. Mirgent's AI generates platform-specific variants if your master draft is generic.
SEARCH_LEADS → lead pipeline
Run keyword search across selected platforms; downstream nodes can iterate over results, draft replies, or queue for approval.
Step 3: insert approval gates
Anywhere a public action would post, drop a REQUEST_APPROVAL node before it.
REQUEST_APPROVAL
Workflow execution pauses; the previous node's output queues for your review. You approve in the inbox; downstream nodes resume.
Configure auto-mode threshold
Per-approval node: 'auto-approve if AI confidence > 90'. Mid-confidence drafts queue; high-confidence ship automatically. Audit log distinguishes auto from human.
Multi-stage approval
Chain two REQUEST_APPROVAL nodes for editor → senior approver flows. Common in B2B teams and agencies with quality gates.
Step 4: test + ship
Click 'Test Run' to execute the workflow once with detailed logs. Identify any node that failed; fix; re-test. Once green, toggle the workflow ON, Mirgent's scheduler dispatches it on schedule.
Scheduling Guide
Calendar, kanban, and queue modes
AI Agents Guide
Configure autonomous AI workflows
Integrations
Connect RSS feeds and platforms
Lead Discovery Guide
Find leads on Twitter and Reddit
Common workflow pitfalls
Mistakes most operators make in their first 5 workflows.
- Forgetting the approval gate. Auto-mode looks faster, but a misfired workflow with no gate posts spam. Always start gated; opt into auto-mode only after 50+ successful runs.
- Variables not interpolating. Check the trigger output schema, {{ rss.title }} only works if your trigger is RSS_NEW_ITEM. Webhook variables follow the JSON shape of your incoming payload.
- Overly broad cron. '* * * * *' (every minute) is almost never right for social. Start with daily or hourly; only narrow if you have a specific need.
- No error handling. Default node behavior on failure: skip downstream nodes. For critical paths (e.g. payment → thank-you post), wrap in a CONDITIONAL_BRANCH that routes failures to a notification.
Three workflow recipes worth copying
Most-installed workflow shapes from the Mirgent template library.
RSS to multi-platform fanout
RSS_NEW_ITEM → AI_FORMAT (per-platform variants) → REQUEST_APPROVAL → CROSS_POST. The single most-used Mirgent workflow.
Lead Hunter to reply queue
TIME_SCHEDULE (hourly) → SEARCH_LEADS (keywords + score floor 70) → AI_DRAFT_REPLY → REQUEST_APPROVAL. Lead-discovery loop in one workflow.
Daily growth flywheel
TIME_SCHEDULE (Sunday 9am) → FOLLOW_FROM_PAGE (target audience) → ACCEPT_REQUESTS → UNFOLLOW_UNRECIPROCATED. Audience growth on autopilot.
Webhook → social acknowledge
WEBHOOK (Stripe new sub) → AI_DRAFT (welcome thank-you) → REQUEST_APPROVAL → POST to Twitter, LinkedIn. External system meets social distribution.
Weekly analytics digest
TIME_SCHEDULE (Sunday 9am) → FETCH_ANALYTICS → AI_SUMMARIZE → SEND_EMAIL. Skip the dashboard scroll; get a digest delivered to your inbox.
Workflows FAQ
How many workflows can I have?
Free: workflows are not included (paid feature). Pro: workflows and AI agents included. Agency: unlimited workflows and automations. Inactive (paused) workflows don't count against limits, keep templates around for situational use.
Can I version workflows?
Yes, every save creates a version snapshot. Revert to any prior version with one click; the live workflow updates immediately. Versions retained for 30 days on all plans.
What happens when a node fails?
Default: downstream nodes skip; the run is marked failed in the run history with the failing node's error visible. Wrap critical paths in CONDITIONAL_BRANCH (success path / failure path) for explicit fallback handling.
Can workflows call other workflows?
Yes via WEBHOOK trigger + INVOKE_WORKFLOW action. Useful for sub-workflows you want to reuse: 'send welcome post' as a callable from multiple parent workflows.
How do I share a workflow with my team?
Workflows are workspace-scoped. Anyone with workspace access (per role permissions) sees the same workflows. To share across workspaces, export-import as JSON.
Are there pre-built workflow templates?
Yes, 25+ in the gallery. Common shapes: RSS share, growth flywheel, lead hunter, comment auto-reply, weekly digest. Install with one click; customize variables per your workspace.