Skip to main content

Scheduled actions

Scheduled actions are DELAYED_JOB jobs that run after a delay from the contact’s last incoming message. Execution depends on the current stage, active rules, and configured delay—not on an AI decision.
Scheduled actions do not inherit rules from the main set. Each stage must have its own rules or share a rule associated with multiple stages.
A rule can use execute_once to run only once per contact.

Scheduled HTTP Call

type, delay_in_seconds, url, and method are required. auth, timeout, run_ai_after, error_message, and execute_once are optional.

Outgoing request

The endpoint receives an envelope containing the function arguments, project, and contact:

Response

The minimum response is:
output is required and must be a string. An empty response is treated as an error. The endpoint may also return continue_conversation, message_to_ai, and direct_messages, as described in HTTP Call. The AI is called again only when both conditions are true:

Force Message

Force Message actions resume a conversation without an HTTP integration.

Message to the AI

FORCE_NEW_MESSAGE_TO_AI delivers the message as an instruction for the AI to write a response using the conversation history.

Direct message to the contact

FORCE_NEW_MESSAGE_TO_USER sends the text directly without AI rewriting.
The rule is scheduled only when it is active and associated with the contact’s current stage.