The channel delivers the alert. The task keeps the evidence and next steps.
Sample data
EXAMPLE WORKFLOW
A condition, a channel and continued ownership.
Connect confirmed page unavailability with the right response. A rule links the condition to an owner, a notification channel and an optional action, giving the team a clear path from signal to resolution.
01
Separate an important condition from a single observation.
Define what the process should confirm, which object the situation concerns and who owns the response. For a page, the active-ad context matters rather than just the occurrence of one error.
Step outcomeA rule condition and an identified response owner.
02
Choose the notification and any action.
Select email, SMS or a Twilio call. A rule can trigger a notification, a supported action or both. The recipient, channel and scope of change need to match the significance of the event.
Step outcomeA configured response path with the required connections.
03
Return to the task and verify the situation.
The notified person opens the issue, reviews the data and checks available solutions. Sending an alert does not fix the problem; an action still needs an outcome review and ownership of any remaining work.
Step outcomeA task with context and the next step towards resolution.
01
CONDITION
Define what deserves an interruption.
Choose a process and a condition that needs a response. Match ownership and notification channels to the significance of the situation.
Process threshold and schedule
Task owner
Rule trigger condition
02
CHANNEL
Email, SMS or a phone call.
Notifications can arrive by email, SMS or a Twilio call. Configure the required connections and numbers; provider availability and costs depend on the chosen channel.
Email to your team
SMS for an important change
Phone calls through Twilio
03
FOLLOW-THROUGH
An alert leads to action.
Open a task with data and a next step. A process can also trigger a configured action; notifications and execution have their own scope and history.
A task with context
Manual, AI or automated work
Verification of the resolution
CHOOSE HOW TO WORK
Decisions to make before enabling a rule.
01
The event’s significance determines the channel.
Email can support reviewing issues, while SMS or a call can draw attention to something important. This is an organisational decision: define who receives the message and what they should do next instead of choosing the loudest channel for everything.
02
Notifications and actions have separate scopes.
Notify a person without changing a campaign, or combine a message with an allowed action. Permission to send a message does not automatically grant permission to modify an ad. Each integration needs the right configuration.
03
Task data matters more than the alarm alone.
The recipient needs to know the project and object, which condition was met and what to check next. The combined portfolio alert view helps the team maintain a shared view of issues requiring a response.
BEFORE YOU START
Good to know.
Does automation wait for someone to open the task?
No. A configured rule can trigger a supported action or notification once the condition is confirmed, without a person opening the task. You set the scope and permissions in advance. You can also start with an alert alone and leave the choice of action to the owner.
Are SMS messages and phone calls free?
Do not assume so. Channels need configuration, and cost and availability depend on the provider and usage. Before enabling them, establish the connections, recipients and channel billing conditions.
Does sending an alert mean the issue is resolved?
No. A notification conveys information, an action performs a defined step, and resolution needs a check of the situation. For example, pausing ads does not repair the page they were pointing to.