[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-filter-step::en":3,"gloss-cluster-filter-step::en":26,"gloss-next-filter-step::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"filter-step","no-code","Filter Step","A filter step is a checkpoint placed between two steps of an automation that only lets the run continue when its condition is met — otherwise the run stops right there. Zapier calls it \"Filter by Zapier\"; Make lets you set a filter on the link between any two modules; n8n has an \"IF\"\u002F\"Filter\" node. Example: a \"new email\" trigger fires on every message, but a filter after it says \"only continue if the subject contains 'invoice',\" so the rest of the workflow runs for invoices only. Why it matters: triggers are often noisy — they fire for every new record — and a filter is how you narrow that firehose to just the items worth acting on, saving operations\u002Ftasks and avoiding unwanted actions. Practical note: a filter halts a single run rather than branching it (that's a router's job). Under usage-based pricing, filtering early — right after the trigger, before any paid action steps — keeps failed-condition runs cheap because they stop before doing billable work.","A filter step is a checkpoint between two automation steps: the run continues only when its condition is met, and stops silently when it isn't.",null,[11,14,17,20,23],{"slug":12,"name":13},"conditional-logic","Conditional Logic",{"slug":15,"name":16},"router","Router",{"slug":18,"name":19},"scenario","Scenario",{"slug":21,"name":22},"trigger","Trigger",{"slug":24,"name":25},"zapier","Zapier",[27,31,35,38,41,44,47,50,53,56,59,62],{"slug":28,"category":5,"name":29,"updated_at":30},"action","Action","2026-08-24T02:46:36+00:00",{"slug":32,"category":5,"name":33,"updated_at":34},"aggregator","Aggregator","2026-08-24T02:46:37+00:00",{"slug":36,"category":5,"name":37,"updated_at":30},"airtable","Airtable",{"slug":39,"category":5,"name":40,"updated_at":30},"api","API",{"slug":42,"category":5,"name":43,"updated_at":30},"api-key","API Key",{"slug":45,"category":5,"name":46,"updated_at":34},"approval-workflow","Approval Workflow",{"slug":48,"category":5,"name":49,"updated_at":30},"automation-platform","Automation Platform",{"slug":51,"category":5,"name":52,"updated_at":30},"automation-recipe","Automation Recipe",{"slug":54,"category":5,"name":55,"updated_at":30},"backend-as-a-service","Backend-as-a-Service (BaaS)",{"slug":57,"category":5,"name":58,"updated_at":34},"backfill","Backfill",{"slug":60,"category":5,"name":61,"updated_at":30},"bubble","Bubble",{"slug":63,"category":5,"name":64,"updated_at":30},"business-logic","Business Logic"]