Your quiz leads in all your tools, by webhook

What you can do with it

• File your leads in a spreadsheet: Make or n8n receives the lead and adds a row to Google Sheets, with the profile and the score.
• Send them to another CRM: HubSpot, Pipedrive, Brevo, ActiveCampaign, through a Make or n8n scenario, with the right tag for each profile.
• Get notified live: a Slack or Discord message, or a text, as soon as a lead gets the profile that buys the most.
• Feed your own website: your database, your member area, your in-house tool, receiving clean, documented JSON.

Set it up in four steps

Count five minutes the first time. Each step says which tool you are in.

1. 1

   Step 1 : Get the receiving address

   In your tool

   In your tool, create a webhook entry point. In Make, it is the Webhooks > Custom webhook module. In n8n, the Webhook node with the POST method. Copy the address it gives you: it starts with https://.

2. 2

   Step 2 : Add the webhook in Tiquiz

   In Tiquiz

   Go to Settings, Connections tab, Webhook card. Give it a name ("Make", "My site"), paste the address, and click Add the webhook.

   If your tool asks for a secret (an X-Secret or Authorization header), put its name and value in Secret header. It is encrypted and never shown again.

3. 3

   Step 3 : Test it with a real quiz

   In Tiquiz

   Click Test the webhook. Tiquiz sends a sample lead built on your own quiz: your real profile names, your real questions. You see right away what your server answered, and how fast. In Make or n8n, this test also lets the tool learn the data structure.

4. 4

   Step 4 : Pick the quiz destination

   In Tiquiz

   Open the quiz, Create tab, and set Where this quiz's leads go to your webhook. That's it: every new lead goes to that address. The quiz's Automate tab lists the tags your tool will receive.

What your tool receives

A JSON POST, with the most useful fields flat at the top (for tools that only read one level), and the full detail nested below.

{
  "version": 1,
  "event": "lead.created",
  "event_id": "5b0d3c1e-8a2f-4c55-9f1e-2a7d6c0b9e41",
  "test": false,
  "sent_at": "2026-10-07T09:14:03.512Z",
  "source": "tiquiz",
  "email": "[email protected]",
  "first_name": "Camille",
  "last_name": "Martin",
  "full_name": "Camille Martin",
  "phone": null,
  "country": "US",
  "profile": "The Busy Strategist",
  "profile_tag": "quiz-busy-strategist",
  "profile_slug": "the-busy-strategist",
  "profile_id": "9c1f…",
  "score_percent": null,
  "tags": ["quiz-busy-strategist"],
  "quiz_id": "3e7a…",
  "quiz_title": "What kind of entrepreneur are you?",
  "consent": true,
  "lead": { "…": "the full contact, custom fields included" },
  "result": { "…": "the profile obtained, its tags" },
  "score": null,
  "answers": [
    { "position": 1, "question": "Your first move on Monday morning?", "answer": "I write my to-do list" }
  ],
  "quiz": { "…": "title, type, language, public URL" },
  "affiliate": null
}

To route your leads, read profile (the profile name, identical for everyone) or profile_tag. tags carries all of the lead's tags: profile, survey answers, score ranges.

event says what triggered the send: lead.created (new lead), lead.shared (the lead shared their result), lead.resent (resent from My leads) or lead.test. event_id is unique: use it to ignore a duplicate.

Reliable and secure

• A temporary outage doesn't cost a lead. If your server doesn't answer, takes more than 10 seconds, or returns a server-side error (5xx, 429), Tiquiz retries twice, after 2 then 8 seconds. A clear refusal (400, 404) is not retried: it would not change.
• A rejected secret warns you. If your server answers 401 or 403, the connection switches to "the server rejects the secret" and you get one email, once.
• Every send is logged. The Webhook card shows the latest sends: the event, the response code, the duration.
• Protected addresses. https only, no redirect followed, no private or local address accepted. A switch pauses the webhook without deleting anything.