Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
Event-Driven AutomationIntermediate

Automated Booking to CRM and Newsletter

Automated Booking to CRM and Newsletter is a 7-node automation blueprint connecting Google Sheets, Telegram, Custom API for Newsletter. Inspect its trigger, execution graph, branches, and implementation requirements.

Google SheetsTelegramCustom API for Newsletter

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

7

Nodes

6

Edges

6

Zones

System stack

3 integrations

  • Google Sheets
  • Telegram
  • Custom API for Newsletter
Automated Booking to CRM and Newsletter interactive execution graphStructural view of 7 workflow nodes and 6 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.on New Booking. trigger node, calTrigger. 0 incoming and 1 outgoing connections.on New BookingTRIGGERCALTRIGGER0 IN / 1 OUTSplit Attendees. transform node, splitOut. 1 incoming and 1 outgoing connections.Split AttendeesTRANSFORMSPLITOUT1 IN / 1 OUTset data. transform node, set. 1 incoming and 1 outgoing connections.set dataTRANSFORMSET1 IN / 1 OUTSet Attendee. transform node, set. 1 incoming and 1 outgoing connections.Set AttendeeTRANSFORMSET1 IN / 1 OUTAdd users. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.Add usersGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTAdd subscriber. integration node, httpRequest. 1 incoming and 1 outgoing connections.Add subscriberINTEGRATIONHTTPREQUEST1 IN / 1 OUTnotify in channel. Telegram node, telegram. 1 incoming and 0 outgoing connections.notify in channelTELEGRAMTELEGRAM1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 2e32e686697801dbEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

1 node

Events, schedules, and unconnected roots that can start an execution.

on New Booking

Trigger

02

Data & operations

5 nodes

Transformations and external-system actions that move the work forward.

Split Attendees

Transform

Add users

Integration

Add subscriber

Integration

Set Attendee

Transform

set data

Transform

03

Intelligence & routing

0 nodes

Model calls and control points that interpret, branch, or govern the run.

No nodes observed in this zone
04

Terminal actions

1 node

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

notify in channel

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
prefix
Quality score
12 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas