Queue message
Add a message to a session’s queue instead of interrupting the agent. Queued messages are sent automatically, in order. An eligible idle, completed, or failed session starts a turn immediately; a busy session consumes the message through its existing queue.
POST
cURL
Who runs a queued message?
Who runs a queued message?
If someone else’s message is queued, Gumloop lets the current run finish, then starts a new run in the same session for that person. The new run uses their permissions, connector accounts, and credits. If the agent uses agent-owned accounts, every run still uses those.
What limits apply to the queue?
What limits apply to the queue?
Stops, approvals, and concurrency limits still apply. A session’s queue holds at most 20 messages. The returned queue can already be empty if delivery started.To interrupt the current turn and send a queued message immediately, use Send queued message now.
Authorizations
A personal API key or an OAuth 2.0 access token. Personal API keys also require the x-auth-key header with your user ID.
Body
application/json