Automate Calendly bookings to ClickUp tasks with Slack using Make.com

Introduction

If you use Calendly, you already know the annoying part: every booking creates admin work. Someone has to copy the client details, create a task in ClickUp, and then message the right person in Slack so they can prep and follow up.

This is the kind of Cross-Platform Automation (XPA) that pays off fast. In this post, you will build a Make.com scenario that automatically creates a ClickUp task from a new Calendly booking and posts a Slack message with the task link.

By the end, you will know how to wire the trigger, map the fields, and avoid duplicate tasks when Make retries.

What You'll Need

• Calendly account with access to the webhook or Make integration for your booked event
• Make.com account with the Calendly, ClickUp, and Slack apps connected
• ClickUp access:
  • permission to create tasks
  • a specific List where tasks will be created
• Slack access:
  • permission to post messages to your target channel
• A decision on your dedupe key:
  • easiest option is the Calendly event ID mapped into a ClickUp field or into the task name

How It Works (The Logic)

When a new booking is created in Calendly, Make.com receives the booking payload. Make.com then:

1. Uses the Calendly event ID as a stable identifier to prevent duplicates.
2. Creates a ClickUp task in your chosen List, or skips if the task already exists.
3. Posts a Slack message containing the client name, booking time, and the ClickUp task link.

That trigger, create-if-missing action, plus Slack notification is the whole XPA pattern.

Step-by-Step Setup

1) Create the Make.com scenario

1. Log into Make.com and create a new scenario.
2. Name it clearly, for example: Calendly → ClickUp task + Slack notify.

2) Add the Calendly trigger

1. Add a module for Calendly.
2. Pick the trigger that fires when a booking is created (commonly an event like booking created).
3. Connect your Calendly account.
4. Run the scenario test, so Make shows you the booking fields you can map.

Gotcha: If your test booking does not trigger, check that your Calendly event/webhook is enabled for the correct calendar and workspace, then create a real new booking to confirm the payload Make receives.

3) Add a ClickUp “find existing task” step for deduplication

This is what stops duplicate tasks when a webhook is retried.

1. Add a ClickUp module that searches for an existing task.
2. Use a value that you can reconstruct reliably from Calendly.

Two practical search patterns:

• Pattern A (fast, simple): Include CalendlyEventId:{event_id} in the ClickUp task name, then search by partial match.
• Pattern B (cleaner): Store the Calendly event ID in a ClickUp custom field (or equivalent field you can search), then search by exact match.

If you want a reference example of the same wiring style, see How to Create ClickUp Tasks from Calendly Bookings Using Make.com and Slack.

4) Add an IF decision: “task exists?”

1. Add a router logic module (in Make you will typically use a conditional/router block).
2. Condition: if the ClickUp search returned zero results.

Route A (true): create the task, then notify Slack. Route B (false): skip creation. Optionally post a quiet audit message somewhere else, but most teams keep Slack clean and do nothing.

5) Create the ClickUp task

On Route A, add a ClickUp module to create a task.

1. Select the target List.
2. Map fields.

A baseline mapping that works well:

• Task name: Booking: {Event Name} - {Invitee Name} (CalendlyEventId:{event_id})
• Description: include at least:
  • Invitee email
  • Booking start time
  • Any notes you need from Calendly
• Due date or start date (choose one): use the booking start time.

Gotcha: Timezone mapping is the most common reason due dates look “off by a few hours.” Use the booking start time field from the Calendly payload, then sanity-check one test booking.

6) Post the Slack message with the ClickUp link

1. Add a Slack module to send a message.
2. Choose the channel your team actually monitors.
3. Build the message with clear next-step text.

Example message content:

• New booking received: {Invitee Name} for {Event Name}
• When: {Booking Start}
• ClickUp task: {task_url}

If you prefer a shorter build order, this same flow is also documented here: Calendly to ClickUp: Build a 5-minute Make.com Scenario to Create Tasks and Post to Slack.

7) Add a small “failure to Slack” path

Make.com scenarios fail occasionally due to rate limits, permission changes, or temporary API issues.

• Create an error handling route that sends a message to a dedicated channel like #automation-errors.
• Include the Calendly event ID in the error message so you can trace the booking quickly.

8) Test with 2 bookings and verify dedupe

1. Turn the scenario on.
2. Make two new Calendly bookings.
3. Confirm:
   • One ClickUp task per booking
   • One Slack message per booking
   • If you rerun the scenario on the same payload (or if Make retries), you do not create duplicates

Real-World Business Scenario

A coaching firm uses Calendly for discovery calls. Before this XPA workflow, the operations admin copied booking details into ClickUp and then messaged a Slack channel so the assigned coach could prepare.

With the Make.com automation in place, every new booking becomes a ready-to-work ClickUp task immediately, with the booking start time and a consistent task name format. Slack gets a single alert containing the task link, so the coach can prep without opening multiple tools.

Common Variations

1. Assign to different ClickUp owners by booking type

   • Map Calendly’s event name or a custom field to the ClickUp assignee field.

2. Add a prep checklist after the task is created

   • Right after the ClickUp create task step, add another module that adds a templated checklist.
   • This approach pairs well with meeting prep templates, covered in How to Create ClickUp Tasks with Templated Checklists and Zoom Links from Calendly Using Make.com.

3. Handle reschedules and cancellations

   • Build a second scenario for the Calendly “updated” and “canceled” events.
   • Locate the task using the same Calendly event ID and update due dates or post a Slack update.

Keep Calendly, ClickUp, and Slack aligned

You built a simple XPA workflow: Calendly booking created triggers Make.com, Make.com creates a deduped ClickUp task, then Slack notifies your team with the task link.

If you want this tailored to your exact ClickUp List structure, custom fields, and Slack routing rules, Olmec Dynamics builds these integrations for businesses like yours. Start by reviewing our Cross-Platform Automation (XPA) approach, or explore more examples on our site.