HappenBoard Pro can post a message in a Slack channel when someone signs up for an event, cancels or checks in. Your team sees it where it already talks, without opening WordPress.
Slack notifications need HappenBoard Pro. See what Pro adds.
Create an incoming webhook in Slack
An incoming webhook is an address Slack gives you to post into one channel.
- In WordPress, go to HappenBoard → Integrations and click Configure on the Slack (Pro) card.
- Click Create one in Slack. Slack’s guide opens: follow its link to create an app, give it a name such as “HappenBoard” and choose your workspace.
- In the app’s settings, open Incoming Webhooks and switch on Activate Incoming Webhooks.
- Click Add New Webhook to Workspace, choose the channel and click Authorize. For a private channel, you must be a member of it.
- Copy the new address under Webhook URLs for Your Workspace. It starts with
https://hooks.slack.com/services/.
Treat this address like a password: anyone who has it can post in your channel.
Connect Slack to HappenBoard
- Back in the Slack (Pro) card, paste the address into Incoming Webhook URL.
- Under Subscribed events, tick the messages you want (see below).
- Click Save changes. HappenBoard refuses any address that is not a Slack incoming webhook and tells you why.
- Click Test ping. A test message with your site’s name appears in the channel. The test uses the saved address, so save first.
Once an address and at least one event are saved, the card shows Active. To stop all messages, empty Incoming Webhook URL and save.
Choose the messages
| Event | Message sent when | Default |
|---|---|---|
| RSVP created | Someone signs up through the RSVP form or gets a ticket, free or paid. | On |
| RSVP cancelled | An attendee cancels with the link in their email, or a refund cancels a paid registration. A cancellation made by your team on the Attendees screen is not posted. | Off |
| Attendee checked in | A ticket is scanned at the door with QR code check-in. | On |
| Check-in undone | A mistaken scan is undone at the door. | Off |
On a busy site, sign-up messages can flood a channel. Keeping only Attendee checked in often gives the team what it needs on the day.
What a message shows
- New sign-up: the attendee’s name (or email when they gave no name), their email, the event and the number of seats.
- Cancellation: the attendee, their email and the event.
- Check-in: the attendee, the event and the time of the scan, in your site’s time zone.
- Check-in undone: the attendee, the event, the seat when the booking has several, and the time.
Each message ends with a View event button that opens the event page on your site.
Messages show attendees’ email addresses, so send them to a private channel if many people can read your team channel.
Good to know
- Messages go to the channel the address was created for. For another channel, create a second webhook in Slack: HappenBoard keeps one address at a time, so the new one replaces the old.
- Messages leave in the background just after the event, so visitors never wait. Slack has five seconds to answer, and a message that fails is not sent again.
- What attendees type is shown as plain text: a name cannot notify your whole channel.
- Nothing is sent to attendees. To send data to another tool rather than people, use outbound webhooks.
Next steps
- Outbound webhooks: send the same moments to Zapier, Make or your CRM.
- WhatsApp notifications: message your attendees rather than your team.
- QR code check-in: the scans behind the check-in messages.