Example recipes
Realistic automation rules built from the real trigger, condition, and action types.
Each of these is buildable exactly as described, using only the triggers, conditions, and actions covered in the trigger, condition, and action references.
Tag every new contact as a lead
When contact.created → Actions: add_tag → Tag name lead.
No conditions needed — this runs for every new contact, however they were created.
Add new contacts to a welcome list
When contact.created → Actions: add_to_list → List "Welcome series".
Combine with the previous recipe by adding a second action to the same rule — one trigger firing two actions.
Create a deal when someone submits your "Book a demo" form
When form.submitted → Conditions: payload.formId equals <that form's ID> → Actions: create_deal → Pipeline "Sales", Deal name left blank (defaults to
the contact's email).
Find a form's ID in its URL under Forms (/forms/<id>).
Tag contacts who confirm their newsletter subscription
When subscriber.confirmed → Actions: add_tag → Tag name
newsletter-subscriber.
Since subscriber.confirmed also fires for subscribers added directly from the
dashboard (see double opt-in), this tags both —
if you only want people who confirmed via the public signup flow, there's no condition
that distinguishes the two paths; you'd need to track that separately.
Flag contacts who unsubscribe
When subscriber.unsubscribed → Actions: add_tag → Tag name unsubscribed.
Useful as a simple segment to exclude from future list-building efforts.
Notify an external system when a deal is won
When deal.stage_changed → Conditions: payload.status equals WON →
Actions: send_webhook → Webhook URL pointing at a Zapier "Catch Hook" (see
Webhooks with Zapier) or your own endpoint.
This is the send_webhook action (per-rule, fires only for deals matching this
condition) rather than a standing webhook subscription
(account-wide, fires for every deal.stage_changed event regardless of status) — worth
picking deliberately between the two depending on whether you want the filtering done
in Threadliner or on the receiving end.
Create a deal from a specific pipeline for every new contact
When contact.created → Actions: create_deal → Pipeline "Sales".
Useful if every new contact should start somewhere in your pipeline by default, rather than deals only being created when someone deliberately adds one.
Last updated on