G Glow Automation Relocation
Operational controls extended · 27 Aug 2026

Make → n8n · Before & after

Less sprawl.
More ownership.

A natural overview of how Glow’s automations move from separate Make scenarios into an entity-owned, observable n8n architecture.

↗
This overview will continue to grow.The 20-scenario Slack baseline and the final additional migration scope are verified. All 19 migratable scenarios were cut over. A dedicated Clay Idempotency Gate was added as a further operational automation on 27 August. PandaDoc and TikTok are explicitly excluded and remain authoritative in Make.
20Slack-baseline Make scenarios migrated and disabled
19/19final migration scope cut over and live verified
6/6Slack routes served by the Glow Bot
10/10Batch-1 cutovers fully verified

The architecture shift

The migration was not a one-for-one copy. Repeated scenarios were consolidated by business purpose, with shared security, routing and idempotency underneath.

Before · Make

Distributed and identity-blurred

  • 20 independently operated scenarios
  • Personal and third-party Slack identities
  • Copy-paste drift across 12 Perspective funnels
  • Inconsistent deduplication and embedded webhooks
After · n8n

Consolidated and Glow-owned

  • 7 business workflows with shared infrastructure
  • Glow Bot on a six-channel allowlist
  • Persistent atomic event claims and safe retries
  • Authenticated ingress, source-level cutover evidence

Batch 1 · verified cutover

All ten source scenarios now run through active Sharp n8n replacements and all ten Make rollback copies are disabled. The six Clay action columns were switched individually with authenticated mappings and a five-row Close readback; the single open legacy exception was transferred to the scheduled n8n report.

Before · MakeRoleAfter · n8nStatusLinks
Calendly Handler
1448479
Signed booking and cancellation eventsGlow - Calendly to Close
BKtU842oHgBtbITx
Cut over · Make disabled
Employee-count control agent
7701500
Close data qualityGlow - Close Data Quality
hhPcviw3430yL4Ei
Cut over · Make disabled
Blacklist double-checking agent
8294845
Close data qualityGlow - Close Data Quality
hhPcviw3430yL4Ei
Cut over · Make disabled
Company-size enrichment
5982913
Scheduled Clay dispatcherGlow - Clay Dispatchers
gAXFsfQi2nUTcLed
Cut over · Make disabled
Person enrichment bot
8296048
Scheduled Clay dispatcherGlow - Clay Dispatchers
gAXFsfQi2nUTcLed
Cut over · Make disabled
GHI person-enrichment pipeline
9233012
Scheduled Clay dispatcherGlow - Clay Dispatchers
gAXFsfQi2nUTcLed
Cut over · Make disabled
GHI marked-enrichment pipeline
9233187
Scheduled Clay dispatcherGlow - Clay Dispatchers
gAXFsfQi2nUTcLed
Cut over · Make disabled
Clay Waterfall & AI callback
8193389
Clay → Close callbackGlow - Clay Callbacks
CWQcIho0I7vOy0Gz
Cut over · Make disabled
Clay person-enrichment callback
8296121
Clay → Close callbackGlow - Clay Callbacks
CWQcIho0I7vOy0Gz
Cut over · Make disabled
Faulty leads report
8693667
Scheduled exception reportGlow - Clay Exception Report
NzuR5iZccdyUgkOT
Cut over · backlog migrated

Additional operational automation

The Clay Idempotency Gate was added after the migration to protect all four Close → Clay dispatch paths. Before a paid Clay request is sent, the gate atomically claims the combination of source, Close Lead ID and enrichment cycle in persistent storage. Concurrent work stops as busy; completed replays bypass Clay. On the three marked branches, duplicate replays still resume the downstream Close marker so an interrupted run can recover without creating another Clay row. Both GHI paths deliberately share one namespace, while the cycle key preserves intended future re-enrichment.

BeforeProtected scopeAdditional n8n automationStatusLink
Clay retry and duplicate risk
Post-cutover hardening · 27 Aug 2026
4 dispatcher paths · source + Lead ID + cycleGlow - Clay Idempotency Gate
ToA4IHV0jfFRteZM
Live · acquired / busy / duplicate verified

Final extension

Thirteen scenarios were investigated. Nine belonged to the final migration scope and all nine are cut over and verified. Four remain deliberately untouched in Make: two TikTok scenarios by scope decision and two PandaDoc automations because Glow has no PandaDoc Production API. PandaDoc was not migrated; its read-only n8n prototype is not presented as an “after” system.

