See llms.txt for all machine-readable content.

ClickUp and Microsoft Teams integration

Save yourself the work of writing custom integrations for ClickUp and Microsoft Teams and use n8n instead. Build adaptable and scalable Productivity, Communication, workflows that work with your technology stack. All within a building experience you will love.

How to connect ClickUp and Microsoft Teams

Create a new workflow and add the first step

In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.

ClickUp and Microsoft Teams integration: Create a new workflow and add the first step

Distribute summarized meeting notes with Microsoft Teams and ClickUp

This workflow processes raw meeting recordings or handwritten notes, automatically transcribes and summarizes them, and then distributes the concise summary to all meeting participants via Microsoft Teams while also creating an action-item task in ClickUp. The goal is to save time, keep everyone aligned, and ensure follow-up tasks are tracked in your project management workspace. Pre-conditions/Requirements Prerequisites n8n instance (self-hosted or n8n.cloud) ScrapeGraphAI community node installed Microsoft Teams tenant with permissions to create Incoming Webhooks or use Bot Framework ClickUp workspace and a target List to hold meeting action items Optional: OpenAI or any LLM API account for high-quality summarization Required Credentials Microsoft Teams Webhook URL – to post summary messages ClickUp Personal Access Token – to create tasks OpenAI API Key (optional but recommended) – for AI-powered summarization ScrapeGraphAI API Key – placeholder key to satisfy the template requirement Specific Setup Requirements | Item | Description | Example | |------|-------------|---------| | Teams Channel Webhook | Create an Incoming Webhook in the desired Teams channel and copy the URL | https://outlook.office.com/webhook/... | | ClickUp List ID | The numeric ID of the list where tasks will be created | 90123456 | | Summarization Model | The LLM model or API you prefer to use | gpt-3.5-turbo | How it works This workflow transcribes or parses meeting content, leverages an LLM to generate a concise summary and action items, then distributes the results to participants in Microsoft Teams and creates a follow-up task in ClickUp. Everything runs in a single automated flow triggered manually or on a schedule. Key Steps: Manual Trigger: Start the workflow after a meeting ends. Sticky Note: Provides on-canvas documentation for quick reference. Set Node – Upload Metadata: Define meeting title, date, and participants. HTTP Request – Transcription: Send audio/video file to a transcription service (e.g., Azure Speech-to-Text). Wait: Pause until the transcription is complete. Code – Summarize: Use OpenAI to summarize the transcript and extract action items. IF Node – Validate Output: Ensure the summary exists; handle errors otherwise. Merge: Combine summary with participant list. Microsoft Teams Node: Send the summary to each participant or channel via webhook. ClickUp Node: Create a task containing the summary and action items. Set up steps Setup Time: 10-15 minutes Create Teams Webhook: In Microsoft Teams, navigate to the target channel → Manage channel → Connectors → Incoming Webhook → give it a name (e.g., “MeetingBot”) and copy the generated URL. Generate ClickUp Personal Access Token: ClickUp → Settings → Apps → Generate Token → copy and store it securely. Get ClickUp List ID: Open the list in ClickUp and copy the numeric ID from the URL bar. Optional – Obtain OpenAI API Key: Sign in to OpenAI → API Keys → Create new secret key. Add Credentials in n8n: In n8n, go to Credentials → New → add Microsoft Teams, ClickUp, and OpenAI (Generic HTTP). Import Workflow: Paste the JSON workflow into n8n or use “Templates → Import”. Configure Nodes: In the Set Node: update meeting_title, date, and participants array. In HTTP Request: set the transcription service endpoint and authentication. In Code – Summarize: paste your OpenAI key or select credential. In Microsoft Teams Node: select the Teams credential and webhook URL. In ClickUp Node: select ClickUp credential and enter the List ID. Test: Click “Execute Workflow” on the Manual Trigger node. Verify that a message appears in Teams and a task is created in ClickUp. Node Descriptions Core Workflow Nodes: Manual Trigger – Initiates the workflow manually or on a schedule. Sticky Note – Documentation block outlining purpose and credential usage. Set – Stores meeting metadata and participants list. HTTP Request – Sends meeting recording to a transcription service and fetches results. Wait – Holds the workflow until transcription is ready. Code – Summarizes transcript and extracts action items via OpenAI. IF – Validates summarization success; branches on failure. Merge – Combines summary text with participant emails/usernames. Microsoft Teams – Posts summary to Teams channel or direct messages. ClickUp – Creates a task containing summary and action items. Data Flow: Manual Trigger → Set → HTTP Request → Wait → Code → IF → Merge → Microsoft Teams Merge → ClickUp Customization Examples Change summarization prompt // Inside the Code node const prompt = ` You are an expert meeting assistant. Summarize the following transcript in under 150 words. List action items in bullet points with owners. Transcript: ${items[0].json.transcript} `; Send summary as a PDF attachment // Add Convert & Save node before Teams // Convert markdown summary to PDF and attach in Teams node Data Output Format The workflow outputs structured JSON data: { "meeting_title": "Q3 Strategy Sync", "date": "2024-05-10", "participants": ["[email protected]", "[email protected]"], "summary": "We reviewed Q3 OKRs, decided to ...", "action_items": [ { "owner": "John", "task": "Prepare budget draft", "due": "2024-05-20" }, { "owner": "Jane", "task": "Compile market research", "due": "2024-05-25" } ], "clickup_task_id": "abcd1234", "teams_message_id": "msg7890" } Troubleshooting Common Issues Teams message not sent – Verify the Incoming Webhook URL and that the Teams node uses the correct credential. ClickUp task missing – Ensure the List ID is correct and the ClickUp token has tasks:write scope. Empty summary – Check that the transcription text is populated and the OpenAI prompt is valid. Performance Tips Compress large audio/video files before sending to the transcription service. Use batching in the Teams node if participant list is >20 to avoid rate limits. Pro Tips: Schedule the workflow to auto-run 5 minutes after recurring meeting end-times. Customize the ClickUp task description template to include embedded links. Add a “Send Email” node for participants not on Teams.

