Webhooks

A webhook is a message Idun Blue sends to another system when something happens in yours. Someone buys — and a row appears in your spreadsheet, a notification in Slack, a contact in another register.

You don’t need to code. You need an address to send to, and the service you’re connecting gives you that.

You’ll find them under Settings → Webhooks.

Do you need a webhook?

Most people don’t. Automations cover nearly everything inside the platform — emails, tags, course access. See Get started with automations.

A webhook is for when something should happen outside Idun Blue: in a spreadsheet, in an accounting system, in another tool you already use.

Create one

1. Go to Settings → Webhooks.
2. Click to add a new one.
3. Fill in:
   • URL — the address the receiving service gave you.
   • Secret — optional, used so the receiver can check the message really came from you.
   • Active — the switch that decides whether it sends.
4. Tick the Events — which things should send something.
5. Save.

There are also five ready-made templates for the most common cases: new member, completed checkout, completed course, submitted form and new booking.

The events

Money — Checkout completed · Purchase · Subscription cancelled · Checkout abandoned · Trial ending

Courses — Enrollment · Enrollment created · Lesson completed · Course completed

People — Member created · Tag added · Tag removed · Inactivity

Email and pages — Email opened · Email clicked · Page visited

Sign-ups — Form submitted · Booking created · Booking cancelled

Only tick what you’ll actually use. Email opened and Page visited can send an awful lot of messages.

Connect to Zapier

1. In Zapier: create a new Zap with the trigger Webhooks by Zapier → Catch Hook.
2. Zapier gives you an address. Copy it.
3. In Idun Blue: create a webhook with that address and tick the events.
4. Do something that triggers the event — buy a test product, fill in your form — so Zapier can see what the message looks like.
5. Build the action in Zapier and switch the Zap on.

Connect to Make

1. In Make: a new scenario with Webhooks → Custom webhook.
2. Copy the address Make gives you.
3. In Idun Blue: create the webhook with that address.
4. Trigger the event so Make can see the structure.
5. Build the rest of the scenario and activate it.

See whether it works

Every webhook has a delivery log. Open it to see each message sent and whether the receiver answered as it should.

Repeated errors are nearly always a wrong address, or the receiving service being switched off.

If it doesn’t work

• Nothing is sent — check the webhook is Active and that the right events are ticked.
• Errors in the log — check the address character by character, and that the service at the other end is on.
• The wrong data arrives — trigger the event once and look at what was actually sent in the log before you build anything on top of it.

Tips

• One webhook per service. Don’t mix Zapier and your accounting system in the same one.
• Give them names you understand: “New purchases to Google Sheets”.
• Look at the log once a week for the first few weeks. Errors sitting unnoticed for a month become a month of missing data.