Automations 101: triggers, actions, targets, variables
In Dailybot, an automation is an operation comprised of triggers and actions that help you automate something at work. Learn more about the concepts that you’ll find when implementing one in the web app:
Contents
1️⃣ Triggers
2️⃣ Actions
3️⃣ Target
4️⃣ Variables
5️⃣ Commands (new!)
1️⃣ Triggers
Triggers are events that tell Dailybot to do something. When an automation is “triggered,” some event that you previously chose just happened, and Dailybot noticed. Essentially, all automations start with an event that triggers an expected action.
⏰IF something happens (your event) ⚡ tell Dailybot to DO something else (expected action)
Dailybot comes with 15 built-in triggers to help you build automations. Let’s see what these are:
User runs a shortcut/command
You can use one of the custom commands you’ve created to trigger an automation.
Scheduled Task is triggered
Use cron expressions to trigger a new automation in the time or frequency you desire.
User completes a check-in
Every time a check-in participant completes their report by chat or web, this event will be triggered.
User reports a blocker in a check-in
Every time a check-in participant completes their report by chat or web, AND their report contains a blocker, this event will be triggered.
Form received new response/record
Every time a user fills out one of your forms, this event will be triggered.
Form record is updated
Every time a user edits a response they previously gave you in one of your forms, this event will be triggered.
Form record is approved
Every time a user fills out one of your forms with approval flow, and one of the selected people approves their request, this event will be triggered.
Form record is denied
Every time a user fills out one of your forms with approval flow, and one of the selected people denies their request, this event will be triggered.
Another Automation has finished
You can nest your automations and use the end of one automation to trigger another.
Activity logged in Dailybot
With the help of our native integrations, you can ask Dailybot to trigger an automation every time it captures new activity from one of these integrations.
Event sent to Automation Trigger API
Use the Automation API trigger to send any JSON event to Dailybot to start a new automation.
Kudos given by any person
This event will trigger an automation any time someone gives kudos, regardless of the destination, message, or team value you choose.
User is added to this organization
Every time a new user is activated in your organization, this event will be triggered.
User is added to a team
Every time someone adds someone else to a team in your organization, this event will be triggered.
User is removed from a team
Every time someone removes someone else from a team in your organization, this event will be triggered.
2️⃣ Actions
Actions are operations that you can run after your initial trigger. When an automation is “triggered,” Dailybot prepares the list of actions that you previously chose to execute it, in order, until the full process is completed.
⏰ Every time your chosen event is triggered ⚡ Dailybot performs a set of actions
Dailybot comes with 5 built-in actions to help you automate processes:
Send a chat message – sends a message to user DMs or channels.
Send an email message – sends an email to Dailybot users or external email addresses.
Trigger custom command – runs one of your custom commands and sends the output to specific channels or DMs.
Select random Form record – picks a random entry from one of your forms.
Insert Form record – creates a new entry in the form of your choice.
3️⃣ Target
Targets are the places and people that are part of your automation. When an automation is “triggered,” you can choose the specific places where you want your action to happen, as well as the people that should be impacted by said action.
Channels / spaces – send actions to specific channels (both public and private). In private channels, Dailybot must be invited first.
People or teams – pre-select active Dailybot members as well as teams.
User involved in this flow – dynamic; either the automation owner or the user who triggered it.
Custom emails – send emails to external (or not-email-identified) Dailybot users.
4️⃣ Variables
Variables are placeholders you can use in your messages to dynamically introduce a piece of information to your automation. They have the form {{variable_name}} and you can pull up the list of working variables by simply typing {{ in the message box of your automation action.
5️⃣ Commands are now part of Automations
You can now also use the “User intent is recognized” trigger inside the Automation Builder. This trigger listens to what people say to Dailybot (previously known as a command), and based on that intent it starts multi-step workflows of your choosing. It’s just like the previous standalone “commands” feature, but now with the full power to chain actions, conditions, and other Dailybot steps in a single flow.
This change is part of our ongoing effort to unify everything into one automation platform for team ops, so instead of separate features, you build and manage all your intent-based workflows from one place.