Popular ways to use the ClickUp and Microsoft Teams integration

Build your own ClickUp and Microsoft Teams integration

Create custom ClickUp and Microsoft Teams workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.

ClickUp supported actions

Microsoft Teams supported actions

ClickUp and Microsoft Teams integration details

ClickUp

ClickUp

Clickup is one app that brings all the tools you use at one place. It is free, an no credit card is needed to sign up. It saves your time and energy and makes your life easier by replacing all the apps you use: Tasks, Docs, Chat, Goals, & more.

Microsoft Teams

Microsoft Teams

Microsoft Teams helps businesses organize their meetings, interviews and online events, schedule their projects, and collaborate together. It offers many useful features such as file storage, video conferencing, screen sharing, messaging, application integration, etc.

FAQ about ClickUp integrations

Need help setting up your ClickUp and Microsoft Teams integration?

Discover our latest community's recommendations and join the discussions about ClickUp and Microsoft Teams integration.

  • Nikolay Titov

    ClickUp Node error HTTP 403 for GET operations

    Nikolay Titov

    Describe the problem/error/question Hey! Recently I’ve started getting error from ClickUp Node, only for GET operations. What I’ve tried before reaching out for help: Checked that I have no rate limitations with Click…

    Open topic
  • Carsten Wraae Andersen

    ClickUp trigger (task CRUD) error in production: 'key' argument

    Carsten Wraae Andersen

    Describe the problem/error/question Running a simple workflow catching CRUD-events from ClickUp tasks using the default ClickUp trigger node works fine while testing. However, as soon as I publish the workflow, the r…

    Open topic
  • Mikey Ross

    Workflow Activation Error - Due to ClickUp webhook

    Mikey Ross

    I’m having the same issue as another post that was posted here 6 months ago here Workflow Activation Error @EmeraldHerald acknowledged the issue in this comment I’m currently stuck with using ClickUp in one workflow on…

    Open topic

Looking to integrate Slack and VirusTotal in your company?

Trusted by teams building smarter workflows

Why

Why use n8n to integrate ClickUp with Microsoft Teams

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.

Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.

Your data is displayed alongside your settings, making edge cases easy to track down.

Use 1000+ workflow templates available from our core team and our community.

Copy and paste, easily import and export workflows.

Simple enough to 
understand + sophisticated 
enough to ship