Skip to content

Create an automation

Create an automation from the list, then drag a trigger from the node palette onto the builder canvas. A trigger defines when AgencyTitan starts a run.

Agency team members who design automations. Requires View Automations, Create Automations, and Edit Automations. Without Create Automations, New Automation does not appear.

  • Decide what event or schedule should start the automation.
  • Identify the record fields, users, departments, or connected integrations the automation needs.
  • Read Automations overview if draft, published, active, and inactive states are new to you.
  1. Open Settings, then Automations ( /settings/automations (opens in new tab) ).
  2. Select New Automation.
  3. Enter Automation Name.
  4. Optionally enter a description so teammates can understand its purpose from the list.
  5. Select Create Automation.

AgencyTitan opens the Builder with a draft and an empty canvas.

Expand a category under TRIGGERS, then drag the trigger onto the canvas.

Published automation builder with the Tasks trigger category expanded to show the available task event triggers
View full size

The current builder groups triggers as follows:

CategoryTrigger examples shown in the builder
GeneralInbound Webhook, On a Schedule, Button/Link Clicked
ClientsClient Created, Client Updated, Client Merged, client notes, client programs, and billing events
Custom ObjectsCustom Object Record Created, Updated, or Deleted
FormsForm Submission Ready, Rejected, or Arrived
IntegrationsEvents from available Mailgun, Google Workspace, Facebook Pages, Instagram, HighLevel, Twilio, Zoom, and Stripe connections
SOPsSOP Updated, Published, Archived, or Feedback Received
TasksTask Created, Updated, Stage Changed, Stale Stage, Completed, or Merged
TicketsTicket creation, updates, status, priority, assignment, messages, inbox moves, SLA events, review events, and linked-task events
EscalationsEscalation Created, Updated, Status Changed, Reassigned, or Comment Added
TrainingCourse and assessment completion, pass, fail, or submission events
UsersUser Invited or User Setup Completed

Integration choices can differ by agency and connection state. Search Nodes when you know the trigger name but not its category.

  1. Select the trigger node.
  2. Optionally replace its label with a name that explains the event.
  3. Complete any trigger-specific settings. For example, On a Schedule requires a schedule type and timezone.
  4. Select Save in the configuration panel.

The issue counter in the builder toolbar lists missing or invalid required settings. Resolve those issues before publishing.

Use trigger conditions when the automation should start for only some matching events.

  1. Open the trigger node and select Add condition.
  2. Choose Standard Condition for a field on the trigger record, or Related-Record Condition to traverse to a related record.
  3. Select a field and comparison.
  4. Choose Fixed value or Compare to field, then complete the value.
  5. Select Done.
  6. Add more conditions or a group when needed.
  7. Choose whether the group should match All or Any conditions.
  8. Select Save on the trigger panel, then Save Draft in the toolbar.
Add condition dialog for a Task Stage Changed trigger with Task Status, Equals, and In Progress configured
View full size

Reopen the trigger after saving and confirm each condition still appears before you publish.

  • The new automation appears in the list as a draft.
  • The builder shows at least one configured trigger node.
  • The toolbar issue count falls as required settings are completed.
  • Saved conditions appear when you reopen the trigger.
SymptomLikely causeWhat to do
New Automation is missingYou lack Create AutomationsAsk a workspace owner to grant Create Automations
Trigger is not in the paletteIt is unavailable in this automation context or connection stateSearch Nodes, check its category, and confirm the required integration is available
Save stays disabledA required trigger setting is incompleteReview the configuration errors in the panel
Condition does not appear after reopening the triggerThe condition did not persist in the draftAdd it again, select Done, save the node, select Save Draft, and submit a ticket if it disappears again
Publish control is blockedThe issue counter has one or more validation errorsOpen the issue counter and resolve every listed item