Workflow trigger reference

Every workflow starts with one trigger — the event that enrolls a contact and kicks off their run. This page lists the events you can pick, what fires each one, and how to pin a trigger to one specific form, stage, product, tag, or channel.

How triggers work

You pick the trigger at the top of the workflow canvas. When that event happens, every workflow that is toggled on and listening for it enrolls the contact automatically. A workflow that's switched off never fires. One workflow, one trigger — to run the same steps on two different events, build a second workflow with those steps and the other trigger.

Pin a trigger to one instance

Some triggers accept a filter so the workflow only fires for one specific instance of the event:

• Form submitted — one form (picked from a dropdown)
• Pipeline stage changed and Deal stalled — one stage
• Product purchased — one product
• Tag added — one tag
• Inbound message — one channel: sms, email, or call

Leave the filter blank and the workflow fires on every instance — every form, every stage, every product. That's how you split traffic: one workflow pinned to your "Free consult" form, another pinned to "Contact us." Note that blank really does mean every instance — a blank-filter workflow fires alongside any pinned ones, not just for the leftovers. If you change a workflow's trigger to a different event, a filter that no longer fits is cleared automatically.

The trigger list

Getting into your CRM

Engagement signals

Appointments

Pipeline & deals

Purchases

The incoming-webhook catch URL

The Incoming webhook trigger gives a workflow its own private URL that any outside app can POST a contact to — Zapier, Make, a lead vendor, your own code. Each POST adds (or updates) the contact and enrolls them, no API key required: the URL itself is the credential.

1. Set the trigger

   On the workflow canvas, set the trigger to Incoming webhook and save. The workflow's catch URL appears right on the canvas: https://app.salesteamtoolbox.com/api/wf/<token>. The token is created the first time you pick this trigger and stays the same after that, so your integrations never break.

2. Point your other app at it

   Add a webhook / HTTP POST action in Zapier or Make (or your vendor's lead-delivery settings) and paste the URL. JSON bodies and form-encoded bodies both work.

3. Send at least one identifier

   Include name, email, or phone — at least one is required, or the request is rejected. Any extra keys that match your custom fields are saved onto the contact too.

4. Done

   Each POST matches an existing contact by email or phone (updating them) or creates a new one, opens a deal for them if they don't already have one, logs the arrival on their timeline, and enrolls them in the workflow.

A minimal example:

curl -X POST https://app.salesteamtoolbox.com/api/wf/wf_YOUR_TOKEN \
  -H "Content-Type: application/json" \
  -d '{"name":"Jane Diaz","phone":"+15551230000","email":"jane@example.com"}'

The Autopilot "trigger"

Autopilot (agentic) appears in the trigger list, but it isn't an event. Picking it marks the workflow as a pipeline's Autopilot manager — the workflow the goal engine runs deals through. Its canvas is informational: Autopilot chooses its own next move per deal, so you steer it with goals in the Agent Goals panel, not with nodes.

You usually don't create this workflow yourself. The first time a deal on a pipeline goes under Autopilot — through the pipeline's AI stages, a workflow's Handoff to Autopilot step, or by turning Autopilot on in Settings — the platform creates "Autopilot: <pipeline name>" for you. You can also create one by hand: set the trigger to Autopilot, then bind the pipeline you want in the Agent Goals panel.

Autopilot requires the Pro or Agency plan. The full story — goals, stage-by-stage behavior, human takeover — is in Autopilot & Agent Goals.