Get a Slack Notification for Every New Booking (Zapier Guide)

You can get a Slack notification every time a customer books through Cartoply by connecting the two tools with a Zapier webhook — no code required, takes under 15 minutes. The moment someone picks a time slot, your Slack channel gets a message with the customer name, address, assigned tech, and job time.

This is the fastest way to keep your dispatch team, operations lead, or field manager in the loop without anyone having to check a separate app. Here's exactly how to set it up.

How to Set Up Slack Notifications for New Bookings (Zapier)

1. Step 1: In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app.
2. Step 2: Select Catch Hook as the trigger event, then copy the unique webhook URL Zapier generates.
3. Step 3: In Cartoply, open Settings → Integrations → Webhooks and paste the Zapier URL into the "New Booking" webhook field.
4. Step 4: Make a test booking in Cartoply so Zapier receives sample data and can map the fields.
5. Step 5: Add Slack as the action app, choose Send Channel Message, and build your message using the booking data fields (customer name, address, tech, date/time).
6. Step 6: Turn the Zap on, make one more test booking, and confirm the Slack message arrives in your chosen channel.

Why Generic Booking Tools Make This Harder Than It Should Be

Most scheduling tools treat notifications as an afterthought — you get an email to one inbox, owned by one person. If your dispatcher is away, nobody sees the new booking until someone manually checks the dashboard.

Slack notifications solve the visibility problem. Your whole ops team can watch a #new-bookings channel in real time. You can even route different booking types to different channels — residential jobs to #residential-dispatch, commercial to #commercial-ops — just by creating separate Zaps with filters.

This matters most when jobs come in fast: after a storm pushes a dozen roofing requests through your site at once, or when a new service area goes live and you're not sure if the routing is working correctly. Slack gives your team a live feed to catch problems before a customer falls through the cracks. If you're managing booking links across multiple techs, real-time Slack alerts are how you verify every assignment landed in the right place.

What to Include in Your Slack Booking Message

A useful Slack notification answers the five questions your dispatcher would otherwise have to look up. When you build your Slack message in Zapier's action step, map these fields from the Cartoply webhook payload:

• Customer name — so anyone can search the CRM immediately
• Service address / ZIP code — confirms the territory routing fired correctly
• Assigned tech or rep — the most important field; if this is wrong, you catch it now
• Job date and time — lets dispatch spot conflicts without opening the calendar
• Service type — helps ops prioritize urgent jobs (emergency vs. scheduled maintenance)
• Deposit paid (yes/no) — flags unpaid bookings before the tech drives out

The deposit field is worth highlighting. Cartoply lets you collect a deposit before confirming a booking via Stripe. Including that in your Slack message means your team knows at a glance whether payment was collected — no more chasing customers after the visit.

Filtering Alerts So Slack Doesn't Become Noise

Once you have the basic Zap running, add a Zapier Filter step between the webhook trigger and the Slack action. This keeps your channels clean and actionable.

Useful filters to consider:

• Only alert if deposit is unpaid — sends to a #payment-flagged channel so someone follows up before the job
• Alert by territory — filter on ZIP code or county to route alerts to the right regional channel
• Alert ops lead only for same-day bookings — filter on booking date equaling today's date for urgent dispatch awareness
• Alert by service type — emergency calls go to a high-priority channel; routine maintenance goes to the standard queue

None of this requires any code — every filter is a dropdown in Zapier's visual editor. If you want to go further, Zapier's Paths feature lets you split one webhook into multiple Slack messages simultaneously based on different conditions.

If you're curious how Cartoply stacks up against general-purpose scheduling tools on automation flexibility, the full Cartoply features overview covers what's available natively before you ever need Zapier.

A Quick Benchmark: How Fast Should the Alert Arrive?

On Zapier's free plan, Zaps run on a polling interval — typically every 15 minutes. That's fine for most scheduling use cases, but for high-urgency dispatch (same-day HVAC calls, emergency plumbing) it's too slow.

Upgrade to a paid Zapier plan to get near-instant webhook triggers — usually under 2 minutes. For field service teams where a tech's next job depends on same-day bookings, that delay matters. Budget roughly $20–$30/month for Zapier's Starter plan if real-time speed is a requirement.

As a rough benchmark: teams handling 20+ bookings per day typically find the paid Zapier plan pays for itself in one avoided no-show or one same-day add-on job that wouldn't have been dispatched in time.

Frequently Asked Questions

Can I get Slack notifications for new bookings without Zapier?

Not natively — Cartoply uses Zapier webhooks to push booking data to external tools like Slack. Zapier's free plan supports this workflow, though free-plan Zaps poll every 15 minutes rather than triggering instantly. For real-time alerts, a paid Zapier plan ($20–$30/month) is worth it for active dispatch teams.

What booking data does Cartoply send to Zapier?

Cartoply's webhook payload includes customer name, service address, ZIP code, assigned tech or rep, booking date and time, service type, and payment status. You can map any or all of these fields into your Slack message template inside Zapier's action editor — no coding required.

Can I send booking alerts to different Slack channels based on territory?

Yes. Add a Zapier Filter or Paths step after the webhook trigger and filter on the ZIP code or territory field from the booking. Each path can point to a different Slack channel action. This is useful for multi-region teams where each territory has its own dispatcher or ops channel.

Does this work if I also use the Jobber integration?

Yes. Cartoply's Jobber integration creates a Jobber Request when a booking comes in — that happens independently of the Zapier webhook. The Slack notification fires from the Cartoply booking event, so you get the Slack alert and the Jobber Request created at the same time, from a single customer booking. If you're evaluating scheduling tools that connect with Jobber, see our breakdown of what Jobber scheduling is missing for context on why teams add Cartoply on top.