Trigger reference (the "when")

A trigger is the event that starts an automation. Set it by clicking the Trigger card and choosing from the When dropdown in the Node Configuration panel. A short description under the dropdown confirms what the trigger means.

One moment, one trigger. Not sure which to pick? Say the sentence out loud: "When ___, do ___." Whatever fills the first blank is your trigger.

Projects

• Project created — a new project is added.

• Project phase changed — a project moves to a new phase.

• Project status changed — a project's status changes (e.g. to Active or On Hold).

Products

• Product added to project

• Product approved by client / Product declined by client

• Product status changed — a product moves to a new status.

• Product status unchanged for X days — a product has sat in the same status for the number of days you set.

Tasks

• Task created, Task status changed, Task completed, Task assigned

Team & contacts

• Team member added — someone joins your studio.

• Contact added — a new contact/client is created.

Forms

• Form submitted — someone submits one of your forms. Choose a specific form or any form.

Leads

• Lead created (manually) / Lead created (from a form)

• Lead stage changed — a lead moves to a new pipeline stage.

• Lead status changed — a lead is marked Open, Won or Lost.

Time tracking

• Time logged — a time entry is recorded.

• Time threshold reached — someone logs more than a set number of hours within a window you define.

Contracts

• Contract sent, Contract viewed, Contract signed (all parties have signed), Contract declined

Estimates

• Estimate created, Estimate viewed, Estimate approved

Invoices & payments

• Invoice created, Invoice paid, Payment made

Procurement intelligence

• Item received — an ordered item is marked received.

• Claim window elapsed — a set share of the vendor's damage/shortage claim window has passed.

• Silent shipment — an item's ship date has passed with no tracking update.

• Lead-time drift — a vendor's expected delivery has slipped later than quoted.

• Install confidence dropped — the likelihood of hitting a project's install date has fallen below a threshold.

Budget intelligence

• Change orders exceed budget % — approved change orders pass a percentage of the contracted budget.

• Spec over allowance — items specified under an allowance run over it by more than you allow.

Asana (if connected)

• Asana task created / Asana task completed — mirror activity from a linked Asana project.