Monitor Klaviyo list decay with Postgres logging and Gmail reports
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 16 nodes and runs on a schedule (every day) (plus 1 other trigger). Along the way it connects Postgres and Gmail.
How it runs
Trigger: On a schedule (every day) (plus 1 other trigger).
- Set: Initialize Run (Edit Fields (Set)): sets or maps fields
- Prepare Error Data (Code): runs custom JavaScript code
- Get All Profiles (HTTP Request): calls an HTTP API
- Log Error to DB (Postgres): uses Postgres
- Extract Profile Items (Code): runs custom JavaScript code
- Send Error Alert (Gmail): uses Gmail
- Score Profiles (Code): runs custom JavaScript code
- Log Profiles to DB (Postgres): uses Postgres
- Build Run Summary (Code): runs custom JavaScript code
- Is Critical? (If): checks a condition and branches into true / false
…plus 4 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Postgres
n8n-nodes-base.postgres - If
n8n-nodes-base.if - Error Trigger
n8n-nodes-base.errorTrigger - Gmail
n8n-nodes-base.gmail
From the author
Klaviyo List Decay Detection Protect your sender reputation by automatically identifying and suppressing unengaged Klaviyo profiles every night. This workflow fetches your entire Klaviyo audience, scores each profile based on days since last engagement, and…