Skip to main content
Choose your client to try Plainrouter’s account-free sandbox, then connect your workspace. Chat clients, terminal agents and workflow platforms use different configuration screens; the server and workspace boundaries stay the same.

​
Choose your setup guide

​
Endpoints and access

Create a Workspace key for one workspace. Read covers analysis; Actions require Write, including their record-read tools. Keep credentials in protected client settings, never prompts or source control. OAuth clients obtain workspace-scoped execution credentials through sign-in instead of requiring a pasted key. Ask waits for approval; Full runs policy-allowed changes automatically. Rule violations are blocked either way. Client permission prompts do not override Plainrouter policy.

​
What proves the connection worked?

Inspect a real tool result. In the sandbox, a successful read contains sandbox: true. In production, a read must return the intended workspace. A discovered tool list or an assistant saying “connected” does not prove authenticated access. Agent wording can vary, and connecting a client does not verify conversion delivery or ad execution. For another client, use the transport and authentication reference. For conversion sending without an agent, start with n8n and Make automation.