January 22, 2026

ClickUp to Notion, polished release notes published

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Release notes shouldn’t be the thing that derails your afternoon. But when updates live in ClickUp, docs live in Notion, and announcements happen in Slack and email, you end up rewriting the same “what changed?” summary three times.

Product managers feel it every sprint. Engineering leads get pulled into repeat questions. And the ops person who “owns comms” is stuck doing copy-paste. This ClickUp Notion automation turns task updates into polished release notes you can publish once and share everywhere.

You’ll see what the workflow does, what you need to run it, and how it eliminates the messy handoff between “work completed” and “release documented.”

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: ClickUp to Notion, polished release notes published

Click to explore

flowchart LR

    subgraph sg0["Draft Structured Rel Flow"]
        direction LR
        n0@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Verify ClickUp Task Event", pos: "b", h: 48 }
        n1@{ icon: "mdi:database", form: "rounded", label: "Log Invalid Events Sheet", pos: "b", h: 48 }
        n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/clickup.svg' width='40' height='40' /></div><br/>Retrieve ClickUp Task Info"]
        n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Normalize Task Fields"]
        n4@{ icon: "mdi:brain", form: "rounded", label: "Azure GPT Model for Notes", pos: "b", h: 48 }
        n5@{ icon: "mdi:robot", form: "rounded", label: "Draft Structured Release Notes", pos: "b", h: 48 }
        n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Extract Notes Title Output"]
        n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/notion.dark.svg' width='40' height='40' /></div><br/>Create Notion Release Page"]
        n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>Post Slack Release Update"]
        n9@{ icon: "mdi:database", form: "rounded", label: "Append Release Log to Sheet", pos: "b", h: 48 }
        n10@{ icon: "mdi:message-outline", form: "rounded", label: "Dispatch Release Summary Email", pos: "b", h: 48 }
        n11@{ icon: "mdi:brain", form: "rounded", label: "Azure GPT Model for Metadata", pos: "b", h: 48 }
        n12@{ icon: "mdi:robot", form: "rounded", label: "Create Release Metadata via AI", pos: "b", h: 48 }
        n13["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Parse Metadata JSON"]
        n14["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Combine Task and Metadata"]
        n15["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Assemble Final Task Payload"]
        n16["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/webhook.dark.svg' width='40' height='40' /></div><br/>Incoming Webhook Trigger"]
        n17["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Parse Webhook Payload"]
        n16 --> n17
        n17 --> n0
        n13 --> n14
        n12 --> n13
        n14 --> n15
        n8 --> n9
        n8 --> n10
        n7 --> n8
        n2 --> n3
        n0 --> n2
        n0 --> n1
        n5 --> n6
        n6 --> n7
        n3 --> n12
        n3 --> n14
        n11 -.-> n12
        n15 --> n5
        n4 -.-> n5
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n5,n12 ai
    class n4,n11 aiModel
    class n0 decision
    class n1,n7,n9 database
    class n16 api
    class n3,n6,n13,n15,n17 code
    classDef customIcon fill:none,stroke:none
    class n2,n3,n6,n7,n8,n13,n14,n15,n16,n17 customIcon

The Problem: Release Notes Get Written Too Late (or Not at All)

Most teams don’t skip release notes because they don’t care. They skip them because the process is awkward. Someone has to dig through ClickUp task details, figure out what’s worth mentioning, write it in a consistent format, then publish it in Notion. After that, you still have to announce it in Slack and send a recap email, and people will ask questions anyway because the “official” notes are missing context. Multiply that by weekly or even daily releases, and it’s a quiet time tax that never shows up on a roadmap.

It adds up fast. Here’s where it breaks down in real life.

Release documentation starts as a rough ClickUp description, so whoever writes notes spends time cleaning and reformatting before they even start writing.
Announcements get posted in different styles depending on who’s on duty, which means stakeholders stop trusting the docs as the single source of truth.
A missed detail (like risk level or testing needs) turns into a Slack thread and another meeting, honestly the worst kind of “work.”
There’s no clean audit trail of what shipped, when it shipped, and who was notified, so QA and support end up reconstructing history later.

