🛠️ Trello tool MCP server 💪 all 41 operations

Name: 🛠️ Trello tool MCP server 💪 all 41 operations
Availability: InStock
Author: David Ashby

🛠️ Trello tool MCP server 💪 all 41 operations preview

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

Overview

Need help? Want access to this workflow + many more paid workflows + live Q&A sessions with a top verified n8n creator?

Join the community

Complete MCP server exposing all Trello Tool operations to AI agents. Zero configuration needed - all 41 operations pre-built.

⚡ Quick Setup

Import this workflow into your n8n instance
Activate the workflow to start your MCP server
Copy the webhook URL from the MCP trigger node
Connect AI agents using the MCP URL

🔧 How it Works

• MCP Trigger: Serves as your server endpoint for AI agent requests • Tool Nodes: Pre-configured for every Trello Tool operation • AI Expressions: Automatically populate parameters via $fromAI() placeholders • Native Integration: Uses official n8n Trello Tool tool with full error handling

📋 Available Operations (41 total)

Every possible Trello Tool operation is included:

🔧 Attachment (4 operations)

• Create an attachment • Delete an attachment • Get an attachment • Get many attachments

🔧 Board (4 operations)

• Create a board • Delete a board • Get a board • Update a board

🔧 Boardmember (4 operations)

• Add a board member • Get many board members • Invite a board member • Remove a board member

🔧 Card (4 operations)

• Create a card • Delete a card • Get a card • Update a card

🔧 Cardcomment (3 operations)

• Create a card comment • Delete a card comment • Update a card comment

🔧 Checklist (9 operations)

• Create a checklist • Create checklist item • Delete a checklist • Delete a checklist item • Get a checklist • Get checklist items • Get completed checklist items • Get many checklists • Update a checklist item

🔧 Label (7 operations)

• Add a label to a card • Create a label • Delete a label • Get a label • Get many labels • Remove a label from a card • Update a label

📝 List (6 operations)

• Archive/unarchive a list • Create a list • Get a list • Get all cards in a list • Get many lists • Update a list

🤖 AI Integration

Parameter Handling: AI agents automatically provide values for: • Resource IDs and identifiers • Search queries and filters • Content and data payloads • Configuration options

Response Format: Native Trello Tool API responses with full data structure

Error Handling: Built-in n8n error management and retry logic

💡 Usage Examples

Connect this MCP server to any AI agent or workflow:

• Claude Desktop: Add MCP server URL to configuration • Custom AI Apps: Use MCP URL as tool endpoint • Other n8n Workflows: Call MCP tools from any workflow • API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

• Complete Coverage: Every Trello Tool operation available • Zero Setup: No parameter mapping or configuration needed • AI-Ready: Built-in $fromAI() expressions for all parameters • Production Ready: Native n8n error handling and logging • Extensible: Easily modify or add custom logic

> 🆓 Free for community use! Ready to deploy in under 2 minutes.

David Ashby

204 workflows

Nodes

n8n-nodes-base.stickynote @n8n/n8n-nodes-langchain.mcptrigger n8n-nodes-base.trellotool

Complexity

advanced

Published 21 Jun 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/5079/5079.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

AI-Powered Paperclip📎🤖 Task Assigner & Completion Tracker

