AI Meeting Summary → ClickUp Comments

Problem

Zoom AI meeting summaries arrived by email, but the useful context still needed to land on the right existing ClickUp tasks. The source inventory confirms this workflow watched Gmail for Zoom AI summary emails, parsed the summary content, matched the meeting to an existing ClickUp task, and posted a meeting summary comment.

The confirmed workflow does not create action-item tasks. It routes summaries into comments on existing tasks.

Objectives

• Watch Gmail for Zoom AI summary emails
• Retrieve the full email message content
• Parse the Zoom AI summary text
• Match the meeting to an existing ClickUp task through a configured lookup
• Post the meeting summary as a ClickUp comment
• Avoid exposing private meeting names publicly
• Avoid claiming task creation or action-item generation that the source does not confirm

Solution

I built an n8n workflow that polls Gmail for Zoom AI summary emails, loads the full email body, parses the summary section, uses a meeting-to-task lookup to find the matching existing ClickUp task, and posts the summary as a comment.

Meeting names and lookup details are kept generalized because the inventory explicitly says not to expose meeting names publicly.

Architecture

The confirmed architecture is a linear n8n flow: Gmail trigger, full message retrieval, Zoom AI summary parsing, existing ClickUp task matching, and ClickUp comment posting.

Workflow

1. n8n polls Gmail for Zoom AI summary emails.
2. When a matching email is found, the workflow retrieves the full message.
3. The email body is parsed to extract the Zoom AI summary content.
4. The workflow checks a configured meeting-to-task lookup.
5. When a matching existing ClickUp task is found, the summary is posted as a comment.
6. The workflow does not create action-item tasks.

Tools Used

• n8n - workflow orchestration, Gmail polling, parsing, and ClickUp action execution
• Gmail / Google Workspace - source of Zoom AI summary emails
• Zoom AI Summary - source content for meeting summaries
• ClickUp - destination for comments on existing tasks

Technical Decisions

Commenting instead of task creation: The source inventory confirms that this workflow posts summaries as comments on existing ClickUp tasks. It does not create action-item tasks.

Lookup table as routing logic: The workflow matches meetings to existing ClickUp tasks through a configured lookup. Whether the lookup should be represented as a decision node or as configuration is not confirmed.

Public-safe meeting names: Meeting names should not be exposed publicly, so examples and diagrams should use generalized labels.

Challenges Solved

• Email-to-task context: Zoom AI summaries were moved from Gmail into the relevant existing ClickUp task context.
• Meeting matching: A configured lookup connected summary emails to the right task without publishing private meeting names.
• Scope control: The workflow avoided creating tasks and only posted comments, reducing the risk of duplicate operational work.
• Public-safe documentation: Meeting names and lookup table contents must stay generalized.

Results

The confirmed output is a ClickUp comment containing the meeting summary on an existing mapped task.

Metrics such as time saved, number of meetings processed, lookup accuracy, or reduction in follow-up messages are not confirmed in the provided inventory.

Future Improvements

• Generalized: decide whether the lookup table should appear as a workflow decision node or remain described as configuration.
• Generalized: confirm whether Zoom AI summary assets beyond the text summary should be represented.
• Generalized: document public-safe examples that do not reveal meeting names.
• Generalized: add outcome metrics only after they are verified.

Lessons Learned

Generalized: not every AI-assisted workflow needs to generate new tasks. In this confirmed workflow, the value is moving the AI-generated meeting context to the existing operational record.

The portfolio version should be precise about that scope: this is summary routing and comment posting, not task extraction.

If I Rebuilt This Today

Generalized: I would first confirm how much of the meeting-to-task lookup can be described publicly, then document the boundary between private meeting configuration and public workflow behavior.

I would also avoid adding action-item extraction claims unless a separate confirmed workflow supports them.

Engineering Notes

• Confirmed trigger: Gmail polling for Zoom AI summary emails every minute.
• Confirmed services: n8n, Gmail, Zoom, ClickUp.
• Confirmed output: ClickUp comments on existing tasks.
• Confirmed limitation: this workflow does not create action-item tasks.
• Unconfirmed: whether the lookup table should be shown as a decision node or configuration, and whether Zoom AI summary assets beyond text should be represented.