Choose what starts the work
| Trigger | Example | What to specify |
|---|---|---|
| Schedule | Review upcoming appointments each morning. | Time zone, frequency, data source, and output. |
| Supported external event | Continue work when a connected record changes. | Provider, event type, filters, and allowed response. |
| Customer action | Start a follow-up after a customer submits a request. | The action that qualifies and the information to pass along. |
Define the action and stop conditions
Tell the Builder what the agent should do when triggered and when it should do nothing. For a reminder, specify who should receive it, through which connected channel, and how canceled or completed work should be excluded.
The relevant connections and permissions must be available when the automation runs. A scheduled action does not automatically bypass an approval requirement or grant additional account access.
A follow-up rule
Each weekday morning, check tomorrow’s confirmed consultations. Use the connected calendar and email account to send a reminder only where the customer has agreed to receive it. Skip canceled meetings and report any delivery failure to the team.
Verify the running workflow
Test a qualifying event and a case that should be ignored. Confirm the actual outcome in the destination, including time zone behavior and any human handoff.
Recheck the workflow when account permissions, business rules, or destinations change. Define a way to pause the automation and handle incomplete runs before relying on it.
What does scheduled work cost?
Cost depends on the selected model, how often the task runs, and the tools it uses. GPT-6 Luna model usage is free. Schedule triggers and connected services can have separate charges, so a free model does not make every automated workflow free.
Test a representative run and check your account’s usage before choosing a schedule frequency or estimating a monthly budget.