Trysquare sends nothing automatically until you ask it to. Automations are how you ask: when a record or an assignment changes, notify the right people in the app, by email, or both.
To set them up, open Admin settings and choose Automations under Configuration.
Automations are part of the Pro plan, and you need the Manage automations permission.
Creating an automation
- Click Create automation, give it a Name, and click Create.
- The builder opens. Right-click the canvas and choose Add trigger.
- Right-click again and choose Add action.
- Set up each step on its node, then click Save.
- Back on the automations list, switch it on with Enabled.
New automations start switched off, so nothing is sent while you are still building one.
Triggers
Each automation has exactly one trigger, the event that starts it:
| Trigger | Starts when |
|---|---|
| Record created | A record of the chosen Model is created |
| Record updated | A record of the chosen model is changed, optionally only when certain Fields change |
| Record deleted | A record of the chosen model is deleted |
| Assignment assigned | An assignment is given to someone |
| Assignment completed | An assignment is completed |
| Assignment status changed | An assignment moves status, optionally only when it Moves to a particular one |
To change the trigger, right-click it and choose Change trigger.
The Notify action
An automation can have several actions, each one a Notify. For each, choose:
- Channels: In-app, Email, or both. In-app notifications arrive in each person's Inbox in the sidebar.
- Recipient type:
- a particular User
- everyone with a Role
- someone from the event itself: the Assignee, the Creator, or the Actor who made the change
- a Variable from the event. Variables can only be emailed, not notified in the app.
Right-click an action and choose Delete to remove it.
Examples
- Assignment status changed, moved to Submitted: email the Reviewer role.
- Assignment assigned: notify the Assignee in the app, so they know there is work waiting.
- Record created on an Action model: notify the Contracts role in the app.
Turning automations on and off
Use the Enabled switch on the automations list. An automation needs a trigger and at least one complete action before it can be switched on.
Run history
Each time an automation runs, it is recorded for 30 days. Click Run history on the automations page, or Recent runs in the builder, to see each run's trigger, status and duration. Filter by status (Succeeded, Failed, Running or Pending) or by automation. Open a run to see its steps and, if it failed, why.
What automations do not do yet
Automations notify people. They do not branch on conditions, update records, start assignments or run on a schedule.