Require two-person email approvals for Airtable change requests with Gmail

by Melbin Francis ✓ · 0 views · created 2026-09-11 · Document Extraction

What this workflow does

This workflow has 24 nodes and runs on Airtable events. Along the way it connects Airtable and Gmail.

How it runs

Trigger: On Airtable events.

1. Approval Rules (Edit Fields (Set)): sets 6 fields: block_self_approval, reply_window_hours, pending_status…
2. Handle Each Request Once (Remove Duplicates): removes duplicate items
3. Read The Change Request (Code): runs custom JavaScript code
4. Still Waiting For A Decision? (If): checks a condition and branches into true / false
5. Handle One Request At A Time (Loop Over Items (Split in Batches)): loops over the items in batches
6. Read The Approver Pool (Airtable): search (record)
7. Pick Two Different Approvers (Code): runs custom JavaScript code
8. Enough Approvers Available? (If): checks a condition and branches into true / false
9. Ask The First Approver (Gmail): send and wait for a reply (message)
10. Refuse - No Eligible Approvers (Edit Fields (Set)): sets 1 field: refusal_reason

…plus 11 more steps. See the full node list below.

Services it uses

AirtableGmail

Before you upgrade to n8n 3.0

Nodes used (10)

• Airtable Triggern8n-nodes-base.airtableTrigger
• Edit Fields (Set)n8n-nodes-base.set
• Remove Duplicatesn8n-nodes-base.removeDuplicates
• Coden8n-nodes-base.code
• Ifn8n-nodes-base.if
• No Operation, do nothingn8n-nodes-base.noOp
• Loop Over Items (Split in Batches)n8n-nodes-base.splitInBatches
• Airtablen8n-nodes-base.airtable
• Gmailn8n-nodes-base.gmail
• Switchn8n-nodes-base.switch

From the author

Who's it for Teams that keep change requests in Airtable and need a second pair of eyes before anything is applied: database changes, access grants, refunds, supplier payments. How it works 1. A new row in the Change Requests table starts a run. Rows a human…

View the original on n8n.io → Check your own copy