The Solution: ClickUp Updates → Notion Release Notes, Automatically

This workflow listens for ClickUp task updates through a webhook, then turns that raw event into release documentation you can actually share. First it validates the incoming payload and checks that a real task_id exists, so bad events don’t contaminate your logs. Once validated, it fetches the full task details from ClickUp, extracts clean fields like title, description, links, priority, and assignee, and then asks GPT-4o to classify the change with useful metadata (risk level, module, change type, impact score, and whether testing is needed). With the task and metadata merged, GPT-4o generates structured release notes using a strict template. Finally, the workflow publishes the notes to Notion, posts the announcement to Slack, emails a formatted summary, and logs everything to Google Sheets for traceability.

The workflow starts with a ClickUp webhook event. AI then standardizes the messy parts: classification plus consistent writing. Notion becomes the source of truth, while Slack, Gmail, and Google Sheets handle distribution and recordkeeping.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Capturing ClickUp task updates via webhook and validating the payload.
Pulling full task details from ClickUp and cleaning them into structured fields.
Generating consistent release metadata (risk level, module, impact, testing needs) with GPT-4o.
Publishing to Notion, then pushing the same release out to Slack, Gmail, and a Google Sheets log.

Most teams get about 2 hours back per release cycle by removing manual writing, formatting, and posting.
Stakeholders get a predictable release-note structure every time, so fewer follow-up questions hit your engineers.
QA and support can see risk and testing flags without chasing context across tools.
Your Notion database stays current because pages are created automatically, not “when someone remembers.”
You also get an auditable release history in Google Sheets with links to the Notion page and Slack message.

Example: What This Looks Like

Say you ship twice a week and document each release in four places: Notion (publish), Slack (announce), Gmail (email recap), and Google Sheets (log). Manually, that’s usually about 20 minutes to read the ClickUp task, 30 minutes to write and format, then another 10 minutes to post and log, so roughly 1 hour per release. With this workflow, you spend about 5 minutes making sure the ClickUp task description is decent, then wait for processing and approvals on your side. You’ve basically traded an hour of context-switching for a quick review.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
ClickUp for task updates and task details.
Notion to publish release notes into a database.
Slack to notify the team or stakeholders.
Gmail to send the formatted release summary email.
Google Sheets for logging releases and invalid events.
Azure OpenAI GPT-4o credentials (get them from the Azure OpenAI resource in Azure Portal).

Skill level: Intermediate. You’ll connect accounts, paste tokens, and confirm your Notion database fields match what the workflow writes.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

ClickUp triggers the workflow. A webhook in n8n receives a POST event when a task update happens, then the payload is parsed to extract the task_id.

Bad events are filtered out early. If the payload is malformed or the task_id is missing, the workflow logs that invalid event to Google Sheets and stops, so you don’t create junk release notes.

Task data becomes “release-ready.” n8n fetches the full ClickUp task details, normalizes the important fields, then uses GPT-4o to generate metadata like risk level, module, impact score, and testing needs. That metadata is parsed and merged back into the task data.

Release notes are generated and distributed. GPT-4o writes structured notes (Summary, Improvements, Bug Fixes, Impact Analysis, Known Issues), n8n publishes them as a Notion page, posts the Notion link to Slack, emails the same content via Gmail, and appends a release entry to Google Sheets.

You can easily modify the Notion template and Slack formatting to match your release process based on your needs. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Webhook Trigger

This workflow starts when a ClickUp event hits the webhook endpoint and the payload is parsed.

Add the Incoming Webhook Trigger node and set HTTP Method to POST.
Set the Path to 4703a2b4-7af0-4949-a18c-32b5a2f05269 in Incoming Webhook Trigger.
In Parse Webhook Payload, keep the provided JS Code that parses $json.body into a clean task_id.
In Verify ClickUp Task Event, confirm the condition checks {{ $json.task_id }} with Operation set to notEmpty.

⚠️ Common Pitfall: Ensure the incoming webhook body contains a JSON string with task_id. If it’s already parsed JSON, adjust Parse Webhook Payload accordingly.

