Test Workflow Tool
Run a custom tool once, exactly as the agent calls it, and see the request, the response, and what the agent reads.
What the test does
- It builds the request exactly like the agent:
{{env.KEY}}secrets, context placeholders,{argument}path parameters, the remaining arguments as query parameters (GET) or as the body (other methods), and the tool’s saved headers. - It works on inactive tools, so you can test a tool before you turn it on.
- It calls your external system for real.
- Unlike a conversation, it only reaches public hosts, does not follow redirects, and runs at most once. A URL that points to a loopback, private, link-local, or cloud metadata address is refused before anything is sent.
- Nothing changes in Nexor: no lead, stage, field, or conversation is touched, and the run does not appear in Tool health.
Before you start
- MCP keys need
workflows:write, because the test reaches your system for real. Full-access REST keys need nothing else. - Get
toolIdfrom List workflow tools. Only the task’s custom tools can be tested. - Nexor platform tools return 400
internal_tool_not_testable. Test those in Playground.
Tools that change data
GET tools run directly. A tool whose method is POST, PUT, PATCH, or DELETE changes data in your system, so the test only runs withconfirm_write: true. Without it the answer is 409 write_requires_confirmation and nothing is sent.
What to send
{{lead.phone}}, stay unresolved and appear in checks.unresolved_placeholders. {{lead_id}} is sent empty.
Placeholders in the tool URL
/appointments/{{appointment_id}}, never gets a value: the literal text reaches your system. Saving a tool like that is rejected with 400 invalid_url_placeholder, which names the arguments in fields and proposes the corrected URL in suggested_url:
checks.unresolved_placeholders.
How to read the result
success only says the test could run. The verdict is passed, which is true when the request was sent, your system answered with a 2xx and a usable body, and the final URL has no unresolved placeholder.
Limits
- One attempt per request, up to the tool’s timeout. A test that times out is not retried, so a tool that changes data runs at most once.
body_excerptandagent_seesare cut at 2,000 characters.- Values that come from
{{env.KEY}}appear inrequest.urlas[Redacted]. Headers are not returned. Values you send inargsorlead_metadataare returned as sent.
Authorizations
Path Parameters
Body
Required as true for tools whose method is POST, PUT, PATCH, or DELETE, because the test really changes data in the external system. Send it only after the operator agreed, with test data, and undo the effect afterwards. The test runs at most once: a timeout is not retried. Ignored for GET tools.
Response
The test ran. success only means the test could run; read passed for the verdict. passed is true when the request was sent, the external system answered with a 2xx and a usable body, and the final URL has no unresolved {{...}} placeholder.
false when no answer came back. Usually the request never left Nexor, for example because args do not match the tool's parameters, a {{env.KEY}} secret is missing, or the final URL points to a host that is not public; it is also false when the single attempt timed out. agent_sees then explains why.