ClickUp ships a native Slack integration. In ClickUp Settings → Integrations → Slack, you connect a Slack workspace and configure which events — task status changes, assignments, comments, due date reminders — post to which channels. For Slack-first organizations, this works well.
ClickUp also ships a Microsoft Teams app. The Teams app lets you create ClickUp tasks directly from Teams messages, preview ClickUp links in Teams, and search for tasks using the Teams search bar. What it does not do is route ClickUp task events to Teams channels as real-time notifications.
The Notification Gap
When a task status changes from In Progress to In Review in ClickUp, the Slack integration fires — the project Slack channel gets the update. The Teams notification never fires. The project manager, the executive sponsor, the account manager — anyone whose primary workspace is Teams sees nothing until they open ClickUp or someone forwards the Slack message.
For organizations that standardized on ClickUp as their project management layer across a mixed Slack/Teams communication stack, this asymmetry creates a daily coordination overhead: Slack users are notified automatically; Teams users rely on manual updates.
What ClickUp Supports Natively
Slack integration (Settings → Integrations → Slack): Routes task created, task status changed, task assigned, comment added, due date changed, and goal milestone reached to a Slack channel. Customizable per-Space or per-List. Well-maintained, official integration.
Teams app (Microsoft AppSource): Task creation from Teams messages. ClickUp link preview cards in Teams. Task search via Teams search. No notification routing from ClickUp to Teams channels.
Automations with Webhook action (Business plan and above): ClickUp Automations support a Webhook action that POSTs a JSON payload to any URL when a trigger fires. This is the configuration layer SyncRivo uses.
The SyncRivo Routing Layer
SyncRivo acts as a unified webhook receiver. Configure a ClickUp Automation with a Webhook action pointing to your SyncRivo inbound endpoint. SyncRivo routes the ClickUp payload to every platform in your routing configuration simultaneously — Slack, Teams, Webex, Google Chat, Zoom — with per-trigger, per-channel routing rules.
The ClickUp Automation fires once. Every platform receives the event.
Routing Patterns for Common ClickUp Workflows
Cross-functional project teams:
- Status → Done (milestone task): Slack #project-team + Teams #leadership simultaneously
- Task assigned: Assignee's native platform (Slack DM for developers, Teams DM for account managers)
- Due date approaching: Assignee's preferred platform, 24h before deadline
Agency/client delivery teams:
- Status → In Review: Slack #reviewers (internal team)
- Status → Delivered: Teams channel (client stakeholders on Teams)
- Status → Blocked: Slack #project-team + Teams #account-management simultaneously
Executive reporting:
- Goal milestone reached: Teams #executive-channel
- Sprint close (all tasks in Closed): Weekly digest to Teams #leadership
Setup Steps
Step 1: In SyncRivo, connect your Slack workspace and Teams tenant via OAuth2. Copy the generated inbound webhook URL.
Step 2: In ClickUp, open a Space or List. Go to Automations and create a new Automation. Set the trigger — status change, assignment, due date, comment. Add a Webhook action and paste your SyncRivo URL.
Step 3: In SyncRivo, configure routing rules. Route different trigger types to different channels — status completions to project channels, urgent tasks to leadership, due date reminders to the assignee's platform.
Step 4: Test by changing a task status. Verify delivery in all configured Slack channels and Teams channels simultaneously.
For the complete ClickUp Automation webhook setup, routing matrix by trigger type, and per-Space routing configuration, see the ClickUp Notifications in Slack & Teams integration guide.
Ready to connect your messaging platforms?
