Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
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

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

7

Nodes

6

Links

1

Run groups

Connected tools

3 integrations

  • Google Sheets
  • Telegram
  • Custom API for Newsletter

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Booking to CRM and Newsletter execution lanes1 run groups containing 7 workflow nodes and 6 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.on New Booking. trigger node, calTrigger. 0 incoming and 1 outgoing connections.STARTon New BookingTRIGGERCALTRIGGER0 IN / 1 OUTSplit Attendees. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 02Split AttendeesTRANSFORMSPLITOUT1 IN / 1 OUTset data. transform node, set. 1 incoming and 1 outgoing connections.STEP 03set dataTRANSFORMSET1 IN / 1 OUTSet Attendee. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set AttendeeTRANSFORMSET1 IN / 1 OUTAdd users. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 05Add usersGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTAdd subscriber. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Add subscriberINTEGRATIONHTTPREQUEST1 IN / 1 OUTnotify in channel. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMEnotify in channelTELEGRAMTELEGRAM1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.7 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

on New Booking

6 Execution Links

  1. Start

    on New Booking

    Trigger

  2. Step 2

    Split Attendees

    Transform

  3. Step 3

    set data

    Transform

  4. Step 4

    Set Attendee

    Transform

  5. Step 5

    Add users

    Integration

  6. Step 6

    Add subscriber

    Integration

  7. Outcome

    notify in channel

    Integration

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