What "Automation" Actually Means Here
Connecting Slack to Meetario gets you instant notifications, but a real automated workflow goes further: routing different bookings to different places, triggering follow-up actions, and giving you a full audit trail of what fired and when. Meetario supports this at two levels — a simple built-in layer and a flexible webhook layer for anything more advanced.
Layer 1: Built-In Slack Notifications
Once you connect Slack under Account → Integrations, Meetario automatically posts three message types to your chosen channel with zero further setup: new bookings, cancellations, and pre-meeting reminders. If you have not done this yet, see our guide on setting up Slack booking notifications first — everything below builds on that foundation.
This layer is intentionally simple: one channel per connected user, fixed message format. For most solo users and small teams, it is all you need. For teams that need routing logic, move to Layer 2.
Layer 2: Custom Webhooks for Advanced Routing
Under Account → Webhooks, Meetario lets you create outbound webhooks that fire on specific events: booking.created, booking.confirmed, booking.cancelled, booking.rescheduled, booking.completed, booking.no_show, reminder.sent, payment.completed, and payment.failed. Each webhook can be scoped with filters — for example, only firing for bookings on a specific event type — and Meetario tracks every delivery attempt with response codes, retry counts, and full payload logs so you can debug failures.
This is where channel routing by event type comes in. Slack's native incoming-webhook integration only supports one channel per connected user, but you can point a Meetario custom webhook at a tool like Zapier or Make.com, which then posts to whichever Slack channel makes sense based on the payload:
- Create a webhook filtered to your "Enterprise Demo" event type, pointing to a Zapier or Make.com endpoint that posts to
#enterprise-sales. - Create a second webhook for your "Support Call" event type, routed to
#support-teaminstead. - Use the
booking.no_showevent to alert a manager channel whenever a guest misses a meeting, so someone can follow up.
Automated Reminders Reduce No-Shows
The reminder.sent event and the built-in Slack reminder notification both fire automatically before a scheduled meeting, giving the host a nudge with a one-click join link. Combined with the automated email reminder sent to the guest, this closes the loop on the most common cause of no-shows: people simply forgetting.
Combining Automation with Round Robin and Calendar Sync
If you run round-robin event types across a team, the new booking notification is sent to whichever team member Meetario actually assigns as host — automation follows the assignment logic automatically. Layer that with Google Calendar sync (see our guide on connecting Google Calendar) and every booking is conflict-checked, added to the assigned host's calendar, and announced in Slack without anyone touching a spreadsheet.
Setting Up Your First Automation
- Go to Account → Webhooks → Create Webhook.
- Give it a name and paste in the destination URL — a Zapier "Catch Hook" trigger, a Make.com webhook, or a custom endpoint you control.
- Select which events should trigger it (start with
booking.created). - Optionally set filters to scope it to a specific event type.
- Use the Ping button to send a test payload and confirm delivery before going live.
- Check the Deliveries tab after a real booking to confirm the HTTP status and response time.
Frequently Asked Questions
Can I filter webhooks by event type?
Yes. When creating a webhook under Account -> Webhooks, you can scope it to a specific event type so it only fires for bookings on that page. This is how you build per-event-type channel routing — create one webhook for your "Sales Demo" page pointed at #sales via Zapier, and a separate webhook for "Support Call" pointed at #support. If you leave the filter blank, the webhook fires for all event types across your account.
How do I test webhook delivery?
Every webhook in Meetario has a Ping button that sends a sample payload to your endpoint immediately. Use this to confirm your Zapier or Make.com trigger is receiving data before any real bookings happen. After a real booking fires, check the Deliveries tab on the webhook detail page — it shows the HTTP status code, response body, and timestamp for every delivery attempt, making it easy to diagnose failures without guessing.
What happens if my webhook endpoint is down?
Meetario retries failed webhook deliveries automatically with exponential backoff. If your endpoint returns a non-2xx status code or times out, Meetario will retry several times over the following hours. Every attempt is logged in the Deliveries tab with the error details, so you can see exactly when the endpoint came back online and whether the payload was eventually accepted. While the endpoint is down, your built-in Slack and email notifications continue working normally — webhooks are an additional layer, not a replacement.
Can I use webhooks without Zapier or Make?
Absolutely. Meetario's webhooks send a standard HTTP POST with a JSON payload to any URL you provide. If you have a custom server, a serverless function (AWS Lambda, Cloudflare Workers), or any HTTP endpoint that can accept POST requests, you can point a webhook directly at it. Zapier and Make.com are just convenient no-code options for teams that do not want to write their own endpoint. For developers comfortable with server-side code, going direct gives you full control over the payload handling logic.
Next Steps
Start with the built-in Slack notifications for immediate visibility, then layer in custom webhooks once you know exactly which bookings need to go where. For team-specific routing patterns, read our guide on Slack team booking workflows next. If you are setting up calendar sync alongside your automation, our Slack + Calendar integration guide shows how to combine all three tools into a single workflow.