Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

Automated News Summary and Chat Update

Automated News Summary and Chat Update is a 13-node automation blueprint connecting Google Gemini, Telegram, Custom HTTP API for news. Inspect its trigger, execution graph, branches, and implementation requirements.

Google GeminiTelegramCustom HTTP API for news

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.

13

Nodes

13

Links

1

Run groups

Connected tools

3 integrations

  • Google AI
  • Telegram
  • Custom HTTP API for news

Canvas controls

Fit wide systems, then zoom into any run group.

Automated News Summary and Chat Update execution lanes1 run groups containing 13 workflow nodes and 13 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.Schedule Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTSchedule TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTCreateYearsList. transform node, code. 1 incoming and 1 outgoing connections.STEP 02CreateYearsListTRANSFORMCODE1 IN / 1 OUTCleanUpYearList. transform node, set. 1 incoming and 1 outgoing connections.STEP 03CleanUpYearListTRANSFORMSET1 IN / 1 OUTSplitOutYearList. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04SplitOutYearListTRANSFORMSPLITOUT1 IN / 1 OUTGetFrontPage. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05GetFrontPageINTEGRATIONHTTPREQUEST1 IN / 1 OUTExtractDetails. integration node, html. 1 incoming and 2 outgoing connections.STEP 06ExtractDetailsINTEGRATIONHTML1 IN / 2 OUTGetHeadlines. transform node, set. 1 incoming and 1 outgoing connections.STEP 07GetHeadlinesTRANSFORMSET1 IN / 1 OUTGetDate. transform node, set. 1 incoming and 1 outgoing connections.STEP 07GetDateTRANSFORMSET1 IN / 1 OUTMergeHeadlinesDate. decision node, merge. 2 incoming and 1 outgoing connections.STEP 08MergeHeadlinesDateDECISIONMERGE2 IN / 1 OUTSingleJson. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 09SingleJsonTRANSFORMAGGREGATE1 IN / 1 OUTBasic LLM Chain. ai node, chainLlm. 2 incoming and 1 outgoing connections.STEP 10Basic LLM ChainAICHAINLLM2 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTGoogle Gemini Chat Model. Google AI node, lmChatGoogleGemini. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Google Gemini Chat ModelGOOGLE AILMCHATGOOGLEGEMINI0 IN / 1 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.13 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

Schedule Trigger

12 Execution Links1 Support Dependency

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    CreateYearsList

    Transform

  3. Step 3

    CleanUpYearList

    Transform

  4. Step 4

    SplitOutYearList

    Transform

  5. Step 5

    GetFrontPage

    Integration

  6. Step 6

    ExtractDetails

    Integration

  7. Step 7

    GetHeadlines

    Transform

    GetDate

    Transform

  8. Step 8

    MergeHeadlinesDate

    Decision

  9. Step 9

    SingleJson

    Transform

  10. Step 10

    Basic LLM Chain

    AI reasoning

  11. Outcome

    Telegram

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

1 node

  • Google Gemini Chat Model

    AI reasoning dependency

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