Step 2: Connect ClickUp and Normalize Task Data

Once the task ID is validated, the workflow retrieves ClickUp details and normalizes fields for downstream AI and outputs.

Configure Retrieve ClickUp Task Info with Operation set to get and ID set to {{ $json.task_id }}.
Credential Required: Connect your clickUpApi credentials in Retrieve ClickUp Task Info.
Keep the provided JS Code in Normalize Task Fields to standardize title, description, priority, and other fields.
For invalid events, configure Log Invalid Events Sheet to append into your error log sheet (set Document and Sheet IDs).
Credential Required: Connect your googleSheetsOAuth2Api credentials in Log Invalid Events Sheet.

Tip: The Verify ClickUp Task Event node routes invalid payloads to Log Invalid Events Sheet, so keep that sheet accessible even in production.

Step 3: Set Up AI Metadata and Release Notes Generation

The workflow uses two AI paths: one to extract structured metadata and another to draft release notes. These run alongside each other after task normalization.

Ensure Normalize Task Fields outputs to both Create Release Metadata via AI and Combine Task and Metadata in parallel.
In Create Release Metadata via AI, keep the Text prompt that returns JSON with fields like risk_level and module, and Prompt Type set to define.
Connect Azure GPT Model for Metadata as the language model for Create Release Metadata via AI and set Model to gpt-4o.
Credential Required: Connect your azureOpenAiApi credentials in Azure GPT Model for Metadata (AI credentials are added to the model node, not the agent).
In Parse Metadata JSON, keep the parsing logic that converts the AI string output into a JSON object.
In Draft Structured Release Notes, keep the structured prompt in Text and the system message in Options → System Message for consistent formatting.
Connect Azure GPT Model for Notes as the language model for Draft Structured Release Notes and set Model to gpt-4o.
Credential Required: Connect your azureOpenAiApi credentials in Azure GPT Model for Notes (AI credentials are added to the model node, not the agent).

⚠️ Common Pitfall: If the metadata AI returns malformed JSON, Parse Metadata JSON will output an error object, which can affect downstream fields like risk_level.

Step 4: Merge Data and Create Notion Release Page

The workflow merges task details with AI metadata, then creates a Notion page from the drafted release notes.

Ensure Parse Metadata JSON connects to Combine Task and Metadata, then into Assemble Final Task Payload.
Keep the JS Code in Assemble Final Task Payload to merge the two inputs into a single object.
In Extract Notes Title Output, keep the JS Code that extracts the first Markdown heading as title.
Configure Create Notion Release Page with Resource set to databasePage and Title set to {{ $json.title }}.
Set the Notion database in Create Notion Release Page and map Description|rich_text to {{ $json.release_notes }}.
Credential Required: Connect your notionApi credentials in Create Notion Release Page.

Step 5: Configure Slack, Sheets, and Email Outputs

Once the Notion page is created, a Slack announcement is sent, and logging/email actions run in parallel.

In Post Slack Release Update, keep the Text message with expressions like {{ $('Extract Notes Title Output').item.json.title }} and {{ $json.url }}.
Credential Required: Connect your slackApi credentials in Post Slack Release Update.
Post Slack Release Update outputs to both Append Release Log to Sheet and Dispatch Release Summary Email in parallel.
In Append Release Log to Sheet, verify the column mappings such as {{ $('Normalize Task Fields').first().json.title }}, {{ $('Create Notion Release Page').item.json.url }}, and {{new Date().toISOString().split('T')[0]}}.
Credential Required: Connect your googleSheetsOAuth2Api credentials in Append Release Log to Sheet.
In Dispatch Release Summary Email, set Send To to [YOUR_EMAIL] and keep the HTML Message and Subject expressions like {{ $('Extract Notes Title Output').item.json.title }}.
Credential Required: Connect your gmailOAuth2 credentials in Dispatch Release Summary Email.

⚠️ Common Pitfall: The Slack message URL in Append Release Log to Sheet uses {{ $json.message.blocks[0].elements[0].elements[29].url }}, which depends on the exact Slack response structure.

