Triggers are a smart way to perform automated actions in Upsales. For example, a trigger could consist of sending an notification email to the team leader when a deal has been won.
This article covers:
- When triggers can be set up
- Adding trigger criteria
- Trigger actions
- Tags in trigger actions
- Available tags
Triggers is part of the Product Workflow Automation
When triggers can be set up
Use triggers for creating, editing or removing:
- Company
- Contact
- Sales
- Appointment
- Campaign
- Agreement
- Company relation
Adding trigger criteria
You can add many variants of match criteria.
For example, imagine you want to automatically notify your sales team when a new appointment is booked.
- Select your trigger to be run on the creation of an appointment
- Add match criteria of "Appointment type" and select the type of appointment you want to send the notification on.
- Add the action "Send notification mail" and compose the email.
To exclude match criteria, use the is/is not field.
Trigger actions
The actions are performed when all of the criteria are met. Available actions are:
Create appointments and activities
Whenever the criteria for your trigger are met you have the option of creating an appointment. A useful feature to mention is the offset function. This lets you set the date of the appointment in the future by the number of days you select.
Update company
Whenever the criteria for your trigger are met you have the option of updating companies. This means adding or removing data like campaigns, categories, account managers, or the custom fields you've created for your Upsales account.
Send webhook
If you've got an external service you'd like to notify by a webhook, this is perfect.
Send notification email
This feature is meant to notify your users of important events. By default, all notification emails will be sent from no-reply@upsales.com. However, you can change the sender email address.
You can have multiple actions that are triggered at once.
Tags in trigger actions
Tags are a way of fetching dynamic data and placing them in your automatic trigger action. For example, by writing "Hello {{Client.Name}}!" in your action, it will render "Hello Company Inc!"
You can place tags on all trigger actions.
Available tags
| Client: ID | {{Client.Id}} |
| Client: Name | {{Client.Name}} |
| Client: Address | {{Client.Address}} |
| Client: Postcode | {{Client.ZipCode}} |
| Client: State | {{Client.State}} |
| Client: City | {{Client.City}} |
| Client: Phone number | {{Client.Phone}} |
| Client: Fax | {{Client.Fax}} |
| Client: Website | {{Client.Www}} |
| Client: Notes | {{Client.Notes}} |
| Client: Account manager | {{Client.UserId}} |
| Client: Account manager's name | {{Client.UserName}} |
| Client: Account manager's email | {{Client.UserEmail}} |
| Client: Registering user | {{Client.RegById}} |
| Client: Registering user's name | {{Client.RegByName}} |
| Client: Registering user's email | {{Client.RegByEmail}} |
| Client: Active | {{Client.Active}} |
| Client: Related project ID's | {{Client.RelatedProject}} |
| Client: Related client ID's | {{Client.RelatedCategory}} |
| Clear date | {{General.ClearDate}} |
| Today | {{General.Today}} |
| Now (format: yyyy-MM-dd HH:mm:ss) | {{General.Now}} |
| Current year | {{General.CurrentYear}} |
| Current user | {{General.CurrentUser}} |
| Current user's name | {{General.CurrentNameUser}} |
| Current user's email | {{General.CurrentEmailUser}} |
| Current user role | {{General.CurrentRoleUser}} |
Custom fields as tags
Any of the custom fields you have created can also be fetched as a tag. They look like this:
| Client: Name of field | {{Client.custom_<field_ID>}} |
Contact support if you need to find a custom field ID