Build with the Simplafy Hub.
Four doors to connect the Hub to your system, your AI assistant and your code: talk to agents, send data, run the whole Hub and publish agents as code.
Which door to use
1 · MCP — the whole Hub inside your AI assistant
What it's for.Connect ChatGPT, Claude or any MCP client to the Hub and run everything by chatting: contacts, deals, pipelines, agents, journeys, campaigns, catalog, invoicing, dashboards and more. Everything the screen does, MCP does.
- 1In the Hub, go to Settings › AI assistants and copy the address.
- 2Paste it into your assistant as an MCP server (custom connector).
- 3Sign in with your Hub account and choose the areas it can see and change, read-only or read and write.
Prefer the official app? Look for «Simplafy Hub» in the ChatGPT store or the Claude directory.
https://mcp-hub.simplafy.com.br/completo
Settings › Connectors › Add custom connector, and paste the address.
https://mcp-hub.simplafy.com.br/completo
Use the official «Simplafy Hub» app in the ChatGPT store or, under custom connectors, paste the address.
https://mcp-hub.simplafy.com.br/completo
In the terminal:
claude mcp add --transport http simplafy-hub https://mcp-hub.simplafy.com.br/completo
In ~/.cursor/mcp.json:
{
"mcpServers": {
"simplafy-hub": {
"url": "https://mcp-hub.simplafy.com.br/completo"
}
}
}In .vscode/mcp.json:
{
"servers": {
"simplafy-hub": {
"type": "http",
"url": "https://mcp-hub.simplafy.com.br/completo"
}
}
}- Transport: MCP Streamable HTTP (JSON-RPC 2.0).
- Authentication: OAuth 2.1 with automatic client registration and PKCE. No key needed.
- The assistant never has more power than the person's role in the organization.
- Over 140 tools with full access.
- Session: access renews on its own for up to 30 days; revoke it anytime in Settings › My assistants.
hub.<área>.read / hub.<área>.write):2 · Agent API — your system talks to an agent
What it's for.Your website, app or system sends a question or a task and the Hub agent answers, with the same tools, knowledge base and rules it uses on WhatsApp. The answer can come as text, in real time, in structured format (JSON) or as a file, like a generated PDF.
- 1In the Hub, under Integrations › Channels, create an Agent API channel and link the agent to it.
- 2Choose the behaviors you want to use: Run, Real time, Structured and File. Each one you turn on gets its own address to copy.
- 3Generate the channel token. It's shown only once; you can rotate and revoke it.
https://api-hub-v2.simplafy.com.br/api/v1/agent-api/{nome-do-canal}- Authentication: Authorization: Bearer <channel token>.
- Required header: Idempotency-Key: <unique request id>. Repeating the same id doesn't run it twice.
- JSON body, up to 256 KiB: { "input": "text for the agent, up to 32,000 characters", "data": { …optional data… } }.
| Route | What it returns |
|---|---|
POST /run | The final response: { "version": "1", "requestId", "status": "completed", "text", "parts" } |
POST /stream | Real-time response (SSE, AG-UI events), with resume via Last-Event-ID |
POST /structured | A validated JSON in the format defined on the channel: { …, "data": {…} } |
POST /file | The files the agent generated: { …, "text", "files": [...] } |
POST /openai/v1/chat/completions | Compatible with the OpenAI API (e.g., to connect ElevenLabs to the agent) |
curl -X POST https://api-hub-v2.simplafy.com.br/api/v1/agent-api/meu-canal/run \
-H "Authorization: Bearer $TOKEN_DO_CANAL" \
-H "Idempotency-Key: pedido-123" \
-H "Content-Type: application/json" \
-d '{"input":"Qual o prazo de entrega para Brasília?","data":{"pedido":"123"}}'Always in the same format:
{ "version": "1", "requestId": "…", "error": { "code": "INVALID_TOKEN", "message": "…", "retryable": false } }| HTTP | code | When |
|---|---|---|
| 400 | INVALID_REQUEST | Invalid body, missing Idempotency-Key, field other than input/data or over 256 KiB |
| 401 | INVALID_TOKEN | Missing or wrong token |
| 403 | BEHAVIOR_DISABLED | This behavior is turned off on the channel |
| 404 | CHANNEL_NOT_FOUND | The channel doesn't exist |
| 409 | AGENT_NOT_LINKED | The channel isn't linked to any agent |
| 422 | NO_FILE_GENERATED | On the /file route, the agent didn't generate a file |
| 503 | AGENT_UNAVAILABLE | The agent is off or unavailable (try again) |
3 · Inbound webhook — send data to the Hub
What it's for.Any system, website form, n8n, Make or Zapier sends data to the Hub, and the Hub uses it in a Journey: create a contact and deal, move stages, write to a Data Table, alert the team or trigger an agent.
- 1In the Hub, under Integrations › Webhook, create the webhook and copy the address and token.
- 2In the Journey, use the «Webhook» trigger and choose what to do with the data.
curl -X POST https://api-hub-v2.simplafy.com.br/api/v1/webhooks/in/{orgId}/{caminho} \
-H "X-Webhook-Token: $TOKEN_DO_WEBHOOK" \
-H "Content-Type: application/json" \
-d '{"nome":"Maria","telefone":"+55 61 90000-0000"}'- Address: https://api-hub-v2.simplafy.com.br/api/v1/webhooks/in/{orgId}/{caminho}. The screen gives it ready to use, with the cURL example.
- POST method. Accepts JSON, form (form-urlencoded) and multipart with a file. Works straight from an HTML form (CORS).
- Authentication: X-Webhook-Token header (or ?token= in the URL). Optional: Bearer or HMAC signature (X-Webhook-Signature).
- You can swap the token and undo the webhook removal.
Not yet available: body format validation, IP allowlist and outbound webhook. For the Hub to call your system, use the Journey's «Call endpoint» step.
4 · ADK — agents, tools and journeys as codeBETA
What it's for.For technical teams and partners: write agents, tools (in Python), tables, journeys and apps as files, keep them in Git, validate on your machine and publish to the Hub with one command. What's already in the Hub can also be exported to files.
npx @simplafy-tec/adk doctor # confere o ambiente npx @simplafy-tec/adk login # entra com a conta do Hub npx @simplafy-tec/adk init tool minha-tool && cd minha-tool npx @simplafy-tec/adk build # valida e procura segredo vazado npx @simplafy-tec/adk deploy --org <orgId>
- The @simplafy-tec/adk package on npm (Node 20 or later). Commands: doctor, login/logout, init tool/mcp/app, build, test, dev, validate, plan, deploy, status, export, mcp-server.
- Login via Hub OAuth (saved on the machine and renews itself). For CI: ADK_TOKEN + --org.
- Publishes in the order tool → agent → journey; whatever fails doesn't take down the rest and shows up in a report.
- plan shows what will change before applying; export pulls what already exists from the Hub; status lists what's pending.
- The build rejects secrets in code: the credential stays in the Hub and is referenced by name.
Version 0.1.0. The full ADK documentation is still being written.