Test custom integration
Fire a test GET request through a workspace custom HTTP integration's STORED credentials and report the outcome: { success, status, statusText, durationMs }. Pass the integration id (from list_workspace_integrations) and an optional path appended to its base URL (default '/'). The stored API key / OAuth token is used server-side and never returned. Requires workspace-admin.
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/test_workspace_integration" \ -H "Content-Type: application/json" \ -d '{ "workspace": "string", "integrationId": "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
}Test workflow function POST
Run one workflow function now and return what it did, with secrets masked. Pass `name` for a saved function, or `function` to run a new or edited one before it is saved; either way it uses this version's variables and secrets. This sends a real request: an http function calls its endpoint and retries as its maxRetries says, so a POST that fails with a 5xx or times out can reach the receiving system more than once; an sms function sends a real text (to smsTo when given), email and slack functions deliver for real, and an app function runs its action on the connected account. Pass `preview: true` to render an http, sms, email or slack function without sending anything; tool and app functions cannot be previewed. Testing an app function for real needs workspace-admin access, and connects the app to the agent for the workflow only, as saving it does. Pass sample values for its placeholders in `variables`, at most 64 of 2000 characters each. The run stops at its slot's limit (10 s for callEnded, 90 s otherwise). The reply has status and reason (empty:<token> means that placeholder rendered empty), arguments (the request or message), response, statusCode, elapsedMs, attempts (one entry per try with its status code, reason and ms), conditions (whether the function's `when` would let it run with these values, rule by rule; null when it has none; the test runs either way), outputs (the variables it maps from the response, which later functions read), empty (each field a placeholder left empty, such as query.phone; an empty query or header value is left out of the request) and preview. Nothing is recorded against a call. Use when the operator asks to test, try or preview a pre-call, hang-up or post-call function.
Undo the last change POST
Put the draft back the way it was before your last change to it, or before your last `steps` changes. Before each change you make to the draft, in the in-app Builder or assistant, over the MCP, through /v1 or with `vai push`, the server saves a checkpoint of the draft for you on this agent; it keeps your newest ten, and a Builder message counts as one change however many edits it made. This applies a checkpoint with apply_agent_spec replace: true, so it covers every field the spec covers, and returns `changedBack`, the steps it reversed in plain words, and `remaining`, how many more changes you can undo. Tell the user the changedBack list as it is. The checkpoints it went back past are used up, so calling it again goes back one change further. It refuses, changing nothing, when there is no checkpoint, when the checkpoints were saved on a version that is no longer this agent's draft (it was published or replaced since), or when the version is published. Changes made on the editor's own pages are not recorded, but an undo puts them back too when they came after the checkpoint.