How to Automate Calendly Bookings to ClickUp and Slack Using Make

Introduction

If your team books client time through Calendly, you know how easy it is for details to get lost in email threads or scattered Google Sheets. The manual process of creating a ClickUp task for each booking and then pinging Slack to notify the right people is repetitive and error prone. This guide shows a lean Make.com workflow that listens for new Calendly bookings, creates a ClickUp task, and posts a Slack message — all automatically.

By the end, you’ll be able to deploy a working end to end automation that reduces admin time and surfaces booking details where your team acts on them. This is a practical, hands on pattern you can adapt for other tools as well. No fluff, just what to build and how.

Note: No related Olmec Dynamics posts were found for this exact topic during research.

What you’ll learn

• How to wire Calendly, ClickUp and Slack in a single Make.com scenario
• Field mapping tips so booked slots become meaningful tasks
• How to test and validate an end to end booking flow

What You'll Need

• Calendly account with at least one event type to trigger on new bookings
• ClickUp workspace with a target List for new tasks
• Slack workspace and channel where you want alerts posted
• Make.com account (a basic plan can work for light usage, but plan limits may apply)
• Basic familiarity with Make.com modules and data mapping

How It Works (The Logic)

Trigger: a new Calendly booking is created. Action 1: Make.com creates a new task in ClickUp using details from the booking. Action 2: Make.com posts a Slack message to a designated channel with booking details and the ClickUp task link.

The flow is intentionally simple: one trigger, two actions, one end result in ClickUp and one alert in Slack.

Step-by-Step Setup

1. Create a new scenario in Make.com and add the Calendly module. Choose the trigger that watches for new bookings (New Event Booking).
2. Add the ClickUp module and select Create a Task. Choose the target Space, Folder, and List where new tasks should live.
3. Map the task fields from Calendly to ClickUp. For example:
   • Task name: Booking for {{Event Type}} by {{Invitee Name}}
   • Description: Booking time {{Event Start}}. Invitee: {{Invitee Email}}. Booking URL: {{Invitee Booking URL}}
   • Due date: {{Event Start}}
   • Assignee: assign to the appropriate teammate or role
   • Tags/Custom fields: add any booking type or client tags you use
4. Add the Slack module and set Post a Message to a channel. Craft a message like:
   • New Calendly booking: {{Invitee Name}} for {{Event Type}} at {{Event Start}}. Link: {{Invitee Booking URL}}. Click to view task: {{ClickUp Task URL}}
5. Ensure data mappings flow from Calendly to ClickUp and then propagate the task URL to Slack. Test by creating a sample booking in Calendly and watching Make.com run.
6. Turn on the scenario. Set up a reasonable schedule so the scenario checks for new bookings as they come in.
7. Validate end to end. Check Calendly for a new booking, verify a ClickUp task appears, and confirm the Slack alert posts correctly.
8. Add a quick test run with a real booking to confirm the task title, description, and URL link updates in Slack as expected.

Real-World Business Scenario

A small consulting agency uses Calendly for client meetings. When a booking comes in, they want a new task in ClickUp for the assigned consultant and a Slack alert to the client success channel. This setup eliminated about 15 minutes of manual data entry per booking and reduced the chance of missing meeting details. The ClickUp task now contains the booking type, client name, and a direct link to the Calendly booking, while Slack keeps the team informed in real time. This pattern is simple enough for a single team and can scale as you add more event types or Slack channels.

Common Variations

• Add a conditional path to only create ClickUp tasks for bookings of a certain type or duration, and skip others.
• Extend with a document generation step to create a calendar agenda or introduction note in PandaDoc or Google Docs, then attach it to the ClickUp task.
• Log every booking in a separate Airtable or Google Sheet for a centralized booking ledger, with links back to ClickUp tasks and Calendly bookings.

Closing thoughts

This 3 step Make.com workflow gives you a reliable, low friction way to turn Calendly bookings into actionable work and timely Slack alerts. It minimizes manual data entry while keeping everyone aligned around the latest client bookings. If you want similar automations tailored to your business, Olmec Dynamics builds these end to end integrations and more. Learn more about our practical automation work at Olmec Dynamics.