Creating Your First Automation
Automations let you create "when this happens, do that" rules so Teamo can handle repetitive work for you.
Only Admins can create or edit automations, but anyone with access to a module can trigger existing automations by performing the actions they listen for.
Opening the automation builder
Go to Automations in the navigation.
You'll land on the Create tab, where you can choose from a library of templates or select Build from scratch.
If your organization has multiple modules, you'll first choose which module the automation belongs to.
The automation builder is made up of three connected sections that read like a sentence:
When → If → Do
When: choosing a trigger
Triggers determine when an automation starts.
You can trigger automations from records, activity groups, activities, or activity details. Common triggers include creating or deleting items, changing a field, completing an activity, or completing all activities in an activity group.
Some triggers include additional configuration:
A field changes
Choose which field to monitor and, optionally, the value it must change to. Leave the value blank to trigger on any change.
On a schedule
Run the automation daily, weekly, monthly, yearly, or on selected weekdays. Choose the time and timezone using the built-in controls.
Something goes stale
Monitor records, activities, or details that haven't been updated for a specified number of days, weeks, or months.
A date condition is met
Choose a date field and define a relative condition such as Today, In 3 days, Has passed, or 3 days before the selected date.
If: adding conditions (optional)
Conditions determine whether the automation should continue after its trigger fires.
Choose the field, operator, and value to check. The available operators depend on the field type, and the value input automatically adapts—for example, showing a date picker for date fields or a dropdown for select fields.
Multiple conditions are currently combined using AND logic only. OR conditions are not yet supported.
Do: choosing actions
Actions define what happens when the automation runs.
Available actions include:
- Update a field or status
- Send a notification
- Send an email
- Create or delete records, activities, or activity details
- Call a webhook
- Add a delay before the next action
Updating a field
Set either a fixed value or use dynamic tokens that reference values from the triggering item.
Status updates currently support fixed values only.
Notifications and emails
Send messages to specific people or teams, or dynamically resolve the recipient from a User field such as the assignee.
Messages can include dynamic tokens from the triggering record.
Creating a record
Choose the destination module and configure its field values using fixed values or dynamic tokens.
Webhooks
Configure a webhook URL, including dynamic tokens if needed.
Webhooks are sent as POST requests with a JSON body. Custom HTTP methods and headers are not currently supported.
Delay
Pause the automation for a fixed amount of time, such as a number of hours or days.
Delays cannot currently be based on a date field.
Actions always run in order. If one action fails, the remaining actions do not run.
Each action can only access data from the original trigger. Actions cannot reference data created by earlier actions in the same automation, such as the ID of a newly created record.
Turning it on
There is currently no test or preview mode.
Once an automation is enabled, it immediately starts acting on live data the next time its trigger fires.
Before enabling an automation, it's worth reviewing the trigger, conditions, and actions carefully, especially if it updates or deletes data.
Limits worth knowing
- Up to 100 automations per module
- A monthly organization-wide automation run limit based on your plan
- Automation chains stop after 10 consecutive executions to prevent infinite loops
If your organization reaches its monthly run limit, Admins receive an in-app notification.
Checking what ran
Each automation includes an Execution History, where you can review every run, including its status and the record it acted on. This is useful for confirming that an automation worked or troubleshooting when it didn't.
Next Steps
Now that you've built your first automation, continue with: