Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Interest Data Collection & Reporting

Interest Data Collection & Reporting is a 10-node automation blueprint connecting Telegram, Facebook Graph API. Inspect its trigger, execution graph, branches, and implementation requirements.

TelegramFacebook Graph API

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.

10

Nodes

9

Links

1

Run groups

Connected tools

2 integrations

  • Telegram
  • Facebook Graph API

Canvas controls

Fit wide systems, then zoom into any run group.

Interest Data Collection & Reporting execution lanes1 run groups containing 10 workflow nodes and 9 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.Get interest name. Telegram node, telegramTrigger. 0 incoming and 1 outgoing connections.STARTGet interest nameTELEGRAMTELEGRAMTRIGGER0 IN / 1 OUTCheck message contents. decision node, if. 1 incoming and 2 outgoing connections.STEP 02Check message contentsDECISIONIF1 IN / 2 OUTExtract message. transform node, code. 1 incoming and 1 outgoing connections.STEP 03Extract messageTRANSFORMCODE1 IN / 1 OUTNo Operation, do nothing. integration node, noOp. 1 incoming and 0 outgoing connections.STEP 03No Operation, do nothingINTEGRATIONNOOP1 IN / 0 OUTSplit Message. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Split MessageTRANSFORMCODE1 IN / 1 OUTConnect to Graph API. integration node, facebookGraphApi. 1 incoming and 1 outgoing connections.STEP 05Connect to Graph APIINTEGRATIONFACEBOOKGRAPHAPI1 IN / 1 OUTSplit Interests into a Table. transform node, code. 1 incoming and 1 outgoing connections.STEP 06Split Interests into a Ta…TRANSFORMCODE1 IN / 1 OUTGet variables. transform node, code. 1 incoming and 1 outgoing connections.STEP 07Get variablesTRANSFORMCODE1 IN / 1 OUTCreate a Spreadsheet. integration node, spreadsheetFile. 1 incoming and 1 outgoing connections.STEP 08Create a SpreadsheetINTEGRATIONSPREADSHEETFILE1 IN / 1 OUTSend the Spreadsheet file. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMESend the Spreadsheet fileTELEGRAMTELEGRAM1 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.10 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

Get interest name

9 Execution Links

  1. Start

    Get interest name

    Trigger

  2. Step 2

    Check message contents

    Decision

  3. Step 3

    Extract message

    Transform

    No Operation, do nothing

    Integration

  4. Step 4

    Split Message

    Transform

  5. Step 5

    Connect to Graph API

    Integration

  6. Step 6

    Split Interests into a Table

    Transform

  7. Step 7

    Get variables

    Transform

  8. Step 8

    Create a Spreadsheet

    Integration

  9. Outcome

    Send the Spreadsheet file

    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