OpenRuna
Sign in
← Workflows

Automate Figma Versioning and Jira Updates with n8n Webhook Integration

4 nodes · jira, figma

Engine
n8n
Nodes
4
Trigger
scheduled/triggered
Source file
1069_Figma_Stickynote_Update_Triggered.json

Workflow flow

IntegrationsJiraFigma
100%
TRIGGER

Figma Trigger

Figma

Find Jira Issue

Jira

Add Comment in Issue

Jira

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

Browse by integration

jirafigma
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

Automate Figma Versioning and Jira Updates with n8n Webhook Integration (4-node n8n automation, jira, figma) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"Automate Figma Versioning and Jira Updates with n8n Webhook Integration" automates a jira-to-figma flow in n8n across 4 nodes. 4 nodes · jira, figma It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Benchmark it against your current jira integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 4-node flow from scratch.
  • Share it with your team as a documented reference for scheduled/triggered automations in the jira stack.
  • Study how data moves from jira to figma before building your own variant.

Example output

Imported into n8n, "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" exposes 4 configured nodes. Trigger type: scheduled/triggered. Integrations: jira, figma. Set your credentials on the jira 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 "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" into Claude and ask it to explain each of the 4 nodes. Claude is good at suggesting credential mappings for jira, figma, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" to your accounts — which jira, figma 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 4 nodes.

Frequently asked questions

How do I import "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" 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 "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" use?
It uses: jira, figma. The flow diagram above shows how each service connects across the 4 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 jira and figma credentials in n8n after import.
What trigger type does "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" 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 "Automate Figma Versioning and Jira Updates with n8n Webhook Integration" 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 jira, figma.

Related resources