Muqira Flow Quick Start Guide

From Dashboard → Workflows, pick a project (if you have more than one) and click a template card — each one is a complete, working workflow you can use as-is or edit. "+ Add step" on any workflow's Pipeline tab lets you build from an empty workflow too, one step at a time, up to 20 steps.

• →The Sheet → LinkedIn Pipeline template runs a Google Sheet as a content queue — a good one to open first even if you don't plan to use it, just to see a full real workflow end to end
• →Templates that publish to external accounts (LinkedIn, X, Slack) auto-schedule themselves on creation — check the Trigger tab if you don't want that

Every workflow has one Trigger control with three tabs: Manual (only runs when you click Run), Schedule (a recurring cron expression, e.g. every 15 minutes), or Webhook (a unique URL any external system can call to start a run). The tab with a green dot shows which one is currently active.

• →Switching to Schedule shows a plain 5-field cron box, not a calendar picker — "*/15 * * * *" means every 15 minutes
• →Webhook URLs are shown in full only once, right when you generate or rotate them — copy it immediately, since reloading the page won't show it again

Each step type gets its own real form, not a JSON box — an AI step shows prompt and model fields, an integration step shows a connector dropdown then an action dropdown then that action's own labeled fields, a branching step shows condition/value/jump-target fields. Every step's output becomes available to later steps via {{ctx.step_key.field}}.

• →Use ↑ / ↓ on any step to reorder it, or ✕ to delete it — deleting warns you if another step jumps to it by key
• →A branching step can jump backward to an earlier step, not just forward — that's what lets a workflow poll ("wait, check again, wait, check again") without a dedicated loop feature

Click Connectors in the sidebar (it's its own top-level item, not nested under Settings) and connect whichever provider a step needs. Once connected, that credential is available to every workflow in the org — you don't reconnect per workflow. If a step's connector isn't connected yet, the step editor shows a clear warning right there, not just a failure when the workflow runs.

• →Connectors keep growing — Google Sheets alone covers read, get, find, update, append, clear, delete, and format, enough to run a spreadsheet as a real workflow queue
• →Credentials are encrypted at rest and never exposed in workflow run output

Use "Run Workflow" to execute it once and inspect every step's output in the Output tab before trusting a schedule or webhook to fire it unattended. Once you're confident, leave the Trigger tab set to Schedule or Webhook — there's no separate "activate" switch, the trigger being set is what makes it live.

• →A run paused on a human_approval step shows Approve/Reject buttons right there in the Run tab — no need to dig through history to find a pending approval
• →Check the History tab after your first live run — every execution is listed with its full step-by-step output for debugging