Connectors, Sheets as a Queue, and Approvals

There's no "loop over every row" step — instead, a workflow finds one pending row per run (a Google Sheets "find row" action matching a status column), processes it, writes the result back, and stops. Put that workflow on a recurring schedule and each run naturally advances to whichever row is next — the sheet is the queue, not the workflow.

• →The Sheet → LinkedIn Pipeline template is a full working example of this pattern — open it and look at the Pipeline tab even if you're building something different
• →Google Sheets can also format a range (background color, bold) — a common pattern is turning a row green on success and red on failure so the sheet itself shows status at a glance

A workflow can send an approval request straight to a Telegram chat with Approve and Reject buttons on the message — no need to open Muqira to act on it. Connect Telegram, then in Connectors → Telegram → Setup, generate the webhook once per bot. After that, any workflow's "Send approval request" step will route a tap on either button straight back to that paused run.

• →There's no Regenerate button in Telegram — that needs a workflow to jump back to an earlier step, which is a different mechanism (see the polling pattern above) than the pause-and-resume a Telegram approval uses
• →Approving from Telegram and approving from the dashboard do the exact same thing on the same run — use whichever's in front of you

Not every platform's API can do everything its UI can. Notion has no permanent delete — "delete" a page and it's archived, exactly like using Notion's own trash. Airtable's API has no cell-coloring/formatting endpoint at all, so a workflow marks a record's status with a field value instead of a color. Reddit's posting API works correctly, but Reddit's own app-approval process can take Reddit itself weeks to grant — that wait has nothing to do with Muqira.

• →If a step's error mentions the connector rejected the request rather than Muqira, check that platform's own docs first — most of these are the third party's limit, not ours
• →Medium and Quora aren't offered as connectors on purpose: Medium's publishing API no longer issues new integration tokens, and Quora has never had a public API to post through

Open the workflow → History tab → click any run to see its Output tab: every step's result, in order, including which branch a conditional step actually took. If a step references an earlier step's value and it came out blank, check the exact key — {{ctx.step_key.field}} has to match that step's own key exactly, including whether the value is nested (an integration step) or flat (an AI step's own text output).

• →A run stuck as "queued" with no error is usually just waiting — on a delay step's timer, or on a human_approval step for someone to act
• →If a workflow's amber "Setup needed" banner is still showing, that's telling you exactly which fields still have template placeholders in them, with a button that jumps straight to fixing each one