Integrations
Webhooks
Send a signal to another tool when something happens in yours. What a webhook is, which events exist and how to connect one to Zapier or Make.
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 or a notification in Slack. You don’t need any code, only the address the service on the other end gives you.
You’ll find them under Settings → For developers → Webhooks.
Do you need a webhook?
Usually not. Automations cover nearly everything inside Idun Blue, such as emails, tags and course access. See Get started with automations.
A webhook is for when something should happen outside Idun Blue, for example in a spreadsheet or another tool you already use.
Create one
- Go to Settings → For developers → Webhooks.
- Click Add webhook.
- Fill in:
- URL: the address the receiving service gave you.
- Signing secret: leave it empty and one is created for you. Every message is signed with it (HMAC SHA-256, in the
X-Webhook-Signatureheader), so the receiver can check that it came from you. - Active: the switch that decides whether it sends.
- Tick the Events that should send something.
- Click Save.
Quick templates has five ready-made setups: new member, new order, course completed, new subscriber (a submitted form) and booking made.
The events
Money: Checkout completed · Purchase · Subscription cancelled · Trial ending · Payment failed
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
Live events: Attended a live event · Missed a live event
Only tick what you’ll use. Email opened and Page visited can send a great many messages.
Connect to Zapier
- In Zapier: create a new Zap with the trigger Webhooks by Zapier → Catch Hook.
- Zapier gives you an address. Copy it.
- In Idun Blue: create a webhook with that address and tick the events.
- Do something that triggers the event, such as a test purchase or a filled-in form, so Zapier can see what the message looks like. Test in the webhook’s menu sends a test message.
- Build the action in Zapier and switch the Zap on.
Connect to Make
- In Make: a new scenario with Webhooks → Custom webhook.
- Copy the address Make gives you.
- In Idun Blue: create the webhook with that address.
- Trigger the event so Make can see the structure.
- Build the rest of the scenario and activate it.
See whether it works
Every webhook has a Delivery log with each message sent and the receiver’s answer. A failed message can be sent again with Retry.
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 in the log at what was sent before you build anything on top of it.
Tips
- Make one webhook per service. Then the log shows which service is playing up.
- Look at the log a few times in the first weeks, so errors don’t sit unnoticed.
