Muqira Flow

Muqira Flow Quick Start Guide

Build your first workflow, choose a trigger, add action steps, connect a third-party integration, and test before going live.

5 steps~15 minFree tier available

Create your first workflow

~2 min

From Dashboard → Workflows → New Workflow, give it a name and description. You'll land in the visual builder — a canvas where you drag and connect trigger and action blocks to define what happens, and when.

Name workflows descriptively ("New lead → Slack alert") — it pays off once you have a dozen of them
Workflows start paused by default so nothing runs until you explicitly activate it

Choose your trigger

~3 min

Every workflow starts with a trigger — a scheduled time (cron), an incoming webhook, a new record in a connected app (e.g. a new contact form submission), or a manual run button. Select the trigger type and configure its specifics in the side panel.

Cron triggers use standard cron syntax — the builder shows you a plain-English preview so you can verify it's set up the way you intend
Webhook triggers give you a unique URL to call from any external system

Add action steps

~5 min

After the trigger, add one or more action steps — generate AI content, send an email, post to a connector (Slack, Notion, Google Sheets, and 18 others), or branch with a conditional. Each step's output is available as a variable to the next step.

Use conditional branches to route a workflow differently based on data from an earlier step (e.g. only post to Slack if a value exceeds a threshold)
Keep early workflows to 2–3 steps; complexity is easy to add later once you trust the basics

Connect an integration

~5 min

If a step needs a third-party connector, click "Connect" on that step and follow the provider's auth flow (OAuth for most, API key for others). Once connected, the credential is available to any workflow — you don't need to reconnect per workflow.

21 connectors are currently supported, spanning social, CMS, productivity, and e-commerce tools
Credentials are encrypted at rest and never exposed in workflow logs

Test, then activate

~3 min

Use "Run Test" to execute the workflow once with sample or live data and inspect the output of every step before it goes live. Once you're confident it behaves as expected, flip the workflow from Paused to Active.

Test runs don't count against your monthly workflow-run quota
Check the run history log after activating — it shows every execution with full step-by-step output for debugging

FAQ

Common questions.

What triggers does Muqira Flow support?

Scheduled (cron), webhook, manual run, and event-based triggers from connected apps (such as a new row in Google Sheets or a new card in Trello).

Does a failed workflow step stop the whole run?

By default, yes — a failed step halts the run and is logged with the error so you can fix and re-run it. You can configure specific steps to fail silently and continue if that fits your use case.

Can I use AI inside a workflow?

Yes — add a Muqira AI step anywhere in the flow to generate or transform content, and pass its output into the next step like any other variable.

Is there a limit on how many workflows I can build?

The number of active workflows and monthly run volume depend on your plan. Building and testing workflows in Paused state doesn't count against your run quota.