What’s New
The New Lead Assigned Zapier trigger now has three optional pickers in the Zap editor:
- Assignee — only fire when a lead is assigned to this user.
- Pond — only fire when the assignee is a member of this pond.
- Group — only fire when the assignee is a member of this group.
Combining filters narrows the match (AND). Leave every picker blank to fire on any user assignment on your team — the same broad behavior as before for newly created Zaps that don’t pick anything.
Why It Matters
The trigger used to silently bind to the user who connected the Zapier integration: if the lead was assigned to anyone else (very common with pond and group rotations), the Zap didn’t fire and looked broken. With the new pickers, partners running pond/group rotation can build a single Zap that watches the rotation pool and fires reliably for every routed lead — no more “the Zap stopped working” support tickets when a new rep joins the pond.
Heads Up for Existing Zaps
Pre-existing New Lead Assigned Zaps keep their original behavior — they continue to fire only for assignments to the user who connected Zapier. To opt into the new pickers, edit the Zap, pick the filters you want (or leave them blank to fire for any assignee on the team), and save. The new filters take effect the next time the Zap is enabled.
For Partner Integrations
Subscribing to contact.assigned with a malformed assignee_user_id, pond_id, or group_id returns 422 Unprocessable Entity rather than silently subscribing with no filter. Send a valid UUID — or omit the parameter to fire for any assignee on the team.