Make / n8n / Zapier webhook connector
Your Silux Chat bot verifies customers against Make / n8n / Zapier webhook, then answers questions about their orders and order status from your live data.
Good to know: Zapier catch hooks reply with a fixed acknowledgement, not your data — use Make or n8n for lookups.
What your bot can do with Make / n8n / Zapier webhook
Recognise and verify customers
Finds the customer in Make / n8n / Zapier webhook by the email address or mobile number they give, checks their name and one more detail, then sends a one-time code to the contact details Make / n8n / Zapier webhook holds. Nothing personal is shared until the code is entered.
Customers ask: “I want to check my account — it’s Jane Smith, jane@example.com”
Orders and order status
Reads a verified customer’s recent orders from Make / n8n / Zapier webhook — order number, date, status and total, plus tracking where Make / n8n / Zapier webhook records it.
Customers ask: “Where is my order?” · “Has my last order been sent?”
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to Make / n8n / Zapier webhook as an administrator to create the key.
Step 1 — in Make / n8n / Zapier webhook
Create a scenario/workflow that starts with a webhook and ends with a JSON response (Make: Webhook response; n8n: Respond to Webhook). Paste the hook address; the unguessable URL is the credential, so keep it private.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “Make / n8n / Zapier webhook”.
- 2Fill in:
Field Example Stored Catch-hook address (without https://) hook.eu1.make.com/abc123def456 Setting - 3Press Connect & test. The platform makes a real, read-only call to Make / n8n / Zapier webhook with a made-up customer and shows a tick or a cross for each capability, with Make / n8n / Zapier webhook’s exact error if something is refused.
- 4If this is your first way of verifying customers it is switched on automatically; otherwise press Use to verify customers. The platform then runs its chained test (verify → code → account → orders → invoices) with the built-in test customer — no real person is contacted.
The private, unguessable webhook address you paste is the credential, so keep it to yourself. Anyone with the address can call your workflow.
How customer verification works
- STEP 1
Customer asks
They ask about their own account. The bot asks for their full name and their email or mobile, plus one more detail such as their postcode.
- STEP 2
Found in Make / n8n / Zapier webhook
The customer is looked up in Make / n8n / Zapier webhook by email, then mobile. The surname must match exactly and the first name must match or start with the same letter, plus one more detail.
- STEP 3
Code sent
A 6-digit code goes to the mobile Make / n8n / Zapier webhook holds (by text, when your plan has SMS) or otherwise to the email it holds. The chat never chooses where it goes.
- STEP 4
Verified
The customer types the code. It is valid for 10 minutes and five wrong attempts cancel it. The verified session lasts 30 minutes.
If the details don’t match, the customer is told only that they couldn’t be matched — never which detail was wrong. If Make / n8n / Zapier webhook can’t be reached, the bot says it can’t check accounts right now rather than “no account found”. The bot is blocked in code from reading orders, invoices or bookings until verification succeeds. Full details: Customer identity verification & OTP.
What the bot can and cannot see
Can see (after verification)
- Record ID
- Name
- Email address
- Phone / mobile
- Postcode
- Order number
- Order date
- Status
- Total
- Tracking number
- Courier
Only these standard fields are mapped from Make / n8n / Zapier webhook’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in Make / n8n / Zapier webhook.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in Make / n8n / Zapier webhook’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the Make / n8n / Zapier webhook endpoints this connector reads, relative to https://{hook_url}. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Recognise and verify customers | POST/ | id, name, email, phone, postcode |
| Orders and order status | POST/ | order_number, placed, status, total, tracking, courier |
Test level: Documented-API tested. Each capability is run automatically against Make / n8n / Zapier webhook’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in Make / n8n / Zapier webhook and reconnect. |
| “That Catch-hook address (without https://) doesn’t look right” | Enter it in the form shown, e.g. hook.eu1.make.com/abc123def456 — without https:// or a trailing slash. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their Make / n8n / Zapier webhook record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in Make / n8n / Zapier webhook, or your Make / n8n / Zapier webhook plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | Make / n8n / Zapier webhook returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as Make / n8n / Zapier webhook asks); if it persists, ask Make / n8n / Zapier webhook about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in Make / n8n / Zapier webhook, or none are recent. Check the customer’s record in Make / n8n / Zapier webhook directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the Make / n8n / Zapier webhook connection read-only?
Yes. Every request Silux Chat makes to Make / n8n / Zapier webhook is a look-up (a few vendors use POST for searches); none creates, changes or deletes anything in Make / n8n / Zapier webhook. Give the key or sign-in read-only permissions wherever Make / n8n / Zapier webhook offers them.
Do I need a developer to connect Make / n8n / Zapier webhook?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to Make / n8n / Zapier webhook straight away and shows exactly which features work.
How does the bot know it is really my customer?
It finds the customer in Make / n8n / Zapier webhook by the email or mobile they give, checks their name and one more detail, then sends a one-time code to the mobile or email held in Make / n8n / Zapier webhook — never to one typed in the chat. The code lasts 10 minutes, five wrong attempts cancel it, and a verified session lasts 30 minutes.
What happens if my Make / n8n / Zapier webhook key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the Make / n8n / Zapier webhook connector been tested?
It is Documented-API tested: every capability is run automatically against Make / n8n / Zapier webhook’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own Make / n8n / Zapier webhook account before your bot uses it.
Other custom connectors
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.