Condition Nodes

What you can check depends on your triggerThe condition fields available to you change based on which trigger your automation uses. You can only check information that the trigger provides.
 
Here is what is available for each trigger type:
 
Contact Form Submitted:

• Form (which specific form)
• Project type

 
Brochure Submitted:

• Brochure title
• Contact email, Contact name
• Selected package IDs
• Submitted at
• Project stage, Project type, Project tags

 
Contact Created:

• Contact type (Contact or Collaborator)
• Contact tags, email, company
• Referred by
• Contact created at

 
Project Stage Changed:

• Next stage, Previous stage
• Project type, stage, tags, start date, due date
• Primary contact tags
• Referred by

 
Task Created:

• Task title, contacts, due date, priority, created at
• Project stage, type, tags

 
Task Completed:

• Task title, contacts, due date, priority, created at, completed at
• Project stage, type, tags

 
Gallery Linked:

• Album title
• Project type, tags, stage

 
Invoice Paid in Full (Payment Received):

• Payment amount, Payment date
• Invoice total, Is fully paid, Invoice template, Invoice title
• Project type, tags, stage
• Contact tags, Referred by

 
File Completed:

• File type (brochure, contract, invoice, proposal, questionnaire)
• File title, File template, Completed at
• Project type, tags, stage
• Contact tags, Contact type

 
Client Signed Contract (Contract Signed):

• Contract template, Contract title, Signed at
• Project type, tags, stage
• Contact tags, Contact type

 
Time-based triggers (Time Based, Project Date, Meeting Starts/Ends): Conditions are not supported. The builder will warn you if you try to add one.
Trigger filters vs. step conditionsThere are two places where rules can be checked in an automation:
 

1. At the trigger level: before the automation even starts running, the trigger can filter whether this event qualifies. For example, you can set a form trigger to only fire for a specific form, or a payment trigger to only fire for a specific package. If the filter does not match, the automation never begins.
2. At the step level (condition node): a condition node inside the workflow checks something after the automation has already started. If the condition does not match, that branch of the workflow stops, but the automation already ran up to that point.

 
The difference matters when you are troubleshooting:

• If your automation never ran at all → the issue is likely a trigger filter
• If it ran but skipped a step → the issue is likely a condition node