Step 6: Test & Activate Your Workflow

Run a manual test to validate each branch, then activate the workflow for production use.

Click Execute Workflow and send a test POST request to the Incoming Webhook Trigger with a body like {"task_id":"YOUR_CLICKUP_TASK_ID"}.
Confirm Retrieve ClickUp Task Info returns task data and Normalize Task Fields outputs normalized fields like title and priority.
Verify Create Release Metadata via AI and Draft Structured Release Notes generate valid outputs and that Create Notion Release Page creates a database entry.
Check that Post Slack Release Update posts a message, and that Append Release Log to Sheet and Dispatch Release Summary Email both run in parallel.
When everything looks correct, toggle the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Notion permissions trip people up. If page creation fails, check the Notion integration access and confirm the Release Notes database is shared with that integration.
If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
Azure OpenAI credentials and deployments can be finicky. If the AI steps error, confirm your GPT-4o deployment name and key, then check Azure logs for quota limits.

Frequently Asked Questions

How long does it take to set up this ClickUp Notion automation?

About 45 minutes if your accounts and databases are ready.

Do I need coding skills to automate ClickUp to Notion release notes?

No. You may edit a few text fields and paste API credentials, but you won’t be writing code.

Is n8n free to use for this ClickUp Notion automation workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Azure OpenAI usage, which is usually a small per-request cost.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this ClickUp Notion automation workflow for different release note sections?

Yes, and you should. The easiest place is the “Draft Structured Release Notes” AI step, where you can change the headings (Summary, Bug Fixes, Known Issues) and the writing style. You can also adjust what gets passed into the model by editing the “Normalize Task Fields” and “Assemble Final Task Payload” steps. Common tweaks include adding a “Breaking Changes” section, enforcing a shorter summary for Slack, and mapping different Notion properties like sprint name or team.

Why is my Notion connection failing in this workflow?

Usually the Notion integration doesn’t have access to the target database. Share the Release Notes database with your Notion integration, then confirm the database ID and required properties match what the workflow is sending. If it still fails, check for a renamed property in Notion (like “Title” vs “Name”), because that breaks page creation immediately.

How many releases can this ClickUp Notion automation handle?

A lot, as long as your n8n and AI quotas can keep up.

Is this ClickUp Notion automation better than using Zapier or Make?

Often, yes, because this is more than a simple two-step zap. You need validation, branching for invalid events, structured AI generation, merging data, and multi-channel distribution (Notion, Slack, Gmail, Sheets) in one run. n8n handles that kind of logic without forcing you into expensive task counts for every branch. Zapier or Make can still work if you keep it very simple, but most teams end up fighting edge cases. Talk to an automation expert if you want a quick recommendation.