This workflow automates the **creation, assignment, tracking, and monitoring of tasks** (issues) inside a **Paperclip** system using AI and external integrations. View this [Youtube Video Tutorial](https://www.youtube.com/watch?v=vdnyiF92qcY) to setup your Paperclip instance for FREE and get API Key (subtitles in English). --- ### ✅ Key Advantages #### 1. ✅ Full Automation of Task Lifecycle The workflow handles everything: * Task intake → assignment → tracking → completion notification No manual intervention is required. #### 2. ✅ AI-Powered Task Assignment Using an LLM: * Tasks are assigned intelligently based on context * Reduces human decision-making errors * Scales easily with more agents #### 3. ✅ Centralized Tracking with Google Sheets * Acts as a lightweight database * Easy to audit, monitor, and share * Provides historical tracking of tasks #### 4. ✅ Real-Time Monitoring & Alerts * Scheduled checks ensure tasks are constantly monitored * Instant email notifications when tasks are completed * Improves responsiveness and visibility #### 5. ✅ Modular & Scalable Architecture * Each block (Webhook, AI, API, Sheets, Email) is independent * Easy to extend (e.g., Slack alerts, dashboards, analytics) * Can integrate with other systems without redesigning everything #### 6. ✅ Efficient Resource Utilization * Batch processing (`Split in Batches`) avoids overload * Scheduled execution reduces unnecessary API calls #### 7. ✅ Seamless API Integration * Connects Paperclip, OpenAI, Google Sheets, and Gmail * Demonstrates strong interoperability across services --- ### How it works This workflow automates the assignment and tracking of issues/tasks to AI agents (called "Paperclip agents") and monitors their completion. **Two main flows:** 1. **Issue creation WF** (triggered via Webhook or Manual): - Receives a task with `title` and `issue` via webhook - Fetches the company ID from the Paperclip API - Retrieves all available Paperclip agents for that company - Normalizes agent data (id, name, title) - Uses GPT-5-mini to intelligently assign the task to the most appropriate agent - Creates a new issue in Paperclip with the assigned agent - Logs the issue to a Google Sheet with metadata (date, ID, title, issue, assigned agent) 2. **Completion monitoring WF** (runs every 10 minutes via Schedule Trigger): - Fetches all open issues (where COMPLETED column is empty) from Google Sheets - Loops through each open issue - Checks the current status of each issue in Paperclip API - If status is "completed", sends a Gmail alert and updates the COMPLETED column in Sheets with the completion timestamp --- ### Set up steps 1. **API Credentials:** - Configure `httpBearerAuth` credentialwith your Paperclip API key - Set up `openAiApi` credential - Configure `gmailOAuth2` credential for sending completion alerts - Set up `googleSheetsOAuth2Api` credential for Sheets access 2. **Google Sheets Setup:** - Clone [this Sheet](https://docs.google.com/spreadsheets/d/1MDJ-SAMiRWdfSpXMXOzH2qiipym-8qhX31ymPMdcz8k/edit?usp=sharing) - Sheet must contain columns: DATE, TITLE, ISSUE, ASSIGN, ID, COMPLETED - Share the sheet with the service account or OAuth account used in credentials 3. **Paperclip API Configuration:** - Replace all `https://paperclip.xxx.xxx` URLs with your actual Paperclip instance URL - Verify the `/api/agents/me`, `/api/companies/{id}/agents`, and `/api/issues/{id}` endpoints are accessible 4. **Workflow Settings:** - Webhook path is auto-generated – copy this for external calls - Update the Gmail recipient from `[email protected] ` to your target email address - Adjust schedule trigger interval (currently 10 minutes) as needed 5. **Testing:** - Activate the workflow - Use the Manual Trigger or send a POST request to the webhook URL with payload containing `title` and `issue` fields - Monitor execution logs to verify agent assignment and issue creation --- 👉 [Subscribe to my new **YouTube channel**](https://youtube.com/@n3witalia). Here I’ll share videos and Shorts with practical tutorials and **FREE templates for n8n**. [![image](https://n3wstorage.b-cdn.net/n3witalia/youtube-n8n-cover.jpg)](https://youtube.com/@n3witalia) --- ### **Need help customizing?** [Contact me](mailto:[email protected]) for consulting and support or add me on [Linkedin](https://www.linkedin.com/in/davideboizza/).

View

Track Zoom attendance and create AI summaries with Google Sheets, ClickUp and Telegram

## Description When a Zoom meeting ends, this workflow fires automatically — no manual action needed. It classifies every participant as On Time or Late, logs all attendance data to Google Sheets, and sends you one AI-written summary via Telegram. For every late joiner, a ClickUp follow-up task is created automatically so no one slips through the cracks. Built for team leads, trainers, and operations managers who run recurring Zoom meetings. --- ## What This Workflow Does - **Automatic attendance capture** — Receives the Zoom meeting.ended event via webhook and processes all participant data instantly, with zero manual input - **Late participant detection** — Classifies each attendee as Attended or Late based on a configurable join delay threshold (default: 5 minutes) - **14-column Google Sheets log** — Saves every participant as one row including join time, leave time, time in meeting, join delay, and status - **AI-written Telegram summary** — GPT-4o-mini writes a professional attendance summary and sends it once per meeting directly to the host's Telegram - **Automated ClickUp follow-up tasks** — Creates one ClickUp task per late joiner with full meeting context, participant details, and a next-day due date - **Clean exit for on-time attendees** — Participants who joined on time bypass the task creation step with no noise or extra actions --- ## Setup Requirements ### Tools and accounts needed - n8n instance (self-hosted or cloud) - Zoom Marketplace account with a Webhook Only App configured - Google account with Google Sheets access - OpenAI account with API access (GPT-4o-mini) - ClickUp account with API access - Telegram Bot (via BotFather) **Estimated Setup Time: 20–30 minutes** --- ## Step-by-Step Setup 1. **Import the workflow** — Open n8n, go to Workflows → Import from JSON, paste the workflow JSON, and verify all nodes are connected. 2. **Configure Zoom Webhook** — In the **1. Webhook — Zoom Meeting Ended** node, copy the webhook URL. Go to your Zoom Marketplace app, open your Webhook Only App, and paste the URL under the `meeting.ended` event subscription. 3. **Set your config values** — Open **2. Set — Config Values** and replace all six placeholders: - `YOUR_TELEGRAM_CHAT_ID` — your Telegram chat ID (get it from @userinfobot) - `YOUR_GOOGLE_SHEET_ID` — the ID from your Google Sheet URL (the long string between `/d/` and `/edit`) - `Attendance Log` — rename if your sheet tab has a different name - `YOUR HOST NAME` — the name that appears in the Telegram summary - `5` — change to your preferred late threshold in minutes - `YOUR_CLICKUP_LIST_ID` — copy from your ClickUp list URL 4. **Connect Google Sheets** — Open **4. Google Sheets — Log Participant Row** and connect your Google Sheets OAuth2 credential. Authenticate via Google when prompted. 5. **Connect OpenAI** — Open **7. OpenAI — GPT-4o-mini Model** and connect your OpenAI API credential. Enter your API key from platform.openai.com. 6. **Connect ClickUp** — Open **9. ClickUp — Create Late Participant Task** and connect your ClickUp API credential. Enter your personal API token from ClickUp Settings → Apps. 7. **Connect Telegram** — Open **12. Telegram — Send Meeting Summary** and connect your Telegram Bot API credential. Enter the token from BotFather. 8. **Activate the workflow** — Toggle the workflow to Active before running your next Zoom meeting. --- ## How It Works (Step by Step) **Step 1 — Webhook: Zoom Meeting Ended** When any Zoom meeting ends, Zoom sends a POST request to this webhook. This is the trigger that starts the entire workflow. No polling or manual action is needed — it fires the moment the meeting closes. **Step 2 — Set: Config Values** This step stores all six configuration values in one place — Telegram chat ID, Google Sheet ID, sheet tab name, host name, late threshold in minutes, and ClickUp list ID. You only set these once, and all downstream steps read from here automatically. **Step 3 — Code: Extract and Classify Participants** This step reads the full participant list from the Zoom payload. For each person, it calculates how many minutes after the meeting start they joined. If the delay exceeds the threshold, they are marked Late. Everyone else is marked Attended. This step outputs one item per participant — every step after this runs once per person. **Step 4 — Google Sheets: Log Participant Row** Every participant — regardless of status — is written as one row in your Google Sheet. The row includes 14 columns: meeting ID, topic, host email, date, start time, duration, participant name, email, join time, leave time, time in meeting, join delay in minutes, status, and the timestamp when the row was logged. **Step 5 — IF: First Row Check** This check gates the Telegram path. Only the first participant item passes through to the summary path (YES). All other participants go to the late-check path (NO). This prevents the host from receiving one Telegram message per attendee. **Step 6 — AI Agent: Write Telegram Summary** Using GPT-4o-mini, this step generates a concise, plain-text Telegram message for the host. The message covers the meeting topic, date, duration, participant counts, one observation about attendance quality, and one action suggestion. It is capped at 80 words and uses no markdown. **Step 7 — OpenAI GPT-4o-mini Model** This is the language model powering the AI Agent in Step 6. It runs with a max token limit of 200 and a temperature of 0.4 for consistent, professional output. **Step 8 — Set: Prepare Telegram Fields** Reads the AI-generated message and the Telegram chat ID, then packages them into a clean output ready to send. **Step 9 — Telegram: Send Meeting Summary** Sends the final AI-written message to the host's Telegram chat. This fires exactly once per meeting — not once per participant. **Step 10 — IF: Is Participant Late?** For every non-first participant, this check reads their status. If status equals Late (YES), they move to the ClickUp task step. If they joined on time (NO), they exit cleanly through the No Action step. **Step 11 — ClickUp: Create Late Participant Task** Creates one ClickUp task per late participant. The task name includes the participant's name and meeting topic. The task body includes full meeting context, participant details, join time, delay in minutes, time in meeting, and three pre-written action items. Due date is automatically set to the next day. **Step 12 — Set: No Action Needed** On-time participants exit here with a simple confirmation message. No task is created and no further action is taken. --- ## Key Features ✅ **Zero-click attendance logging** — The workflow fires automatically when Zoom ends; you never need to start it manually ✅ **Configurable late threshold** — Change one value in the config step to adjust what counts as late for your team ✅ **One Telegram message per meeting** — The first-row gate ensures the host gets one clean summary, not one message per attendee ✅ **14-column Google Sheets record** — Every row is complete with time-in-meeting, join delay, and logged-at timestamp for easy reporting ✅ **Pre-written ClickUp task body** — Late participant tasks include context and three ready-to-act follow-up items out of the box ✅ **Next-day due date on tasks** — ClickUp tasks are automatically due 24 hours after the meeting ends ✅ **GPT-4o-mini for cost efficiency** — Telegram summaries use the lightweight model for fast, affordable generation --- ## Customisation Options **Change the late threshold per meeting type** — In **2. Set — Config Values**, update `lateThresholdMinutes` to a higher value (e.g., 10) for longer or less structured meetings. **Add email notification for late participants** — After **9. ClickUp — Create Late Participant Task**, connect a Gmail or SMTP node to automatically email the late participant a summary of what they missed. **Log to multiple sheets by meeting topic** — In **4. Google Sheets — Log Participant Row**, use an expression to dynamically set the sheet tab name based on the meeting topic — one tab per recurring meeting type. **Add a Slack notification alongside Telegram** — Duplicate **12. Telegram — Send Meeting Summary** and replace it with a Slack node to send the same summary to a team channel in addition to the host's personal Telegram. **Increase task priority for participants who joined very late** — In **9. ClickUp — Create Late Participant Task**, add an IF check before the task node to set `priority: 1` (urgent) if `joinDelayMin` exceeds 15 minutes. **Filter out internal test accounts** — Before **3. Code — Extract and Classify Participants**, add a Code node that removes any participants matching test email domains so they don't pollute your sheet or trigger tasks. --- ## Troubleshooting **Workflow not triggering when the meeting ends:** - Confirm the webhook URL from **1. Webhook — Zoom Meeting Ended** is pasted correctly in your Zoom Marketplace app - Verify the event subscription is set to `meeting.ended` specifically — not `meeting.ended` with a typo or a different event type - Make sure the workflow is activated in n8n before the meeting starts **Google Sheets rows not appearing:** - Check that the Sheet ID in **2. Set — Config Values** is the correct ID from the sheet URL - Confirm the sheet tab name matches exactly what is written in `sheetName` — it is case-sensitive - Re-authenticate the Google Sheets OAuth2 credential if you recently changed Google account permissions **Telegram message not sending:** - Verify the Telegram chat ID is correct — use @userinfobot in Telegram to retrieve it - Confirm the Telegram Bot token in **12. Telegram — Send Meeting Summary** is valid and has not been revoked via BotFather - Make sure the bot has been added to the chat and has permission to send messages **ClickUp tasks not being created:** - Check that the ClickUp list ID in **2. Set — Config Values** is the correct list — not a space ID or folder ID - Verify the ClickUp API credential is connected and the token has not expired - If no participants are late in your test, the task node will not fire — use a threshold of `0` for initial testing **AI summary is blank or returns an error:** - Confirm the OpenAI API key in **7. OpenAI — GPT-4o-mini Model** is valid and has available credits - Check that the credential is connected properly in n8n — reconnect and re-enter the key if needed --- ## Support Need help setting this up or want a custom version built for your team or agency? 📧 Email:[[email protected]]([email protected]) 🌐 Website:[https://isawow.com](https://isawow.com)

View

Log Jira worklogs nightly from Google Sheets with Gmail and GPT-4o-mini

# Jira Daily Worklog Automation — Auto-log Time from Google Sheets to Jira Every Night Automatically logs time to Jira every night from a Google Sheet. No manual worklog entries needed — just fill in your sheet and the workflow handles the rest at 10 PM. Built for developers and teams who track their daily tasks in a spreadsheet and want their Jira time entries done automatically, with a clean email report. --- ## How It Works - Runs every night at **10 PM** via a Schedule Trigger - Reads all rows from your Google Sheet and filters rows where `status = Pending` and `date <= today` - Loops through each pending row one at a time using `splitInBatches` - Builds the Jira worklog payload — normalises time format, constructs the ISO timestamp from `date` + `started_at` - Calls the **Jira REST API** (`POST /rest/api/3/issue/ticket_id/worklog`) with Basic Auth - Updates the sheet row status to `Completed` or keeps it `Pending` with an error message and incremented `retry_count` - After all rows are processed, reads results from static data and builds a summary - **GPT-4o-mini** writes a friendly 2–3 sentence team update - Sends a formatted **HTML email report** via Gmail with success count, fail count, total time logged, and the AI summary --- ## How to Use **Step 1 — Set up your Google Sheet** Create a sheet with these exact column headers in row 1: | ticket_id | log_text | date | started_at | log_time | status | error_message | retry_count | |-----------|----------|------|------------|----------|--------|---------------|-------------| - `ticket_id` — your Jira issue key e.g. `PROJ-123` - `log_text` — worklog comment e.g. `Reviewed PR and fixed unit tests` - `date` — date to log against e.g. `2026-04-02` - `started_at` — time the work started e.g. `09:30` - `log_time` — time spent e.g. `1h`, `30m`, `1h30m` - `status` — set to `pending` for rows to be processed - `error_message` — auto-filled on failure - `retry_count` — auto-incremented on failure **Step 2 — Add credentials in n8n** - **Google Sheets OAuth2** — connect your Google account - **Gmail OAuth2** — connect your Gmail account for email reports - **HTTP Basic Auth** — your Jira email + API token (get token at [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)) - **OpenAI API** — for the AI summary (GPT-4o-mini) **Step 3 — Update the workflow** - Open the `Read Log Sheet` node and select your spreadsheet and sheet tab - Open the `Update Sheet` node and do the same - Open `Jira: Add Worklog` and update the Atlassian domain in the URL: `https://YOUR-DOMAIN.atlassian.net/...` - Open both Gmail nodes and update the `sendTo` email address - Select your HTTP Basic Auth credential in `Jira: Add Worklog` **Step 4 — Activate** Toggle the workflow to **Active**. It will run automatically every night at 10 PM. To test immediately, open the workflow and click **Test Workflow**. --- ## Requirements - n8n (self-hosted or cloud) - Google account with Google Sheets + Gmail - Jira Cloud account with an API token - OpenAI API key (free tier works for low volume) --- ## Customising This Workflow - **Change the schedule** — edit the cron expression in the trigger node. Examples are in the sticky note - **Change the Jira domain** — update the URL in `Jira: Add Worklog` to your Atlassian subdomain - **Use Telegram instead of Gmail** — replace both Gmail nodes with a Telegram node using `chatId` and `text` - **Skip the AI summary** — delete the `AI Summary` node and wire `Build Summary` directly to the Gmail node; update the email template to remove `$json.message.content` - **Add multiple projects** — the sheet supports any mix of ticket IDs from different Jira projects in the same run - **Catch missed past days** — the filter already picks up rows where `date < today`, so any past pending rows are automatically retried on the next run

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

🛠️ Trello tool MCP server 💪 all 41 operations

Workflow preview

Important notice

Overview

⚡ Quick Setup

🔧 How it Works

📋 Available Operations (41 total)

🔧 Attachment (4 operations)

🔧 Board (4 operations)

🔧 Boardmember (4 operations)

🔧 Card (4 operations)

🔧 Cardcomment (3 operations)

🔧 Checklist (9 operations)

🔧 Label (7 operations)

📝 List (6 operations)

🤖 AI Integration

💡 Usage Examples

✨ Benefits