Audit UnoPim catalog completeness weekly and email a scorecard to your team
UnknownWhat this workflow does
This workflow has 11 nodes and runs on a schedule (every week at 07:00). Along the way it connects Linear, Slack, Google Sheets and Gmail and 1 more.
How it runs
Trigger: On a schedule (every week at 07:00).
- Settings (Edit Fields (Set)): sets 3 fields: requiredFields, locale, channel
- Read the whole catalog (Uno Pim): get many (product)
- Score each product (Code): runs custom JavaScript code
- Missing a required field? (If): checks a condition and branches into true / false
- Collect every score (Aggregate): combines items into one
- Create a data quality issue (Linear): create (issue)
- Build the scorecard (Code): runs custom JavaScript code
- Ping the catalog channel (Slack): uses Slack
- Append the weekly scorecard (Google Sheets): append
- Email the scorecard (Gmail): uses Gmail
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 Read the whole catalog).
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Uno Pim
n8n-nodes-unopim.unoPim - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Linear
n8n-nodes-base.linear - Slack
n8n-nodes-base.slack - Aggregate
n8n-nodes-base.aggregate - Google Sheets
n8n-nodes-base.googleSheets - Gmail
n8n-nodes-base.gmail
From the author
Quick overview Every Monday morning this workflow scores the whole UnoPim catalog against the fields you cannot ship without, opens a Linear issue for each product with gaps, and emails one scorecard so the trend is visible over months. How it works 1. A…