Sync Approved Google Sheets Menu to OrbitPage Menus (n8n)

Keep your OrbitPage menu synced with approved Google Sheets rows—safely and with review

This n8n workflow previews, diffs, and synchronizes one native OrbitPage menu section from approved Google Sheets data. It supports additions and edits, shows an exact before/after diff by email for approval, and enforces controlled deletions—without overwriting unrelated page blocks or other menu sections.

What this workflow does

• Runs in a shared configuration for manual execution and scheduled checks every 30 minutes; scheduling remains disabled until the workflow is published.
• Uses SAMPLE mode for safe testing with isolated fictional scenarios—no external calls, no menu changes, and no reviewer email.
• In real runs, reads unformatted Google Sheets values, the current native OrbitPage menu, the current publication revision, and a dedicated n8n Data Table ownership registry.
• Updates only one managed menu section: existing page blocks, other menu sections, unmanaged items, and item fields outside the sheet mapping are preserved.
• Protects against accidental removals: missing or unapproved rows keep their previous items. Deletion requires an approved DELETE row and ALLOW_DELETIONS enabled.
• EMAIL_APPROVAL workflow: creates a pending claim and emails a before/after diff. Decline or expiry releases the claim without saving changes.
• Re-approval safety check: on approval, it re-reads the sheet, menu, publication revision, and ownership record. Changes in source/revision/ownership or manual edits to managed fields block the write.
• Revision precondition + read-back: the reviewed menu is written with an exact revision precondition; read-back checks confirm success before recording completion.

Use cases

• Automation engineers: validate menu changes with an email diff before publishing OrbitPage updates.
• SaaS operators: manage approved navigation content in Google Sheets while keeping other site elements intact.
• Teams: prevent accidental deletions by requiring explicit approved DELETE rows.

Technical details

• n8n nodes: if, set, code, data table, email send, sticky note.
• Core concepts: SAMPLE vs real runs, managed OrbitPage menu section updates, EMAIL_APPROVAL claims, and revision-guarded writes.