OpenRuna
Sign in
← Workflows

Sync Jira issues with subsequent comments to Notion database

10 nodes · notion, switch, jira

Engine
n8n
Nodes
10
Trigger
scheduled/triggered
Source file
1769_Jira_Stickynote_Sync_Triggered.json

Workflow flow

IntegrationsNotionSwitchJiraIFCode
100%
jira:issue_updatedjira:issue_deleted
TRIGGER

On issues created/updated/deleted

Jira

Lookup table

Code

IF

IF

Create database page

Notion

Create custom Notion filters

Code

Find database page

Notion

Switch

Switch

Delete issue

Notion

Update issue

Notion

9 steps · flows top to bottom, branches left to right

Browse by integration

notionswitchjira
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Sync Jira issues with subsequent comments to Notion database. 10 nodes across notion, switch, jira, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"Sync Jira issues with subsequent comments to Notion database" is an n8n automation built from 10 nodes spanning notion, switch, jira. 10 nodes · notion, switch, jira Execution begins at the scheduled/triggered trigger and flows through the 10 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "Sync Jira issues with subsequent comments to Notion database" into n8n, reconnect credentials for notion, switch, jira, and run the same automation in your own workspace.
  • Share it with your team as a documented reference for scheduled/triggered automations in the notion stack.
  • Study how data moves from notion to switch before building your own variant.
  • Benchmark it against your current notion integration to spot missing steps or redundant nodes.

Example output

Imported into n8n, "Sync Jira issues with subsequent comments to Notion database" exposes 10 configured nodes. Trigger type: scheduled/triggered. Integrations: notion, switch, jira. Set your credentials on the notion node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Sync Jira issues with subsequent comments to Notion database" into Claude and ask it to explain each of the 10 nodes. Claude is good at suggesting credential mappings for notion, switch, jira, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Sync Jira issues with subsequent comments to Notion database" to your accounts — which notion, switch, jira credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 10 nodes.

Frequently asked questions

How do I import "Sync Jira issues with subsequent comments to Notion database" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Sync Jira issues with subsequent comments to Notion database" use?
It uses: notion, switch, jira. The flow diagram above shows how each service connects across the 10 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own notion and switch credentials in n8n after import.
What trigger type does "Sync Jira issues with subsequent comments to Notion database" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Sync Jira issues with subsequent comments to Notion database" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for notion, switch, jira.

Related resources