Before · MakeRoleAfter · n8nStatusLinks
Webhook → Clay Enrichment
5353046
Legacy import processorGlow - Import Processor
SKuLe0dUHADQKPfw
Cut over · Make disabled
ID Leads → Clay
7479775
ID-lead intakeGlow - Import Processor
SKuLe0dUHADQKPfw
Cut over · Make disabled
Google Sheet → Webhook
7805552
Scheduled table sourceGlow - Import Source Adapter
QaMeD4PFoKwxtqVJ
Cut over · Make disabled
Apify → Direct Import
8138568
Secure job-batch dispatcherGlow - Import Source Adapter
QaMeD4PFoKwxtqVJ
Cut over · Make disabled
Webhook → Clay / Close Contacts
8140680
Job importGlow - Import Processor
SKuLe0dUHADQKPfw
Cut over · Make disabled
Close Opportunity → PandaDoc
1483998
Signed opportunity eventNot migrated
Make remains authoritative
Excluded · PandaDoc Production API unavailable
Close Link → PandaDoc
7601241
Manual offer requestNot migrated
Make remains authoritative
Excluded · PandaDoc Production API unavailable
TikTok Form → LeadTable
6312857
Instant Form AExcluded from migration
Make remains authoritative
Excluded · untouched in Make
TikTok Form → LeadTable · New
6648382
Instant Form BExcluded from migration
Make remains authoritative
Excluded · untouched in Make
Email Permutation · Webhook Tool
7824530
Name + domain intakeGlow - Email Permutation Planner
j72xSrfAlY9Mi8tP · 47-node Sharp
Retired orphan · Make disabled · provider E2E verified
Email Permutation · Subscenario
8099155
CRM-context intakeGlow - Email Permutation Planner
j72xSrfAlY9Mi8tP · task-bound BounceBan
Cut over · Make disabled · provider E2E verified
Turbo Trigger · Job Enrichment
8280464
Clay job callbackGlow - Clay Job Enrichment Callback
1LDubsRvUnq3x3Um
Cut over · Make disabled
Python Scraper → Empty JSON
8830036
Retired legacy no-opGlow - Legacy Scraper Compatibility
lU3dqvHufwEmo9lU
Cut over · Make disabled

Every relocation

Migrated rows link to the former Make scenario and current n8n destination. Explicit exceptions link only to their still-authoritative Make scenario. Access follows the permissions of the respective platforms.

Before · MakeTriggerAfter · n8nStatusLinks
Closing Form → Airtable + Slack
2693645
Webhook / AirtableGlow - Closing Onboarding
CFf5crnTZ5iJYYfS
Cut over
Import Email · Jotform to Close
7021457
JotformGlow - Jotform Reply Intake
DhmYSypuEdAGqUQ6
Cut over
Open import-data report
7786547
Friday scheduleGlow - Backoffice Reports
GlvG2t3pQz7HEQgh
Consolidated
SEO & ID lead report
8171707
Monday scheduleGlow - Backoffice Reports
GlvG2t3pQz7HEQgh
Consolidated
Lead Magnet · DE Elektro
5151856
Perspective webhookGlow - Lead Magnet Intake
Mlj1sUv6Q9YRIqH3
Consolidated
Lead Magnet · Top 5 Benefits
6413819
Perspective webhookGlow - Lead Magnet Intake
Mlj1sUv6Q9YRIqH3
Consolidated
Outbound Call CA Handler
9542419
Close signed webhookGlow - Close Sales Events
Xvhq1Al5oNgt0mYD
HMAC v2
Perspective · DE Website
6047899
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · CH Website
6048397
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · DE Blog
6054552
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · CH Blog
6054727
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · DE Dynamic Vertical
6751478
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · DE Dynamic Region
6751505
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · CH Dynamic Vertical
6751536
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · CH Dynamic Region
6751554
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · CH Dynamic Service
6788205
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · DE Dynamic Service
6790066
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · DE Website Benefits
7256567
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Perspective · DE Blog Post Offer
8612501
PerspectiveGlow - Perspective SEO Intake
4mGOMlpA769nELey
Consolidated
Job Ad Generator · Slack
9310506
Authenticated webhookGlow - Tool Leads
zUSiR390lV7FhY2a
Cut over

What changed underneath

The visible workflow consolidation sits on top of shared operational controls that did not exist consistently before.

🤖

Entity-owned identity

Slack delivery now uses the Glow Bot instead of personal OAuth identities or foreign workspace connections.

🧭

Fixed channel routing

A central gateway maps logical routes to six approved Glow channels. Callers cannot inject arbitrary channel IDs.

🔐

Authenticated ingress

Webhooks use signatures, header credentials or a hashed provider key. Secrets remain outside workflow source.

◉

Atomic idempotency

The dedicated Clay gate and its persistent event-claim table prevent repeated paid dispatches during retries, races and delayed search-index updates.

↻

Safe cutovers

Sources were switched and validated individually before their corresponding Make rollback copies were disabled.

⌁

Auditable baseline

The final audit checks active workflows, Make status, Slack identity, channel membership and recent errors.

PD
PandaDoc was not migrated

Make 1483998 and 7601241 remain active and authoritative. Glow has no PandaDoc Production API entitlement, the native Make credential cannot be exported, and the read-only n8n prototype is not counted as a production relocation.

!
Explicit exception: Make 9599483

“pos. Reply Hiring-Intelligence” is not part of this 20-scenario relocation. It remains active and unchanged in Make and is deliberately excluded from the migration audit.

×
Retired integration: Smartlead / Make 8714747

Smartlead was cancelled on 25 August 2026. Its reply webhook still appears active in Make, but the service is not being recreated in n8n. Any Make deactivation is handled separately as an explicit cleanup, not as a migration cutover.