Skip to content

workflow_wait_resolve

Answer an approval (`decision`) or an input (`payload`, checked against the node’s form) and let the run continue.

Tool

workflow_wait_resolve

Answer an approval (`decision`) or an input (`payload`, checked against the node’s form) and let the run continue.

Answer an approval (`decision`) or an input (`payload`, checked against the node’s form) and let the run continue. Authorised for the assignee, or for the holder of the signed `link_token` the notification carried — not for whoever merely holds write. A wait that was already answered or has expired is refused.

Behavior

HTTP
POST /workflow/waits/resolve

Arguments

Name
Type
Required
Description
comment
string
—
No description in the catalog.
payload
object
—
Required for an `input`: the answer, checked against the node's form.
wait_id
string
•
No description in the catalog.
decision
string
—
Required for an `approval`.
link_token
string
—
The signed token from the notification link. Resolves on behalf of the addressee.

Response

Field
Type
Always
Description
wait
object
•
channel
string
•
How the resolution arrived; recorded on the run.
resolved_by
string
•
Who the run’s trace records as having answered.

Try it

Answer an approval (`decision`) or an input (`payload`, checked against the node’s form) and let the run continue.

When to use

Answer an approval (`decision`) or an input (`payload`, checked against the node’s form) and let the run continue. Authorised for the assignee, or for the holder of the signed `link_token` the notification carried — not for whoever merely holds write. A wait that was already answered or has expired is refused.

Example

Ask your agent something like this:

Answer an approval (`decision`) or an input (`payload`, checked against the node’s form) and let the run continue.

The agent will invoke workflow_wait_resolve with these arguments:

{
  "wait_id": "<wait_id>"
}

Esc

Start typing to search the docs.

↑↓navigate↵select