Action reference
The 4 things an automation rule can do.
A rule can have multiple actions — they run in order, and one failing doesn't stop the rest (see how it works).
add_tag
Attaches a tag to the triggering contact, creating the tag first if it doesn't already exist by that name.
Fields: Tag name.
add_to_list
Subscribes the triggering contact to a newsletter list — same as adding a subscriber
from the dashboard, so it skips double opt-in
and goes straight to SUBSCRIBED.
Fields: List (pick from your existing lists).
create_deal
Creates a new deal for the triggering contact in a chosen pipeline.
Fields:
- Pipeline (required).
- Deal name — defaults to
Deal for <contact's email>if left blank. - Value ($) — optional.
There's no stage picker for this action — the deal always lands in the pipeline's
first stage (the same one new deals default to when nothing else is specified).
If you need it to land somewhere else, move it manually or with a follow-up
automation on deal.created.
send_webhook
Sends the triggering event's data as a JSON POST to a URL you specify — a one-off, per-rule webhook, distinct from the account-wide webhooks you register under Settings.
Fields: Webhook URL.
This is the action to reach for when you want to notify something outside Threadliner (Slack via an incoming webhook URL, a custom endpoint, Zapier's Catch Hook) for a specific rule, without registering a standing webhook subscription for every event of that type. See example recipes for a concrete use.
Last updated on