How to Automatically Post New ClickUp Tasks to Slack Using Make.com

Automate ClickUp to Slack: stop manual task forwarding

When a new task is created in ClickUp, someone on your team has to notice it, then forward the link into Slack. That creates delays, missed updates, and threads nobody can trace back to the source task.

With an XPA using Make.com, you can watch ClickUp for newly created tasks and post a structured Slack message immediately. By the end, you will have a working ClickUp → Make.com → Slack automation with filters and field mappings you can trust.

What You’ll Need

• Make.com (scenario creation and run permissions, paid plan may be required depending on your usage)
• ClickUp workspace access
• Slack workspace access, plus a bot (or user token) allowed to post to your channel
• In ClickUp, access to the Space and/or List you want to monitor

How It Works (The Logic)

When a new task is created in your chosen ClickUp list (trigger in Make.com), Make.com reads task fields like name, URL, due date, and assignees (mapping), then sends a Slack channel message using a consistent template. If you add a filter step, Make.com only posts tasks that match your criteria.

Step-by-Step Setup

1) Create a new Make.com scenario

1. Open Make.com and click Create a new scenario.
2. Add the first app as ClickUp.

2) Add the ClickUp trigger for new tasks

1. Choose a ClickUp trigger that watches for new task creation (commonly a “watch tasks” style trigger with a “new task” event).
2. Configure scope:
   • Select the Space you want to monitor.
   • Select the List inside that Space.

Gotcha to check: Make.com’s ClickUp trigger output structure can vary based on the module version and what you enable in that trigger. Do not assume field names, always verify with a live test run.

3) Add a filter to prevent Slack spam

1. Add a Filter module directly after the ClickUp trigger.
2. Use conditions based on fields that your trigger returns. Practical filters include:
   • status is in: To Do, In Progress (or whatever your workflow uses)
   • due date is not empty
   • priority equals a specific value (optional)

If your trigger does not return a field you want to filter on (for example, a custom field), you will handle it in a later variation by adding a task details step.

4) Add the Slack action to post the message

1. Add a Slack module as the next step.
2. Choose the action to send/post a channel message.
3. Select the channel.
4. Build the message text using mapped ClickUp fields.

A reliable Slack template:

• Line 1: New ClickUp task: {{task.name}}
• Line 2: {{task.url}}
• Line 3: Due: {{task.due_date}} | Assignees: {{join(", ", task.assignees[].name)}}

5) Handle blank fields with the simplest approach

If you see blank due dates or assignee fields:

• Confirm the trigger output includes those fields for your specific task.
• If due date is frequently missing, keep the automation clean by filtering those tasks out (Step 3) rather than forcing formatting.

6) (If needed) Fetch full task details before posting

If your trigger output lacks custom fields or deeper metadata, insert an extra ClickUp module before Slack:

1. Add a Get Task (or equivalent task details) action.
2. Use the task ID from the trigger to fetch details.
3. Map Slack fields from the details module output instead.

7) Test with one real task

1. Create a test task in ClickUp in the exact list you configured.
2. Run the scenario once in Make.com.
3. Verify:
   • The trigger fired once
   • The filter passed (or did not pass, if expected)
   • The Slack message contains the correct link and fields

8) Turn the scenario on

Switch the scenario to On only after your test run produces the message you want. For an XPA, the first real run is where you catch message formatting mistakes and unexpected noise.

Real-World Business Scenario

A UK logistics coordinator uses ClickUp to track client onboarding steps across multiple lists. Previously, internal updates happened in meetings, and Slack only saw tasks when someone manually posted them.

After adding this Make.com ClickUp to Slack automation, every newly created onboarding task appears in a dedicated Slack channel with the task link and due date context. The coordinator also uses the filter to only post tasks that match the “action required” statuses, so the channel stays readable instead of becoming a firehose.

Common Variations

1. Route tasks by list into different Slack channels

   • If you monitor multiple lists, add branching or separate scenarios per list so each team gets the right channel.

2. Post only when a specific custom field equals a value

   • Add a task details step (Step 6), then filter using the returned custom field.

3. Include a short status line when tasks are created

   • Extend the Slack message template to add Status: {{task.status}} and keep the format consistent.

A clean ClickUp → Slack XPA, with less noise

You built an XPA that does one job well: ClickUp new-task event in Make.com, then a structured Slack channel message. The two practical reliability choices are early filtering and verifying trigger field mappings with a real test task.

If you want help designing the message format, selecting the right trigger event, and making the field mapping robust for your custom fields, Olmec Dynamics builds these automations end to end. Start with a quick overview of Cross-Platform Automation (XPA) and see more about Olmec Dynamics.

Note: no related internal posts were found specifically for the exact ClickUp → Slack Make.com pattern yet.