curl --request POST \
--url https://app.trelica.com/api/workflows/v1/{workflowId}/runs/{runId}/firedSignals/{activityId}/{signalName} \
--header 'Authorization: Bearer <token>'{
"type": "about:blank",
"title": "One or more validation errors occurred.",
"status": 400,
"detail": "The request body failed validation. See errors for the offending fields.",
"errors": {
"email": [
"The email field is required."
]
},
"traceId": "00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01"
}Fire a signal
Fires a named signal (for example an approval or rejection) on a workflow step that is
currently waiting for input, allowing the run to continue. The valid signals for a waiting
step — and the URL to call to fire each one — are listed under the step’s waiting.actions
in the run’s response, so a client can simply POST to the supplied href.
Returns 200 when the signal was fired and the run advanced. Returns 409 if the
step is no longer waiting (for example it has already been signalled or has timed out), and
404 if the run or workflow cannot be found.
Required scope: Workflows.Runs.Execute (Execute workflow run actions)
curl --request POST \
--url https://app.trelica.com/api/workflows/v1/{workflowId}/runs/{runId}/firedSignals/{activityId}/{signalName} \
--header 'Authorization: Bearer <token>'{
"type": "about:blank",
"title": "One or more validation errors occurred.",
"status": 400,
"detail": "The request body failed validation. See errors for the offending fields.",
"errors": {
"email": [
"The email field is required."
]
},
"traceId": "00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-01"
}Authorizations
OAuth 2.0. Obtain an access token via the Client Credentials or Authorization Code flow, then send it as Authorization: Bearer <token>.
Path Parameters
The workflow's ID.
The run's ID.
The ID of the waiting step the signal is fired on.
The name of the signal to fire (one of the step's waiting actions).
Query Parameters
Optional iteration ID, for a step inside a loop.
Response
OK
Was this page helpful?