Once this is running, release notes stop being a recurring chore. The workflow handles the repetitive parts so your team can focus on shipping, not summarizing.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "226d5decc6132615fe3b938758280f48b7d3eab1694679ab0f4ef3a5ba3c7daf"
},
"name": "Automated Release Notes Workflow",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-11743",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 1230,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "d2d1f6df-b89b-435b-aa69-c6a7e84bd982",
"name": "Verify ClickUp Task Event",
"type": "n8n-nodes-base.if",
"position": [
570,
165
],
"parameters": {
"options": [],
"conditions": {
"options": {
"version": 2,
"leftValue": "",
"caseSensitive": true,
"typeValidation": "strict"
},
"combinator": "and",
"conditions": [
{
"id": "e2adb005-2b3c-4d1e-8445-442df1fe925a",
"operator": {
"type": "string",
"operation": "notEmpty",
"singleValue": true
},
"leftValue": "={{ $json.task_id }}",
"rightValue": ""
}
]
}
},
"typeVersion": 2.2
},
{
"id": "8ae9f883-49df-464d-bf5a-fa6351c51a5f",
"name": "Log Invalid Events Sheet",
"type": "n8n-nodes-base.googleSheets",
"position": [
1130,
295
],
"parameters": {
"columns": {
"value": [],
"schema": [
{
"id": "error_id",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "error_id",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "error",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "error",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [
"error_id"
],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "append",
"sheetName": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "error log sheet"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "Interviewer Brief Pack "
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.6
},
{
"id": "c884e43d-5823-481d-a0cb-f43c8b471326",
"name": "Retrieve ClickUp Task Info",
"type": "n8n-nodes-base.clickUp",
"position": [
850,
120
],
"parameters": {
"id": "={{ $json.task_id }}",
"operation": "get"
},
"credentials": {
"clickUpApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "3f7c53f1-c1df-4762-84f5-75b534a1de5b",
"name": "Normalize Task Fields",
"type": "n8n-nodes-base.code",
"position": [
800,
315
],
"parameters": {
"jsCode": "// Extract ClickUp task details safely\nconst task = $json;\n\n// Handle cases where arrays or fields might be empty\nconst assignee = (task.assignees && task.assignees.length > 0) ? task.assignees[0] : {};\nconst customFields = task.custom_fields || [];\n\n// Try to find the first field with a value (like a GitHub or docs link)\nconst linkField = customFields.find(f => f.value) || {};\n\nreturn [\n  {\n    json: {\n      title: task.name || \"Untitled Task\",\n      description: task.description || \"No description available.\",\n      status: task.status?.status || \"No status\",\n      priority: task.priority?.priority || \"Not set\",\n      due_date: task.due_date || \"No due date\",\n      assignee: assignee.username || \"Unassigned\",\n      email: assignee.email || \"No email\",\n      link: linkField.value || \"No link provided\",\n      url: task.url || \"No URL\",\n    },\n  },\n];\n"
},
"typeVersion": 2
},
{
"id": "f4559864-e4de-4d2b-9427-7bc7a15ea5fc",
"name": "Azure GPT Model for Notes",
"type": "@n8n/n8n-nodes-langchain.lmChatAzureOpenAi",
"position": [
350,
360
],
"parameters": {
"model": "gpt-4o",
"options": []
},
"credentials": {
"azureOpenAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "77d63c36-df56-4f12-9c10-d060b5fd6e3c",
"name": "Draft Structured Release Notes",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
320,
445
],
"parameters": {
"text": "=Create Smart Release Notes from this task:\n\nTask Title: {{$json.title}}\nDescription: {{$json.description}}\nStatus: {{$json.status}}\nPriority: {{$json.priority}}\nDue Date: {{$json.due_date}}\nAssignee: {{$json.assignee}} ({{$json.email}})\nTask URL: {{$json.url}}\nReference Link: {{$json.link}}\n\nFormat the output EXACTLY like this (keep the headings):\n\n## \ud83d\ude80 Release Notes \u2013 {{$json.title}}\n\n### \ud83d\udd27 Summary\n- 1\u20132 bullets summarising what changed\n\n### \u2728 Improvements & New Features\n- Bullet list of user-facing improvements and changes\n\n### \ud83d\udc1e Bug Fixes\n- Bullet list of fixes\n- If you don't see any fixes, write: \"No bug fixes mentioned.\"\n\n### \ud83d\udcd8 Impact Analysis\n- Who is affected?\n- Any dependencies or sensitive areas touched?\n- Overall risk level (low/medium/high) based on your judgement\n\n### \u26a0 Known Issues\n- Potential or known issues to watch out for\n- If there are none, write: \"None known at this time.\"\n",
"options": {
"systemMessage": "=You are a professional release notes writer for a product team.\nYour job is to turn raw task data into clear, structured, non-marketing release notes.\n\nRules:\n- Always follow the given section headings and order.\n- Keep language simple and easy to skim.\n- Prefer bullet points over long paragraphs.\n- Do NOT write an FAQ. Only write release notes in the requested format.\n"
},
"promptType": "define"
},
"typeVersion": 2.1
},
{
"id": "bf7b20b8-23af-4511-b487-574c9a0d07a5",
"name": "Extract Notes Title Output",
"type": "n8n-nodes-base.code",
"position": [
545,
485
],
"parameters": {
"jsCode": "const ai = items[0].json;\n\n// extract first markdown heading as title\nconst firstLine = ai.output.split(\"\\n\")[0].replace(\"## \", \"\").trim();\n\nreturn [\n  {\n    json: {\n      title: firstLine,\n      release_notes: ai.output\n    }\n  }\n];\n"
},
"typeVersion": 2
},
{
"id": "483b81ea-b25f-43ef-9930-6d09725d763f",
"name": "Create Notion Release Page",
"type": "n8n-nodes-base.notion",
"position": [
890,
450
],
"parameters": {
"title": "={{ $json.title }}",
"simple": false,
"options": [],
"resource": "databasePage",
"databaseId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "Release Notes"
},
"propertiesUi": {
"propertyValues": [
{
"key": "Description|rich_text",
"text": {
"text": [
{
"text": "={{ $json.release_notes }}",
"annotationUi": []
}
]
},
"richText": true
}
]
}
},
"credentials": {
"notionApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.2
},
{
"id": "f1e2aaed-c1ce-4a4a-ad50-55d7aed709eb",
"name": "Post Slack Release Update",
"type": "n8n-nodes-base.slack",
"position": [
880,
645
],
"webhookId": "ddaa7632-9e35-4bd3-82d6-572d5cae84cc",
"parameters": {
"text": "=\ud83d\ude80 *Release Deployed*\n\n*Feature:* {{ $('Extract Notes Title Output').item.json.title }}\n\n\ud83d\udcd8 *Summary:*\n{{ $('Extract Notes Title Output').item.json.release_notes }}\n\n\ud83d\udd17 View full notes in Notion:\n{{ $json.url }}",
"user": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "newscctv22"
},
"select": "user",
"otherOptions": []
},
"credentials": {
"slackApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.3
},
{
"id": "b316cb94-8507-4f0c-b897-762535d1e24e",
"name": "Append Release Log to Sheet",
"type": "n8n-nodes-base.googleSheets",
"position": [
535,
650
],
"parameters": {
"columns": {
"value": {
"Notes": "Auto-generated release log entry",
"Title": "={{ $('Normalize Task Fields').first().json.title }}",
"Module": "={{ $('Assemble Final Task Payload').item.json.module }}",
"Task ID": "={{ $('Parse Webhook Payload').first().json.task_id }}",
"Priority": "={{ $('Normalize Task Fields').first().json.priority }}",
"Notion URL": "={{ $('Create Notion Release Page').item.json.url }}",
"Risk Level": "={{ $('Assemble Final Task Payload').item.json.risk_level }}",
"Released On": "={{new Date().toISOString().split('T')[0]}}",
"Slack Message URL": "={{ $json.message.blocks[0].elements[0].elements[29].url }}"
},
"schema": [
{
"id": "Task ID",
"type": "string",
"display": true,
"required": false,
"displayName": "Task ID",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Title",
"type": "string",
"display": true,
"required": false,
"displayName": "Title",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Priority",
"type": "string",
"display": true,
"required": false,
"displayName": "Priority",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Module",
"type": "string",
"display": true,
"required": false,
"displayName": "Module",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Risk Level",
"type": "string",
"display": true,
"required": false,
"displayName": "Risk Level",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Released On",
"type": "string",
"display": true,
"required": false,
"displayName": "Released On",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Notion URL",
"type": "string",
"display": true,
"required": false,
"displayName": "Notion URL",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Slack Message URL",
"type": "string",
"display": true,
"required": false,
"displayName": "Slack Message URL",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Notes",
"type": "string",
"display": true,
"required": false,
"displayName": "Notes",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "defineBelow",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "append",
"sheetName": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "Updated Release Notes Flow"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultName": "sample_leads_50"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.6
},
{
"id": "2722eac8-dc0e-4566-8f44-c36cf4a3f299",
"name": "Dispatch Release Summary Email",
"type": "n8n-nodes-base.gmail",
"position": [
270,
630
],
"webhookId": "0c82c299-6938-42ed-bda6-5007d79af34f",
"parameters": {
"sendTo": "=[YOUR_EMAIL]",
"message": "=<h2>\ud83d\ude80 New Release Published</h2>\n\n<p><b>Feature:</b> {{ $('Extract Notes Title Output').item.json.title }}</p>\n\n<p><b>Summary:</b></p>\n<pre>{{ $('Extract Notes Title Output').item.json.release_notes.split(\"\\n\\n\")[1] }}</pre>\n\n<p><b>Full Release Notes:</b></p>\n<pre>{{ $('Extract Notes Title Output').item.json.release_notes }}</pre>\n\n<p><b>Notion Page:</b> \n<a href=\"{{ $('Create Notion Release Page').item.json.url }}\">\nClick here to view</a>\n</p>\n\n<p><b>Released On:</b> {{ new Date().toISOString().split(\"T\")[0] }}</p>\n",
"options": [],
"subject": "=New Release Published \u2013 {{ $('Extract Notes Title Output').item.json.title }}"
},
"credentials": {
"gmailOAuth2": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
},
{
"id": "90d26ead-66a7-462c-8652-c86ea79edf6f",
"name": "Azure GPT Model for Metadata",
"type": "@n8n/n8n-nodes-langchain.lmChatAzureOpenAi",
"position": [
620,
190
],
"parameters": {
"model": "gpt-4o",
"options": []
},
"credentials": {
"azureOpenAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1
},
{
"id": "7d029983-92a9-440c-a2e5-e1f40469aa05",
"name": "Create Release Metadata via AI",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
575,
280
],
"parameters": {
"text": "=Analyze the task details below and extract structured metadata useful for release management.\n\nTask Data:\n{{ JSON.stringify($json, null, 2) }}\n\nReturn ONLY a valid JSON object with the following fields:\n\n{\n  \"risk_level\": \"low | medium | high\",\n  \"change_type\": \"feature | fix | enhancement | refactor\",\n  \"module\": \"backend | frontend | ui | automation | analytics | other\",\n  \"impact_score\": 1-10,\n  \"requires_testing\": true or false\n}\n\nRules:\n- Be accurate and concise.\n- Infer values from description, priority, and status.\n- If uncertain, make the best logical guess.\n",
"options": {
"systemMessage": "=You are a senior engineering analyst. \nYour job is to classify changes based on risk, complexity, and module.\nAlways return clean JSON. No explanations.\n"
},
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 2.1
},
{
"id": "d90c385e-8db7-4e1e-9740-467bf26066a6",
"name": "Parse Metadata JSON",
"type": "n8n-nodes-base.code",
"position": [
230,
320
],
"parameters": {
"jsCode": "// The AI node returns metadata as a STRING inside output.\n// Example: \"{ \\\"risk_level\\\": \\\"medium\\\", ... }\"\n\n// Grab the raw string from the previous node\nconst rawString = $json.output;\n\n// Safely parse it into a real JSON object\nlet parsed = {};\ntry {\n  parsed = JSON.parse(rawString);\n} catch (error) {\n  // If parsing fails, return an error structure\n  parsed = {\n    error: \"Failed to parse AI metadata JSON\",\n    raw_output: rawString\n  };\n}\n\n// Return as proper JSON to the next node\nreturn [\n  {\n    json: parsed\n  }\n];\n"
},
"typeVersion": 2
},
{
"id": "e2068588-bd5c-4dcf-b027-3a4c38ab6fef",
"name": "Combine Task and Metadata",
"type": "n8n-nodes-base.merge",
"position": [
10,
285
],
"parameters": [],
"typeVersion": 3.2
},
{
"id": "ebccabcd-da53-4381-a375-29ace5e46589",
"name": "Assemble Final Task Payload",
"type": "n8n-nodes-base.code",
"position": [
45,
480
],
"parameters": {
"jsCode": "// Input 0 = Task Details from \"Parse Task Details\"\n// Input 1 = Metadata from \"Code (Parsed Metadata)\"\nconst task = items[0].json;\nconst meta = items[1].json;\n\n// Merge both objects into a single final object\nconst combined = {\n  ...task,   // expands all task fields\n  ...meta    // expands all metadata fields\n};\n\n// Return the combined object as one item\nreturn [{ json: combined }];\n"
},
"typeVersion": 2
},
{
"id": "a9f2b8f1-406b-49c7-9992-9cc9f5c061dd",
"name": "Incoming Webhook Trigger",
"type": "n8n-nodes-base.webhook",
"position": [
0,
165
],
"webhookId": "4703a2b4-7af0-4949-a18c-32b5a2f05269",
"parameters": {
"path": "4703a2b4-7af0-4949-a18c-32b5a2f05269",
"options": [],
"httpMethod": "POST"
},
"typeVersion": 2.1
},
{
"id": "bb569018-5aab-426b-9b26-86d85ffdbe55",
"name": "Parse Webhook Payload",
"type": "n8n-nodes-base.code",
"position": [
220,
125
],
"parameters": {
"jsCode": "// The webhook sends the body as a string like:\n// \"{\\\"task_id\\\":\\\"86b78ggjw\\\"}\"\n\n// Step 1: Read the raw body\nconst rawBody = $json.body;\n\n// Step 2: Parse it into actual JSON\nlet parsed;\ntry {\n  parsed = JSON.parse(rawBody);\n} catch (err) {\n  parsed = { error: \"Invalid JSON\", raw: rawBody };\n}\n\n// Step 3: Return only the task_id in clean form\nreturn [\n  {\n    json: {\n      task_id: parsed.task_id || null\n    }\n  }\n];\n"
},
"typeVersion": 2
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"Incoming Webhook Trigger": {
"main": [
[
{
"node": "Parse Webhook Payload",
"type": "main",
"index": 0
}
]
]
},
"Parse Webhook Payload": {
"main": [
[
{
"node": "Verify ClickUp Task Event",
"type": "main",
"index": 0
}
]
]
},
"Parse Metadata JSON": {
"main": [
[
{
"node": "Combine Task and Metadata",
"type": "main",
"index": 1
}
]
]
},
"Create Release Metadata via AI": {
"main": [
[
{
"node": "Parse Metadata JSON",
"type": "main",
"index": 0
}
]
]
},
"Combine Task and Metadata": {
"main": [
[
{
"node": "Assemble Final Task Payload",
"type": "main",
"index": 0
}
]
]
},
"Post Slack Release Update": {
"main": [
[
{
"node": "Append Release Log to Sheet",
"type": "main",
"index": 0
},
{
"node": "Dispatch Release Summary Email",
"type": "main",
"index": 0
}
]
]
},
"Create Notion Release Page": {
"main": [
[
{
"node": "Post Slack Release Update",
"type": "main",
"index": 0
}
]
]
},
"Retrieve ClickUp Task Info": {
"main": [
[
{
"node": "Normalize Task Fields",
"type": "main",
"index": 0
}
]
]
},
"Verify ClickUp Task Event": {
"main": [
[
{
"node": "Retrieve ClickUp Task Info",
"type": "main",
"index": 0
}
],
[
{
"node": "Log Invalid Events Sheet",
"type": "main",
"index": 0
}
]
]
},
"Draft Structured Release Notes": {
"main": [
[
{
"node": "Extract Notes Title Output",
"type": "main",
"index": 0
}
]
]
},
"Extract Notes Title Output": {
"main": [
[
{
"node": "Create Notion Release Page",
"type": "main",
"index": 0
}
]
]
},
"Normalize Task Fields": {
"main": [
[
{
"node": "Create Release Metadata via AI",
"type": "main",
"index": 0
},
{
"node": "Combine Task and Metadata",
"type": "main",
"index": 0
}
]
]
},
"Azure GPT Model for Metadata": {
"ai_languageModel": [
[
{
"node": "Create Release Metadata via AI",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Assemble Final Task Payload": {
"main": [
[
{
"node": "Draft Structured Release Notes",
"type": "main",
"index": 0
}
]
]
},
"Azure GPT Model for Notes": {
"ai_languageModel": [
[
{
"node": "Draft Structured Release Notes",
"type": "ai_languageModel",
"index": 0
}
]
]
}
}
}