One Meta callback.
Every tool that needs it.
Meta sends Lead Ads and WhatsApp events to one URL per app. Relayo takes that one URL, verifies every event, and delivers it to your CRM, confirmation tool, n8n and order system — with retries, logs and one-click replay.
Meta gives you one webhook. Your business runs on five tools.
Every COD store and agency hits the same wall once a second tool needs the same events.
One callback per app
Lead Ads sends every lead to one URL. Point it at n8n and your CRM stops getting leads. Switch n8n from test to production and the old URL is silently replaced.
One URL per WhatsApp number
Your confirmation tool and your CRM both need incoming messages. Meta’s answer is “create another app” — and every app sees every number on the WABA.
No retries you can see
When a tool is down, events are lost or arrive days later. Nobody knows which order was never confirmed until the customer calls.
Set up once, in about ten minutes
No code in your tools. They receive the same Meta payloads they already understand.
-
Connect your Meta app
Paste Relayo’s callback URL and verify token into your Meta app. Relayo answers the verification and checks every signature from then on.
https://in.relayo.app/in/k3x7q… -
Add your tools
Each tool is a receiver: its webhook URL, plus optional headers. Tools that expect Meta’s signature get one signed with their own secret.
POST https://confirm.example/webhook -
Route by Page, WABA or number
Send leads from one Page to the CRM, messages from one number to the confirmation tool, delivery statuses to the order system.
messages → ConfirmX · statuses → OMS
Built for Meta’s webhooks, not generic ones
Generic relays forward bytes. Relayo understands what Meta sends.
Verified on arrival
Checks X-Hub-Signature-256 on the exact bytes Meta sent and answers hub.challenge for you. Forged requests never reach your tools.
Batches split, routed by ID
WhatsApp batches up to 100 changes per request. Each becomes its own event, routed by Page, WABA or phone number — the most specific match wins.
Retries and dead letters
Failed deliveries retry after 30 s, 2 min, 10 min, 1 h, 6 h and 24 h. A tool that keeps failing is paused, not hammered. Replay any event with one click.
Signed for each tool
Every copy carries a fresh Relayo signature and an event ID to dedupe on. Meta-compatible mode signs like Meta, so ConfirmX-style tools accept it unchanged.
Answers Meta fast
Relayo stores and acknowledges in milliseconds, then delivers in the background. Meta never sees a slow tool and never disables your webhook.
Every event logged
Search by Page, number, field or status. See exactly what each tool answered, when, and how many tries it took.
Full lead details Soon
Lead Ads only send a lead ID. Relayo will fetch the full lead (name, phone, answers) before delivery.
Your whole marketing stack, in any AI
Your WhatsApp confirmation tool, your store, n8n and every brand’s Meta ad account each have their own MCP server — and most AI apps only take one URL per connector. Relayo puts all of them behind one hub URL that works in Claude, ChatGPT, Cursor or any MCP client.
Works with ClaudeClaude CodeChatGPTCursorVS CodeGemini CLIany MCP client
One URL, every tool
Add your MCP servers once — ConfirmX-style WhatsApp tools, your store or OMS, n8n — and their tools appear side by side, each prefixed by where it comes from.
Every brand’s ads, built in
Relayo’s own Meta tools read spend, results and campaigns for every ad account you allow, each with that brand’s token. No Meta MCP proxying.
You stay in control
Pick which servers and tools each hub URL exposes, keep ads read-only, and replace a URL in one click. Keys and tokens are stored encrypted.
Knows what reached your tools
“Did today’s leads reach the confirmation team?” — your AI reads Relayo’s event log and delivery health, phone numbers masked.
Which brand had the cheapest lead yesterday, and are any orders still unconfirmed?
Meta: wesell 41 EGP per lead (26), Alhafez 58 EGP (31). WhatsApp tool: 4 Alhafez orders are still waiting for confirmation — want me to send the reminder template?
Made for cash-on-delivery stores and agencies in MENA
صُمّم لمتاجر الدفع عند الاستلام والوكالات في الشرق الأوسط وشمال أفريقيا
- A lead or message that reaches your confirmation team late is an order that ships late — or never.
- Works with the tools you already use: ConfirmX-style WhatsApp confirmation, EasyOrders, Shopify flows, Google Sheets via n8n, your own order system.
- Agencies: one workspace per client brand, one place to see what reached each tool.
- Arabic interface coming next.
Simple pricing
One plan, everything included. 7-day free trial when we launch — card required, nothing charged until the trial ends, cancel anytime.
Relayo
- 1 Meta app
- 5 receivers
- 50,000 events / month
- 14-day event log
- Retries, replay, dead letters
- Meta-compatible signing
- AI hub: 2 MCP servers + 2 ad accounts
Running multiple brands or agency clients? We price that with you — talk to us
Get early access
We are onboarding a small group of COD stores, agencies and tool makers. Tell us what you run and we will reach out within two working days.
Questions
Is Relayo made by Meta?
No. Relayo is an independent service that receives webhooks from your own Meta app. It is not affiliated with or endorsed by Meta Platforms.
Do my tools need to change?
No. Each tool receives the standard Meta webhook body for one change. Tools that verify Meta’s signature can get one signed with their own app secret.
What happens when a tool is down?
Relayo keeps retrying for about 31 hours, then marks the delivery dead. You can replay it at any time from the dashboard or the API.
What do you store, and for how long?
The event payloads, for 14 days, so you can search and replay them. App secrets and signing secrets are encrypted at rest.
Does it work with my WhatsApp provider?
If your number uses the WhatsApp Cloud API through your own Meta app, yes. Numbers managed fully inside a BSP’s own app need that provider’s webhook settings instead.