Messaging map agent - archived source
21 nodes · 21 non-note nodes
Open read-only HTML explorer →Download explicitly sanitized review JSON
Messaging
Homepage messaging studio: Turn client research into a clear homepage direction.
Homepage messaging studio connects market research, a dedicated messaging map and staged copy workflows. Client material becomes a shared direction document before drafting, giving the team a concrete reference for developing homepage copy and carrying that direction into final-copy preparation.
Workflow viewOpen full view: Original messaging-map workflow
About this view
Local import only
21-node archived source imported locally. Inactive; no credentials or execution.
Workflow viewOpen full view: Messaging-map source branch
About this view
Local import only
Native local source detail. Populated variants and approval frontend have not been recovered.
1 / 2
What it does
- Staged workflow family covering research, messaging maps, copy and final-copy preparation.
- Messaging-map workflow connecting stored client research with a separate direction document.
- Linked Airtable and Google Docs handoffs for carrying client context into copy development.
Why it matters
Gives writers a shared messaging foundation and a structured path from research to homepage copy.
- research, messaging map, copy and final-copy workflow exports
- 4 source stagesSource-defined stages excluding a testing variant. The populated variants/approval frontend has not been recovered.
Under the hood
Technology stack
n8n
Anthropic
Airtable
Google Docs- HTTP integration
Build note
Research, messaging map and homepage copy: four staged workflows.Source & context
Based on historical operating documentation and archived implementation evidence. Current end-to-end execution and business results were not independently retested.
Native n8n imports are local and inactive, not production execution. Historical recording capture dates are unknown; a displayed report period is not its capture date. Local source review: October 27, 2026. Public release and client-material clearance remain separate.
Start with research and a messaging map
The source family contains market research, messaging-map, copy and final-copy exports. The native backend view here is the twenty-one-node messaging-map component.
Keep variants and approval on their actual evidence
The SOP describes the intended variant and approval handoff. A populated approval inbox or accepted finished homepage was not recovered, so the case does not substitute invented client records.
Inspect the workflow rather than a placeholder dashboard
The backend canvas and its standalone source explorer make the available implementation structure concrete. The original source is shown as a local import, not as proof that the client-facing approval flow is currently live.
Inside the system
- Call and page-plan intake Parses Fathom context and the structured-plaintext Octopus plan into linked client records.
- Research document Turns stored client material into an inspectable market-research artifact.
- Messaging map Creates a separate messaging-direction document after research.
- Three homepage variants Produces linked copy alternatives and corresponding Google Docs.
- Approval inbox Lets the team or client choose a direction and records approval status.
The handoff
- Call and planning-file intake
- Research and messaging map
- Three homepage-copy variants
- Recorded final selection
Technology stack
Selected messaging workflow
- n8n
- Anthropic
- Airtable
- Google Docs
- HTTP integration
Selected recovered messaging-map workflow. Four-workflow system coverage remains partial.
Not established
- Full-system framework and production hosting are not established.
Source & context
| View | Provenance and limitation | Evidence class |
|---|---|---|
| Fig. 1 | Original messaging-map workflow 21-node archived source imported locally. Inactive; no credentials or execution. | Local import only |
| Fig. 2 | Messaging-map source branch Native local source detail. Populated variants and approval frontend have not been recovered. | Local import only |
Based on historical operating documentation and archived implementation evidence. Current end-to-end execution and business results were not independently retested.
Native n8n imports are local and inactive, not production execution. Historical recording capture dates are unknown; a displayed report period is not its capture date. Local source review: October 27, 2026. Public release and client-material clearance remain separate.
Reviewed: 2026-10-27
Map your version of this system
Bring the workflow your team is struggling to complete. We can map the inputs, integrations, review decisions and usable outputs before defining implementation scope.