For the complete documentation index, see llms.txt. This page is also available as Markdown.

Scheduled Execution Tool

The Scheduled Execution Tool lets an Agent schedule a Workflow execution for a future time during a conversation.

Use it when the future action should be decided by a Workflow instead of being limited to sending a follow-up message.

Scheduling rules

  • The Agent can schedule a single future execution using an absolute date and time or a relative delay, such as “in one hour.”

  • Each schedule points to one existing Workflow trigger.

  • When the scheduled time arrives, Zaia runs that trigger automatically.

  • No separate CRM rule is required to create a one-time schedule.

  • Scheduled executions are separate from the legacy Follow Up Tool. Existing follow-up messages continue to work independently.

Context sent to the Workflow

The scheduled Workflow receives the conversation context needed to choose the next action, including the chat, channel, recent messages, current tags, and the active ticket when one exists.

The Workflow can then send a reminder, update an external system, start another automation, or perform any action supported by its configured nodes.

Status and management

A scheduled execution has a visible status:

  • Pending — waiting for its scheduled time.

  • Executed — the Workflow trigger completed.

  • Canceled — the execution will no longer run.

  • Failed — the trigger could not complete.

Failed executions keep a consultable reason. Existing schedules can be reviewed and updated through scheduled-execution management.

Validation and restrictions

  • The Workflow trigger must exist when the schedule is created.

  • The schedule must include the minimum conversation context required by the execution.

  • Invalid schedules are rejected instead of being saved partially.

  • Recurring schedules and automatic schedules created from workspace events are not part of the initial release.