Operation

Automations

The Automations area creates automatic rules in the format "Every time… an event happens, Do this…": send a template, resend a communication or classify it — for example, birthday message, welcome for seniority or automatic tagging of submissions.

Concepts and terms

Term (as it appears on screen)	What does it mean
Automation	A "trigger → action" ruler, displayed as a card with title, scope (My / Time / Other), activation switch, trigger and Executions and Failures counters.
Trigger ("Every time…")	The event that triggers: "An announcement for" → Sent, or "A employee" → Had a birthday / Complete N Days / Months / Years.
Conditions	Optional restrictions on the trigger (e.g. only communications from a tag or campaign; only employees from a department). Each condition is column + Is / Isn't + values; several conditions all combine together (E).
Action ("Do this…")	What happens: Create a template from scratch, Send the template, Resend the same announcement, Add to a campaign, Add to a TAG (the last two only in the announcement trigger).
Template	The content that the automation sends — created in the editor (automation mode) or chosen from existing templates.
Executions / Failures / Next submission	The three indicators of automation; Crashes have an "Error Details" pane.
Status	Active or paused (switch on card, with confirmation).

What can you do

Create automations with two triggers: sending an announcement or employee dates (birthday / completing N days, months or years)
Define the action: send a template (new or existing), resend the same announcement, or add the announcement to a campaign/TAG
Adjust sending: delay "After N Hours/Days" (announcement trigger), send time, sender and subject (email, with customization variables)
Restrict with conditions (Is / Is not) on tags, campaigns and employee fields, with pre-defined periods for dates
One-click wake/pause, inline rename, edit and delete
Monitor: list with search, filter All / Active / Inactive, ordering (Most recent / Alphabetical order); in detail, the three indicators and the Sends tab with all the announcements that the automation generated (with views and tags, opening in the announcement details)

Step by step

Create an automation

1.In the side menu, click on Automations and then on New automation. Give it a name (the title is editable at the top of the dialog).
2.Under "Every time…", choose the trigger:

An announcement is → Sent; or
An employee → Had a birthday, or Complete + number + Days/Months/Years.

1.(Optional) Click on Add Condition and restrict the audience/event: choose the column, Is or Is Not, and the values (with search). Date conditions use ready-made periods (Today, Yesterday, Last week, Last 7 days, Last 30 days, Last quarter).
2.Under "Do this...", choose the action. To submit content:

Create a template from scratch — opens the editor in automation mode; when you click on Finish, you return with the ready template; or
Send template — choose an existing template (the automation channel comes from the chosen template).

1.Complete the fields that appear: After N Hours/Days (announcement trigger), Subject (e-mail, accepts variables), Send time and Sender.
2.Click Create automation. Automation is already active.

Activate, pause and fix

1.The card switch activates/pauses (with confirmation). If any fields are missing, a warning lists what to fill in before activating ("Automation incomplete").
2.Cards with errors have a red border — See details shows the total of failures, successes and the technical error.

Track sends

1.Click the card to open `/automacoes/:id`: Executions, Failures and Next Send at the top.
2.The Sends tab lists the communications generated by the automation (title/date with status, channels, views, tags). Click to open the announcement details in a new tab; You can delete submissions (individually or in bulk, depending on your permission).
3.Edit automation reopens the form; the pencil in the title renames inline (with Undo for 5 seconds).

Delete

Trash on card → confirm: "This action is irreversible. All history will be lost."

Limits and rules

Rule	Value
Availability	Account with Automations enabled + permission to edit communications
Creation	Requires trigger, action and selected template to save; mandatory subject in the email; time and sender when applicable
Initial status	Active (pause after creating if it is not yet in effect)
Conditions	Operators only Is / Isn't; all conditions must hold together (E); incomplete lines are discarded on save (with warning)
Date Periods	Fixed: Today, Yesterday, Previous week, Last 7 days, Last 30 days, Last quarter
Channel	Defined by the chosen template (cannot be chosen separately)
Deletion	Irreversible — deletes the automation and its history
Scope of cards	The My/Team/Others badge is informative; whoever accesses the area sees and edits the automations listed

What tends to confuse

Automation is born active — when it is created, it is already valid; pause on the card if you are still testing.
The channel comes from the template: to change the channel, change the template (the channel field is read-only).
There is no execution-by-execution log — the indicators are aggregated, and the Sends tab shows the reports generated (the real trace of each send).
"Resend the same announcement" resends in the context of the announcement trigger — different from follow-up on the Announcements screen (which is manual and only for those who haven't read it).
If the template used is deleted or becomes unavailable, the automation shows "Template not available" and cannot be saved until you choose another one.
Employee status in the communication trigger evaluates the recipients of the communication sent.

Related Features

Create (editor) — editor automation mode creates the ruler template
Communications — the submissions generated appear in the list of announcements and have normal measurement
Employees — employee dates and fields used in triggers and conditions
Campaigns — add campaign action