CONNECTION GUIDE

Connect your automation
to a conversation.

Verify the connection with one message,
then receive replies and run approved tasks.

Set up for your tools

01 · PREPARE

Prepare conversations and permissions in the app.

  1. Create an account and a conversation in the internal test app you were invited to.
  2. In the app's connection settings, allow only the conversations and permissions your program needs.
  3. To configure on the web, approve QR sign-in in the app. Keys are shown only once when issued.

Keep keys in your runtime's secret configuration or a private key file, outside source code and conversations. App-approved MCP connections do not require copying a program key.

02 · CONNECT

Choose a connection that fits your setup.

REST API · n8n

Send messages and tasks from an HTTP step in your scripts or automations. Authenticate with a program key and use stable task IDs.

REST API · Developer docs

MCP · Agents

Add Pushyou to an agent that supports MCP. Approve its conversations and permissions in the app, or connect with a program key.

MCP · Developer docs

Responses · Webhooks

The receiver polls response events and runs your handler. Webhooks deliver signed events to your HTTPS endpoint.

See the receiver and examples

03 · CONTINUE THE WORK

Connect approvals to actual execution.

  1. Send a task with its title, form fields and category through the API.
  2. The user reviews and approves in the app or web.
  3. Your connected program receives the task event and claims execution.
  4. Check the actual result, then report success, failure or a need for review.

The original request and its result stay in the same task. If the outcome is uncertain, such as after a timeout, check the external state before deciding to retry. An ACK does not replace task completion.

Deployment, incident and report use cases · Fields, states and API reference

04 · RUN & VERIFY

Keep receiving responses in your program.

The REST receiver runs on Node 22 or later. It saves progress and execution results to resume after delivery failures. For use after closing your terminal, follow the macOS or Linux service setup in the installation guide.

Response receiver installerNode 22+ · Local packageInstall, run continuously and recoverCustom handlers and Codex integrationn8n deployment approval workflowConfigure your URL, conversation and credentials before useREST approval request exampleDeployment, incident and report requestsTask handler exampleLocal reports, diagnostics and deployment input checksSigned webhook receiver exampleVerify signatures and preserve events on disk

The deployment example is a dry run and makes no infrastructure changes. The n8n file is an importable request example; verify execution in your own environment separately. Tasks cannot run while your program is stopped or your computer is asleep.

Developer docs

REST APISend a message, receive a reply, and follow approved work through to its result. Build with the Pushyou REST API.MCPConnect an MCP client to Pushyou. Send requests, read replies, and report results in the same conversation.

Verify your connection with one conversation.

Verify message delivery and a real reply round trip, step by step.

Open connection setup