Sync UnoPim product catalogs to Shopify and log results in Sheets, Slack and Jira
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on Uno Pim events (product.updated). Along the way it connects Shopify, Google Sheets, Slack and Jira Software and 1 more.
How it runs
Trigger: On Uno Pim events (product.updated).
- Settings (Edit Fields (Set)): sets 3 fields: locale, channel, storeIdAttribute
- Build the store payload (Code): runs custom JavaScript code
- Ready to publish? (If): checks a condition and branches into true / false
- Already in the store? (If): checks a condition and branches into true / false
- Open a data quality ticket (Jira Software): create (issue)
- Update the store product (Shopify): update (product)
- Create the store product (Shopify): create (product)
- Warn the catalog channel (Slack): uses Slack
- Log the sync to a sheet (Google Sheets): append
- Post the sync summary (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-unopim is verified or supports 3.0 (used in Product updated in UnoPim).
Nodes used (8)
- Uno Pim Trigger
n8n-nodes-unopim.unoPimTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Shopify
n8n-nodes-base.shopify - Google Sheets
n8n-nodes-base.googleSheets - Slack
n8n-nodes-base.slack - Jira Software
n8n-nodes-base.jira
From the author
Quick overview The UnoPim Trigger fires the moment a product is saved, so a Shopify storefront updates within seconds. Products that are ready are published, incomplete ones open a Jira ticket naming the missing fields, and every run is logged to Google…