Works today on WordPress, WooCommerce & any website · Shopify coming soon
All integrations · Webhooks · Recipes · JSON fields · Signing · Telegram · WooCommerce · Email and CSV
Pick an event
See exactly what your tools receive.
Each enquiry is posted to your webhook, which Zapier, Make and n8n all accept, and can also reach Telegram. This is the real shape of the post, with example values.
New enquiry
WebhookZapierMaken8nTelegramCSV
{
"event": "lead.created",
"site": { "name": "Example Shop", "url": "https://shop.example/" },
"lead": {
"id": 481,
"name": "Sarah Klein",
"email": "sarah@bistronord.example",
"company": "Bistro Nord",
"question": "Trade prices for 50 trays a week?",
"link": "https://shop.example/desk/#ticket-481"
}
}Details added later
WebhookZapierMaken8nTelegramCSV
{
"event": "lead.updated",
"lead": {
"id": 482,
"email": "chef@hotel-alma.example",
"question": "Weekly order with Friday delivery?"
}
}CSV export
WebhookZapierMaken8nTelegramCSV
name,email,phone,company,question,created Sarah Klein,sarah@bistronord.example,,Bistro Nord,Trade prices for 50 trays a week?,2026-09-28
Every integration
What connects to HolaReply, and on which plan.
Available works on every plan, Free included. Pro means Pro and Business. Coming soon is not in the plugin yet.
Where it runs
WordPress
A plugin that reads your published pages, posts and the custom post types you choose.
WooCommerce
Products, prices as a guest sees them, stock and store pages. Product cards on every plan.
Shopify
An app for Shopify stores, coming soon to the Shopify App Store.
Any website
Wix, Squarespace, Webflow or a custom site, with one line of code.
The AI that writes the answers
Google Gemini
Your own key. Google bills you, about $1.70 per 1,000 answers with Gemini Flash.
OpenAI
Your own key for the models behind ChatGPT. OpenAI bills you.
Anthropic Claude
Your own key for the answers; Gemini or OpenAI builds the index.
HolaReply AI
No key: $12 per 1,000 answers in credits, less in larger packs.
DeepSeek
Being built and tested. Billed by the provider.
xAI Grok
Being built and tested. Billed by the provider.
Meta Llama
Being built and tested. Billed by the provider.
Where your leads go
Every enquiry emailed to your sales inbox with the whole conversation.
Telegram
New enquiries in Telegram. Reply there and the visitor gets it in the chat.
Webhooks
Signed JSON to any https address, the moment a lead arrives.
Zapier
Webhooks by Zapier, Catch Hook; then any app Zapier connects.
Make
A Custom webhook module; then any app Make connects.
n8n
A Webhook node, on n8n cloud or your own server.
CSV export
Every enquiry as a spreadsheet, from the Sales Desk inbox.
Weekly summary email
Enquiries, after-hours answers and unanswered questions, once a week.
Webhooks · Business
Every new lead, posted as signed JSON.
Your sales process lives in a CRM, a spreadsheet or a Slack channel. Enquiries that stay in one more inbox are enquiries somebody has to copy by hand. HolaReply sends each enquiry where your team already works: your sales inbox on every plan, and with Pro, Telegram and a signed webhook for Zapier, Make, n8n or your own server, the moment the lead arrives.
Copy an address
In Zapier choose “Webhooks by Zapier”, Catch Hook; in Make, “Custom webhook”; in n8n, a Webhook node. Each gives you an https address.
Paste it and send a test
In HolaReply, Settings → Lead capture → Webhook address. Send a test posts a made-up lead, so your tool can learn the fields.
Every lead follows
Each new enquiry is posted as it arrives, without making the visitor wait, and again if it gains contact details later.
| Event | Sent when |
|---|---|
lead.created | A new enquiry was saved. |
lead.updated | An enquiry that arrived without contact details gained them. Same id. |
lead.test | You clicked Send a test. Made-up details, id 0. |
| Header | Value |
|---|---|
Content-Type | application/json |
X-HolaReply-Event | lead.created, lead.updated or lead.test |
X-HolaReply-Signature | sha256= and the HMAC-SHA256 of the body, in hex |
Recipes
Four ready recipes, three steps each.
The first three start from the webhook. HolaReply posts to one address, so one Zapier, Make or n8n workflow can run several of them at once.
Zapier
New lead → Google Sheets
- In Zapier, create a Zap with the trigger “Webhooks by Zapier”, event Catch Hook, and copy its address.
- Paste it into Settings → Lead capture → Webhook address in HolaReply and click Send a test.
- Add the action Google Sheets, Create Spreadsheet Row, and map lead name, email, phone, company, question and link to your columns.
Make
New lead → HubSpot or your CRM
- In Make, start a scenario with Webhooks, Custom webhook, add a hook and copy its address.
- Paste it into HolaReply and click Send a test while Make is listening, so it learns the fields.
- Add your CRM’s module that creates or updates a contact, such as HubSpot CRM, map email, name, phone and company, and put the question and link in a note.
n8n
New lead → Slack
- In n8n, add a Webhook node with the method POST and copy its production address; activate the workflow.
- Paste it into HolaReply and click Send a test.
- Add a Slack node that sends a message to your sales channel, for example: New lead {{ $json.body.lead.name }}: {{ $json.body.lead.question }} {{ $json.body.lead.link }}
No automation needed
New lead → a shared inbox
- In Settings → General → Send enquiries to, enter your team’s shared address, such as sales@yourcompany.com.
- Every enquiry arrives there with the whole conversation, on every plan, even when the AI is down.
- Need several addresses or your own subject line? Send the webhook to Zapier and use Email by Zapier, Send Outbound Email.
What a webhook sends
The JSON, field by field.
Fields the visitor didn’t fill in are empty strings, never missing. In the test post, lead.id is 0 and lead.link is empty.
Example: lead.created
{
"event": "lead.created",
"site": {
"name": "Your Shop",
"url": "https://example.com/"
},
"lead": {
"id": 128,
"created": "2026-09-27T10:42:05+01:00",
"name": "Olivia Moreau",
"email": "olivia@example.com",
"phone": "+44 20 7123 4567",
"company": "Moreau Bakery",
"question": "Can you do 50 kg of dried apricots a month?",
"link": "https://example.com/desk/#ticket-128"
}
}| Field | What it holds |
|---|---|
event | lead.created, lead.updated or lead.test, as in the X-HolaReply-Event header. |
site.name | Your site’s name. |
site.url | Your site’s address. |
lead.id | The enquiry’s number: the same in the Sales Desk and in both posts about it. |
lead.created | The time of this post, in ISO 8601 with your site’s time zone. |
lead.name | The visitor’s name. |
lead.email | Their email address. |
lead.phone | Their phone number. |
lead.company | Their company. |
lead.question | The question or message they left for your team. |
lead.link | A link to the ticket in your Sales Desk, with the whole conversation. |
Signing
Check that a post really came from your site.
Every post carries an X-HolaReply-Signature header: sha256= followed by the HMAC-SHA256 of the request body, in hex, made with your site’s signing secret. Find the secret in Settings → Lead capture → Signing secret once Pro is active. Compute the same HMAC over the raw body, exactly as received and before parsing the JSON, and compare the two in constant time.
Zapier and Make don’t need it. It is for your own server, or an n8n workflow, that wants to be sure a lead really came from your site.
PHP
$body = file_get_contents( 'php://input' );
$expected = 'sha256=' . hash_hmac( 'sha256', $body, $secret );
$received = $_SERVER['HTTP_X_HOLAREPLY_SIGNATURE'] ?? '';
if ( ! hash_equals( $expected, $received ) ) {
http_response_code( 401 );
exit;
}Node.js
const crypto = require('crypto');
// rawBody: the request body exactly as received, before JSON parsing.
const expected = Buffer.from('sha256=' + crypto.createHmac('sha256', secret).update(rawBody).digest('hex'));
const received = Buffer.from(req.get('X-HolaReply-Signature') || '');
const valid = expected.length === received.length && crypto.timingSafeEqual(expected, received);Telegram · Pro
Leads on your phone, replies back to the chat.
Each new enquiry arrives in Telegram with the visitor’s details and question. Reply to it there and the visitor gets your answer in the chat on your website.
Make a bot
In Telegram, open @BotFather and send /newbot. It takes a minute and gives you a token.
Connect it
Paste the token in Settings, Lead capture, then press Start in your chat with the bot, or add it to your team’s group.
Reply from Telegram
Each enquiry arrives with the visitor’s details and question. Reply to that message and it goes to the visitor.
Your own bot
The bot and the chat are yours. Nothing passes through our servers.
For a team
Add the bot to a group, and everybody in it sees new enquiries.
Their next message too
When the visitor writes again in the chat, it is forwarded to Telegram the same way.
Safe
The token is encrypted on your site and never shown again. Telegram signs every call, and only your connected chat is listened to.
WooCommerce
Your catalogue, read the way a shopper sees it.
What it reads
Each product as a signed-out shopper sees it: the price your shop displays, SKU, category, visible attributes, weight, stock or back-order status and the short description.
Always current
A product is re-indexed when you edit it.
Trade prices stay private
Prices shown only to logged-in customers are never quoted.
Store pages too
Delivery, returns, payment and FAQ pages, which answer many of the questions shoppers ask.
Product cards
Up to three products under an answer, with picture, name, price and a link; Pro adds stock and sale prices. If prices are a locked topic, the cards leave the price off.
Not yet
Add to cart from the chat, and order look-ups. Order problems go to your team.
Email and exports
Your inbox, a weekly summary and a spreadsheet.
Enquiry emails
Every enquiry goes to the address in Settings → General → Send enquiries to, with the whole conversation, even when the AI is down.
Weekly summary
Once a week, on the day and at the time you choose: enquiries, what the assistant did while you were closed, and the questions nobody could answer.
CSV export
An Export CSV button in the Sales Desk Inbox: every enquiry, ready for Excel, Google Sheets or a CRM import. Formulas typed by visitors are defused.
Honest limits
What it doesn’t connect to yet.
- WhatsApp alerts are planned. Telegram alerts work today.
- Ticket events, such as assigned or won, are planned. Today the webhook sends new leads and leads that gain contact details.
- Automatic retries are planned. Today each lead is posted once; it is still saved on your site, emailed to your sales inbox and in the CSV export.
- Direct apps for HubSpot, Slack or Google Sheets: not built. Zapier, Make and n8n connect to all three, as in the recipes above.
- The page the visitor was on and the conversation text are not in the webhook. The link opens the ticket, with the whole conversation, in your Sales Desk.
Questions
Asked about integrations.
Which plan has webhooks, Zapier, Make, n8n and Telegram?
Pro and Business. WordPress, WooCommerce, every AI option and enquiry emails work in the free version too.
Do I need Zapier?
No. Any tool or server that accepts a JSON post over https works: Make, n8n or your own CRM.
Does HolaReply connect to HubSpot, Slack or Google Sheets directly?
Not with its own app. Send the webhook to Zapier, Make or n8n, which connect to all three; the recipes on this page take three steps each.
What happens if my endpoint is down when a lead arrives?
The post is sent once and is not retried yet. The lead is still saved on your site, emailed to your sales inbox and included in the CSV export.
Is WhatsApp available?
Not yet. WhatsApp alerts are planned; Telegram alerts work today in Pro.