Connect Instagram and WhatsApp automations to n8n, Make, Zapier or your own code with the Repli REST API and signed webhooks. API keys, no OAuth setup, unlimited workflows.
Create, edit, pause and delete comment-to-DM rules, AI reply prompts, follow-gates, lead forms and follow-up sequences programmatically.
Manage WhatsApp Business keyword rules, AI agents, buttons, appointment triggers and follow-ups — and send session messages from any workflow.
Repli pushes lead.created, lead.completed, appointment.created and message.sent to your n8n webhook node with an HMAC-SHA256 signature.
Pull collected leads, booked appointments, lead form definitions and full message logs into your CRM, Google Sheet or data warehouse.
Agencies running 200–300 client accounts can provision automations for every workspace from one n8n workflow — each account keeps its own key.
Open the Developers page in your Repli dashboard and create a key. You get an rpk_live_ token shown once, with read-only or read-write scopes.
Use an HTTP Request node (n8n), an HTTP module (Make) or plain curl with an Authorization: Bearer header. JSON in, JSON out — no SDK required.
Register your n8n webhook URL, pick the events you care about, and Repli delivers signed payloads within about 60 seconds of each event.
Yes. Use the HTTP Request node with a Header Auth credential set to Authorization: Bearer rpk_live_your_key, and the Webhook node to receive Repli events. No OAuth app, no self-hosted callback allowlisting and no browser step is required.
Repli's managed authorization server only accepts redirect URIs on Repli-owned domains, so a self-hosted n8n callback URL cannot be allowlisted. API keys are the supported path and are simpler: one header, no token refresh, revocable at any time.
Yes. Each client account generates its own API key inside their own Repli workspace, so data stays isolated per tenant. Store the keys in your n8n credential vault and loop over them to create automations, pull leads or send messages in bulk.
Every delivery includes an X-Repli-Signature header containing an HMAC-SHA256 hash of the raw request body, computed with the secret shown when you register the endpoint. Verify it before trusting the payload.
API keys and webhooks are available on paid Repli plans starting at ₹499/month, with no per-call or per-contact fees. Message sending still respects your plan's daily limits and the platform rules of Meta.
It is a JSON REST API over HTTPS. Read endpoints use GET with limit and filter query parameters; writes use POST, PATCH and DELETE. Errors return a JSON body with the upstream status and provider details so failures are easy to debug in n8n.
Create a Repli API key, call the REST API from n8n, and subscribe to signed webhooks.
Drive every Repli automation from n8n, Make, Zapier or your own backend. One API key, a clean JSON REST API, and signed webhooks that push leads, bookings and message events into your workflow in real time.
Anything you can build in the Repli dashboard can be created, updated and monitored through the API — across all two channels.
No OAuth app, no callback allowlisting, no token refresh logic. Just a header.
Register any HTTPS endpoint — an n8n Webhook node, a Make scenario, a Slack relay or your own server — and Repli delivers a JSON payload as events happen. Each request carries an
header with an HMAC-SHA256 hash of the body so you can verify authenticity before acting on it.