How to Create ClickUp Tasks from Calendly Bookings Using Make.com and Slack

Introduction

You get a Calendly booking, someone manually creates a task in ClickUp, and the important details get missed or typed incorrectly. That manual loop costs time and causes handoffs to stall, especially when bookings come in outside core hours.

Automating the flow so every Calendly booking becomes a ClickUp task and posts a short message to Slack removes that friction. By the end you will have a small Make.com scenario that captures booking fields, creates a task with the right assignee and due date, and notifies the team in Slack.

What you will know by the end: the exact Make.com modules to use, the field mappings to map Calendly payloads to ClickUp task fields, and the common gotchas to avoid.

What You'll Need

• A Calendly account with webhook access or API key, Calendly webhooks require a paid plan
• A ClickUp account with API access and permission to create tasks in the target List
• A Slack workspace with permission to post into the target channel
• A Make.com account with Calendly, ClickUp, and Slack connections (free tier can work for light use, paid plan recommended for production webhook volume)
• A simple mapping plan: target ClickUp List ID, default assignee ID or routing rule, and task naming convention

How It Works (The Logic)

When a new booking is created in Calendly, Calendly sends the booking payload to Make.com. Make.com extracts invitee name, email, event start time, and any answers to invitee questions. Make.com then creates a task in ClickUp in the chosen List, maps the start time to the task due or start date, optionally assigns the task, and finally posts a concise Slack notification with a link to the new ClickUp task and the booking summary.

Trigger (Calendly booking) → Parse booking fields → Create ClickUp task → Post Slack message

Step-by-Step Setup

1. Create the Calendly webhook or prepare the trigger

• In Calendly, create a webhook subscription for the event.created event type. Calendly requires a paid plan for webhooks.
• For testing, use the Make.com Calendly "Watch Events" trigger and create a test booking to fetch a sample payload.

Common gotcha: group events return multiple invitees. Decide whether to create one task per invitee or a single task for the event before you build.

2. Start a new Scenario in Make.com and add the Calendly trigger

• Add the Calendly module "Watch Events" (or "Watch Invitees" depending on connector versions).
• Select the specific event types to monitor or leave blank to capture all event types. Pull a sample payload by making a real test booking.

3. Parse or map the booking fields you need

From the Calendly payload, map these values to variables you will use later:

• Invitee name (or split into first and last name)
• Invitee email
• Event start time (ISO timestamp)
• Event end time if you need duration
• Answers to custom invitee questions (for example, meeting purpose or project code)
• Event location or conference link

Gotcha: Calendly timestamps include timezone. Use Make.com date functions to convert to your workspace timezone or to epoch milliseconds if ClickUp requires that format.

4. Add ClickUp: Create a Task module

• Add the ClickUp "Create a Task" module and point it at the target Workspace, Space, Folder and List.
• Map fields as follows:
  • Task name: "Meeting: {{event_name}} — {{invitee_name}}"
  • Description: include invitee email, invitee answers, meeting link, and original Calendly booking URL
  • Start date or Due date: map from Calendly event start time. If ClickUp expects epoch milliseconds, convert the ISO time with Make.com date functions, for example: formatDate(convertTimezone({{start_time}}; "UTC"; "Europe/London"; "X") )
  • Assignees: use a default assignee ID, or implement a simple conditional mapping based on an invitee answer or event type
  • Custom fields: map any booking answers to ClickUp custom fields if your List uses them

Common gotcha: ClickUp connectors sometimes expect timestamps as integers. Test the date format and adjust before enabling the scenario.

5. Optionally add a filter to skip low-value or internal bookings

• If you only want tasks for specific event types, add a Make.com filter before the ClickUp step. Example: continue only when event type equals "Sales Discovery" or when a required invitee question equals "Request follow-up".

6. Add Slack: Post a message to the team channel

• Add the Slack "Post a Message" module in the target channel.
• Build a concise message and use the ClickUp task URL returned by the Create Task module. If the connector returns only a task ID, construct the URL with your workspace and task ID pattern.

Example message format:

New booking from Jane Doe — Discovery Call
When: 2026-04-20 10:00 (BST)
ClickUp: <https://app.clickup.com/t/{{task_id}}|Open task>
Email: jane@client.com
Notes: Requested a product demo

Gotcha: Make sure the Slack app used in Make.com has permission to post in the channel. Test mobile display to confirm line breaks and link formatting work.

7. Test the full flow with a live Calendly booking

• Create a real test booking that matches your filters and confirm the webhook triggers in Make.com.
• Verify a task appears in ClickUp with correct dates, description, and custom field values.
• Check Slack to ensure the message includes the ClickUp link and expected booking details.

8. Turn the scenario on and monitor the first few runs

• Activate the scenario and review the first week of bookings. Look for timezone mismatches, missing emails for group events, or skipped fields when invitee answers are optional.
• Tweak date conversions and filters until task creation matches your daily process.

Real-World Business Scenario

A small consultancy uses this flow for discovery calls. Every booked call creates a ClickUp task assigned to the lead owner, with the meeting link and client answers in the description. The operations channel in Slack gets a one-line alert so the delivery lead can prepare. This removed manual task creation and cut first-response time by hours on new leads.

If you already capture leads with forms, combine this pattern with a form-to-CRM flow. For a matching mapping approach see our guide on connecting Typeform to HubSpot: How to Connect Typeform to HubSpot and Auto-Create New Leads Using Make.com.

Common Variations

• Create tasks only for selected event types: add a filter so only sales or onboarding event types create tasks.
• Assign tasks dynamically: use a small lookup table in Google Sheets or a ClickUp custom field to route bookings to the right assignee based on service or region.
• Add a pre-meeting checklist: after task creation, append a checklist template using ClickUp's checklist module so every meeting has the same prep steps.

How this helps your team

You now have a minimal Make.com scenario that converts Calendly bookings into actionable ClickUp tasks and notifies the team in Slack. The build reduces manual entry, captures full booking context, and enforces consistent handoffs. If you want this implemented across your Calendly, ClickUp, Slack, and other tools, Olmec Dynamics builds these automations for real businesses. See our guide to ClickUp status alerts for related patterns: How to Automatically Notify Slack When a ClickUp Task Changes Status Using Make.com.