ACTION_ID: blocker NAME: Blocker CATEGORY: Floq Tools CREDITS: 0 A breakpoint in the chain. Every row that reaches a Blocker stops there, and no step after the Blocker runs for that row. Steps above the Blocker run as usual, and so do sibling branches that do not pass through it. Use it to build and test the first part of a workflow without triggering the later (often paid) steps, or to park a workflow halfway. Distinct from `filter`: a filter decides per row, so some rows pass and some stop. A Blocker stops every row, with no condition. Reaching a Blocker is an early end of the chain on purpose, not a failure and not an unmet condition. 1. INPUTS (none. The Blocker has nothing to configure.) 2. OUTPUTS (none. Nothing downstream can reference the Blocker.) 3. HOW TO CONFIGURE There is nothing to configure. Add it with `after` set to the last step that should run; everything previously downstream of that step moves below the Blocker: POST /api/v1/workflows/{workflow_id}/sheets/{sheet_id}/actions/add { "action_id": "blocker", "after": "" } To continue past it, choose one: - Run the step right after the Blocker with Run Action and `run_next_action: true`. That step and everything below it run for the selected rows; the Blocker stays in place for later runs. - Delete the Blocker (Delete Action). The chain is relinked around it, and the next run goes straight through. Rows that already stopped there do not resume on their own; run the step after it for those. 4. KEY NOTES - Running the Blocker itself does nothing. Run Action on a Blocker returns 200 with `rows_queued: 0` and queues no rows, and its column in the Floqer app has no run menu. Run the step after it instead. - The Blocker never gets a cell status, and the steps after it are not queued for a row that stops there, so it leaves no `queued` cells behind. - In the Data tab the Blocker column shows a fixed "Blocked" label. It has no cell status, no status counts, no filter, and no run menu. Opening its settings shows only its name, which can be renamed, and its description: there is no run condition, continue on fail or output to set. - Only the branch that passes through the Blocker stops. A sibling branch that does not pass through it keeps running. - A shortcut may contain a Blocker. A shortcut run whose rows stop at the Blocker ends there at once with status `completed` and no outputs, the same as a branch that ends before the Output node, so the calling cell shows no data. This includes runs started from a published listing that is backed by a shortcut. A run started from an older published listing with no shortcut behind it is not ended: it stays running and the calling cell never finishes. - A shortcut runs the version it was published with, so adding or removing a Blocker only reaches callers after Update Shortcut. - The Blocker replaces the old workaround of a Formula node (or any action) with a run condition that never passes, or a formula that throws on purpose. Prefer the Blocker: it says what it is. Existing workarounds are not converted automatically; leave them unless the user asks to swap them. 5. WHERE IT FITS IN A WORKFLOW UPSTREAM: the steps being built and tested. Typically the cheap ones: inputs, formulas, lookups, a first enrichment. THIS ACTION: stops every row. Nothing is billed at the Blocker or below it. DOWNSTREAM: the steps held back until the upper part is proven. Typically paid enrichment, outreach (`instantly_add_to_campaign`, `reply_add_and_push_to_campaign`) and CRM writes (`hubspot_update_object`, `salesforce_update_record`). 6. WHEN TO USE Build in stages Add a Blocker right after the part being built, run a few rows, read the cells, and only then run the step after the Blocker (or delete it). Hold back writes and spend until the flow is proven Put a Blocker in front of a CRM write, an outreach push or an expensive enrichment while the upstream logic is still being checked. Park a workflow halfway Leave the upper half running on new rows while the lower half is not ready yet. 7. WHEN NOT TO USE Some rows should continue and others should stop Use `filter` (or `run_if` on a single action). A Blocker stops every row. The workflow backs a shortcut that other steps call A run that stops at the Blocker completes with no outputs, so the calling cell shows no data. Remove the Blocker once the workflow is tested. Last updated: 2026-10-01.