Zapier: trigger on work order status 'Completed' only

We need Zapier to fire only when a work order hits "Completed" — not on every status change. Right now we're getting flooded with triggers on "In Progress", "On Hold", etc.

Is there a way to filter this in the FieldPulse trigger itself, or do I need to add a Zapier filter step? My team can't move forward on the customer notification workflow until we nail this down.

Parents
  • Hey Brandon — heads up, the FieldPulse Zapier trigger fires on any status change, so you'll need to handle this downstream. Two options:

    Option 1: Zapier Filter (easiest)

    Add a Filter step immediately after your trigger:

    Only continue if...  
    Status (from FieldPulse)  
    Exactly matches: Completed

    YMMV on task usage — filters count against your Zapier plan.

    Option 2: Webhook + custom logic

    If you're burning through tasks, consider switching to a webhook subscription directly. You can subscribe to work_order.status_changed and filter server-side before hitting your automation. Worth noting: this requires hosting a small endpoint or using something like Hookdeck to filter and route.

    Either way, the FieldPulse trigger itself doesn't offer status filtering at the source. I've confirmed this with their team — it's a common request though.

Reply
  • Hey Brandon — heads up, the FieldPulse Zapier trigger fires on any status change, so you'll need to handle this downstream. Two options:

    Option 1: Zapier Filter (easiest)

    Add a Filter step immediately after your trigger:

    Only continue if...  
    Status (from FieldPulse)  
    Exactly matches: Completed

    YMMV on task usage — filters count against your Zapier plan.

    Option 2: Webhook + custom logic

    If you're burning through tasks, consider switching to a webhook subscription directly. You can subscribe to work_order.status_changed and filter server-side before hitting your automation. Worth noting: this requires hosting a small endpoint or using something like Hookdeck to filter and route.

    Either way, the FieldPulse trigger itself doesn't offer status filtering at the source. I've confirmed this with their team — it's a common request though.

Children
No Data