The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"id": "5kYHogzDGeo21MxE",
"meta": {
"templateCredsSetupCompleted": true
},
"name": "Automate Figma Versioning and Jira Updates with n8n Webhook Integration",
"tags": [],
"nodes": [
{
"id": "a3853962-36ce-4a2f-b9d6-c2807652d7ff",
"name": "Sticky Note",
"type": "n8n-nodes-base.stickyNote",
"position": [
-20,
-260
],
"parameters": {
"width": 700,
"height": 200,
"content": "## Note\nTo use this automation, you will need the Figma Commit Plugin installed and configured. The plugin sends the design version details via a webhook to trigger this n8n workflow.\n\nYou can find the Figma Commit Plugin on GitHub here:\n\ud83d\udd17 [Figma Commit Plugin on GitHub](https://github.com/omid-d3v/Figma-Commit-plugin-with-webhook/)\n\nMake sure to follow the setup instructions in the plugin\u2019s documentation to get started."
},
"typeVersion": 1
},
{
"id": "843f1e0b-4c8b-4744-a9b7-8ce5725768bc",
"name": "Find Jira Issue",
"type": "n8n-nodes-base.jira",
"position": [
220,
0
],
"parameters": {
"issueKey": "={{ $json.issueLink }}",
"operation": "get",
"additionalFields": {}
},
"credentials": {
"jiraSoftwareCloudApi": {
"name": "<your credential>"
}
},
"typeVersion": 1
},
{
"id": "59101813-9625-4d1f-b2b6-7ff442c1fe0f",
"name": "Add Comment in Issue",
"type": "n8n-nodes-base.jira",
"position": [
440,
0
],
"parameters": {
"comment": "={{ $('Figma Trigger').item.json.pageName }}{{ '\\n' }}{{ $('Figma Trigger').item.json.versionName }}{{ '\\n' }}{{ $('Figma Trigger').item.json.designLink }}{{ '\\n' }} {{ $now }}",
"options": {},
"issueKey": "={{ $json.key }}",
"resource": "issueComment"
},
"credentials": {
"jiraSoftwareCloudApi": {
"name": "<your credential>"
}
},
"typeVersion": 1
},
{
"id": "378150c5-b640-477a-861f-216e8b15c0e4",
"name": "Figma Trigger",
"type": "n8n-nodes-base.figmaTrigger",
"position": [
0,
0
],
"parameters": {
"teamId": "940915773877350235",
"triggerOn": "fileVersionUpdate"
},
"credentials": {
"figmaApi": {
"name": "<your credential>"
}
},
"typeVersion": 1
}
],
"active": true,
"settings": {
"executionOrder": "v1"
},
"versionId": "9525049e-7fca-4f83-bf6a-069d477f669e",
"connections": {
"Figma Trigger": {
"main": [
[
{
"node": "Find Jira Issue",
"type": "main",
"index": 0
}
]
]
},
"Find Jira Issue": {
"main": [
[
{
"node": "Add Comment in Issue",
"type": "main",
"index": 0
}
]
]
},
"Add Comment in Issue": {
"main": [
[]
]
}
}
}
Credentials you'll need
Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.
figmaApijiraSoftwareCloudApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Automate Figma Versioning and Jira Updates with n8n Webhook Integration. Uses stickyNote, jira, figmaTrigger. Event-driven trigger; 4 nodes.
Source: https://github.com/Zie619/n8n-workflows — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
How It Works: This n8n template automates the process of tracking design changes in Figma and updating relevant Jira issues. The template is triggered when a new version is created in Figma via a cust
⚠️ Important: This workflow uses the Autype community node and requires a self-hosted n8n instance.
Let a user load multiple files with a Form node, and process the binary data. A very important workflow for many tools.
Turn a .rvt project into open, analysis-ready data (XLSX + optional DAE/PDF) using the RvtExporter.exe from the DDC Revit toolkit. This n8n template provides a Form UI to set paths and flags, then run
Post on X. Uses airtop, executeWorkflowTrigger, formTrigger, stopAndError. Event-driven trigger; 10 nodes.