Set tool follow-up
Decide what happens when a call ends before this tool fires, the caller hangs up mid-enquiry and the action the agent was working toward is lost. `off` (default) loses it, as today. `notify` has a post-call judge read the call and alert someone with what the agent was about to do. `complete` runs the tool after the call through a headless agent-run, using only what the caller actually said, then reports that it ran. `complete` is refused on tools that need the live call (transfer_to_human, end_call, the live-screen set) or that message the CALLER rather than the business (send_text_message), use `notify` for those. Set `requiredArgs` so a half-finished call downgrades to notify instead of guessing a phone number, and `note` to tell the judge when NOT to act (cold callers, robocalls). Identify the tool by toolName or toolId.
Authorization
bearerAuth A personal access token from Settings > API tokens.
In: header
Header Parameters
A key you choose, such as a UUID, that makes this POST safe to retry. Within 24 hours the same key and request answers with the first successful answer and runs nothing, the same key with a different request answers 422 idempotency_key_reused, and a key whose request is still running answers 409 idempotency_key_in_use. A failed request keeps nothing, so the same key runs it again.
1 <= length <= 255Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
curl -X POST "https://example.com/operations/set_tool_follow_up" \ -H "Content-Type: application/json" \ -d '{ "mode": "off", "agent": "string" }'{}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}{
"type": "http://example.com",
"title": "string",
"status": 0,
"detail": "string",
"code": "string",
"errors": [
{
"path": "string",
"message": "string"
}
],
"estimate": {},
"retryAfterSeconds": 0
}Set tool endpoint POST
Update an HTTP tool's method + URL (always together, they're coupled). Identify the tool by toolName (its snake_case name) or toolId. URL may contain `{{variable_name}}` placeholders.
Set tool headers POST
FULL-REPLACE an HTTP tool's headers map (this is NOT a merge: the new map overwrites the existing one entirely, so always send the COMPLETE set of headers you want, not just the ones that changed). Identify the tool by toolName (its snake_case name) or toolId. Pass an object of `{ headerName: value }` (NOT array-of-{key,value}). Empty object clears all headers. Values may contain `{{variable_name}}` placeholders, commonly `Authorization: Bearer {{api_key}}`. **Never send a real credential as a header value**: headers are stored on the tool row in the clear, and a literal credential is refused wherever it is recognisable. Send the placeholder, then put the value in the Vault with `request_secret_variable` in the app (the operator types it into a dialog you never see) or, over the MCP, `set_secret_variable`.