Screen DPDP consent manager registrations with GPT-4o, Google Sheets and Gmail
Ready for 3.0What this workflow does
This AI workflow has 14 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Google Sheets, Azure OpenAI Chat Model and Gmail.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Extract & Normalize Registration Payload (Code): runs custom JavaScript code
- Validate Registration Payload Structure (If): checks a condition and branches into true / false
- AI Eligibility Evaluator (DPDP Compliance) (AI Agent): runs an AI agent, with model: Configure GPT-4o — Eligibility Evaluation Model
- Write Initial Registration Entry to Sheet (Google Sheets): append
- Log Invalid Registration Requests to Sheet (Google Sheets): append
- Parse AI Eligibility JSON Output (Code): runs custom JavaScript code
- Validate Eligibility Status (If): checks a condition and branches into true / false
- Merge Registration + Eligibility Summary (Code): runs custom JavaScript code
- Send Rejection Email to Applicant (Gmail): uses Gmail
- Send Approval Email to Compliance Team (Gmail): uses Gmail
…plus 2 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)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Google Sheets
n8n-nodes-base.googleSheets - Azure OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatAzureOpenAi - AI Agent
@n8n/n8n-nodes-langchain.agent - Gmail
n8n-nodes-base.gmail - Edit Fields (Set)
n8n-nodes-base.set
From the author
📘 Description This workflow automates the complete DPDP-aligned Consent Manager Registration screening pipeline — from intake to eligibility evaluation and final compliance routing. Every incoming registration request is normalized, validated, logged,…