Skip to main content

The invoke request

Atlas calls one action per invoke request. Example:

Design rules

  • Keep action input inside action.input
  • Keep room and session context outside action.input
  • Do not depend on hidden routing state
  • Treat invocationId as the stable correlation id
  • Return useful outputText and machineSummary values whenever you can

Valid response states

completed

The action finished immediately.

accepted

The gateway started async work and returned a durable job id.

approval_required

The action should pause for human approval instead of running immediately.

rejected

The action cannot run.
Start simple:
  • use completed for read-only actions that can finish quickly
  • use accepted for long-running work
  • use approval_required for sensitive actions
  • use rejected for invalid or impossible requests
Do not overload one state to mimic another. Atlas tracks these flows differently.