Automations help you respond automatically when something happens in a space. You can welcome new members, collect a survey, add people to another space, send messages, update member properties, invite people to a calendar event, call a webhook, and build branches based on conditions.
Each automation has a starting event, one or more actions, an Active or Inactive state, and a report where you can review what happened.
Before you start
You need manager access to create, edit, or review automations for a space.
Some actions depend on your account access, plan, or connected integrations. For example, inviting someone to a Google Calendar event requires an active Google connection.
Create anything the automation needs first, such as destination spaces, surveys, certificates, member properties, or calendar events.
Create an automation
Open the space where the automation should run.
Go to Manage, then open Automations.
Select New automation.
Choose the starting event. Some events ask for details before the builder opens, such as which survey, form, or member activity should start the automation.
In the builder, choose Add a step here and select the first action.
Configure the action, save it, then add any additional steps you need.
Actions you can add
Depending on the trigger and your account access, Sutra can run actions such as:
Send email or send direct message
Add person to a space, remove member from a space, or remove contact
Wait for a period of time before the next step runs
Set member status to pending or survey person on join
Set a member property, issue a certificate, invite to Google Calendar, or call a webhook
Add a condition or go to another step to create branches in the journey
Activate and monitor the automation
Keep an automation Inactive while you are still building it. When it is ready, turn it Active so new matching events can enter the automation.
Active automations accept new people. People already in progress continue from the saved state of the automation. If you remove an automation, unfinished runs are canceled.
Use the Report view to see statuses, counts, email results, and each person’s recorded automation history.
Good to know
Most starting events can only be used once per space. Some configured events, such as specific survey submissions, can be used more than once.
Wait steps run asynchronously, so timing should be treated as approximate rather than exact to the second.
Disabled actions are skipped until they are enabled again.
Editing an automation does not restart people who already completed it.
Troubleshooting
I do not see the action I need. Action availability can depend on the starting event, your permissions, account access, or an integration connection.
The automation did not run for someone. Confirm that the automation was Active before the person matched the starting event. Automations usually do not apply retroactively.
I edited a live automation. Future runs use the latest version. People already in progress may continue from their current saved step.