Resolve interrupt

Submit user response to resolve a pending interrupt. The value type depends on the interrupt type:

• confirmation: boolean (true = confirmed)
• choice: string or string[] (selected values)
• text: string (user input)
• form: object (form data matching schema)

POST /interrupts/{interruptId}

cURL

confirmation

curl --request POST \ --url http://localhost:5173/api/flowdrop/interrupts/{interruptId} \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "value": true }'

200

{
  "success": true,
  "data": {
    "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "nodeId": "<string>",
    "executionId": "<string>",
    "config": {
      "message": "Do you approve this action?",
      "confirm_label": "Approve",
      "cancel_label": "Reject"
    },
    "allowCancel": true,
    "messageId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
    "response": "<unknown>",
    "response_time": "2023-11-07T05:31:56Z",
    "user_id": "<string>",
    "createdAt": "2023-11-07T05:31:56Z"
  },
  "message": "<string>",
  "error": "<string>"
}

Authorizations

BearerAuthSessionAuth

Authorization · string · header · required

JWT token for authentication

Path Parameters

interruptId · string<uuid> · required

Interrupt UUID

Body

application/json

Request body for resolving an interrupt

value · any · required

User's response. Type depends on interrupt type:

• confirmation: boolean
• choice: string or string[]
• text: string
• form: object
• review: ReviewResolution (decisions map + summary)

Response

200

application/json

Interrupt resolved successfully

success · boolean

Whether the request was successful

data · object

Represents a Human-in-the-Loop interrupt request. Interrupts are created when workflow execution requires user input.

Show child attributes

message · string

Response message

error · string

Error message (if any)