Decide what the channel should hear about
A channel that posts every change quickly becomes noise, so choose before you build. Shoal can tell another tool about four things: someone registers, someone joins the waitlist, someone cancels and someone checks in.
- Registrations and cancellations suit a planning channel
- Waitlist joins tell you when it may be time to raise capacity or choose a bigger plan
- Check-ins are most useful on event day, in a channel for the people running the door
Get a webhook address from your automation tool
A webhook is an address that another tool listens on. In Zapier, create a Zap and choose Webhooks by Zapier with the Catch Hook trigger. In Make, create a scenario and start it with the Custom webhook module. Either one gives you an address to copy.
Shoal doesn't have its own Zapier app, so this built-in webhook step is the way in. Webhooks by Zapier is only on Zapier's paid plans, while Make's webhook module is available on its free plan.
Add the webhook in Shoal
Owners and admins find Webhooks on the API page. Paste the address, tick what you want to hear about under Send When, and choose one event or leave All Events to cover your whole organization. Then choose Add Webhook and Send Test.
The test sends a ping message, so your automation tool has a real sample to show you. Real messages carry the event's name, plus the person's name, email, job title, company, track, ticket link and registration answers.
Turn the message into a chat post
Add a step after the webhook: Slack's Send Channel Message, or the Microsoft Teams action that posts to a channel. Write the message with the fields from the sample, such as the person's name, company and the event name, for example: New registration for Tech Summit: Sam Lee, Acme.
Keep the message short and leave out anything private. Registration answers can include things like dietary needs, and a busy channel is rarely the place for them.
Send different events to different places
Each message carries its type, such as attendee.registered or attendee.checked_in. Add a filter or router step in your automation tool so registrations go to one channel and check-ins to another. You can also add a separate webhook in Shoal for each channel and tick only the changes it needs.
Check that messages are really from you
Every Shoal webhook has its own signing secret, and each message carries a signature made with it. A developer can check the signature before trusting a message. The built-in steps in Zapier and Make don't check it for you, so keep the webhook address private and treat it like a password.
Expect the occasional repeat
If your tool is down when a message is sent, Shoal tries again, up to seven tries over about a day, so the same message can occasionally arrive twice. Every message has a delivery id you can use to skip repeats. A webhook that has failed for three days is switched off, and you can switch it back on from the API page.