Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Automated Recipe Notifier via Telegram

Automated Recipe Notifier via Telegram is a 15-node automation blueprint connecting Airtable, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

AirtableTelegram

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.

15

Nodes

13

Links

2

Run groups

Connected tools

2 integrations

  • Airtable
  • Telegram

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Recipe Notifier via Telegram execution lanes2 run groups containing 15 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.Telegram Trigger - people join bot. Telegram node, telegramTrigger. 0 incoming and 2 outgoing connections.STARTTelegram Trigger - people…TELEGRAMTELEGRAMTRIGGER0 IN / 2 OUTAirtable. Airtable node, airtable. 1 incoming and 1 outgoing connections.STEP 02AirtableAIRTABLEAIRTABLE1 IN / 1 OUTTelegram - Welcome Message. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 02Telegram - Welcome MessageTELEGRAMTELEGRAM1 IN / 1 OUTIF. decision node, if. 1 incoming and 1 outgoing connections.STEP 03IFDECISIONIF1 IN / 1 OUTGet recipes. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get recipesINTEGRATIONHTTPREQUEST1 IN / 1 OUTSet1. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Set1TRANSFORMSET1 IN / 1 OUTTelegram Recipe Image. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 04Telegram Recipe ImageTELEGRAMTELEGRAM1 IN / 1 OUTAirtable1. Airtable node, airtable. 1 incoming and 0 outgoing connections.OUTCOMEAirtable1AIRTABLEAIRTABLE1 IN / 0 OUTTelegram Recipe URL. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegram Recipe URLTELEGRAMTELEGRAM1 IN / 0 OUTCron. integration node, cron. 0 incoming and 1 outgoing connections.STARTCronINTEGRATIONCRON0 IN / 1 OUTAirtable2. Airtable node, airtable. 1 incoming and 1 outgoing connections.STEP 02Airtable2AIRTABLEAIRTABLE1 IN / 1 OUTSet. transform node, set. 1 incoming and 1 outgoing connections.STEP 03SetTRANSFORMSET1 IN / 1 OUTGet recipes from API. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Get recipes from APIINTEGRATIONHTTPREQUEST1 IN / 1 OUTRecipe Photo. Telegram node, telegram. 1 incoming and 1 outgoing connections.STEP 05Recipe PhotoTELEGRAMTELEGRAM1 IN / 1 OUTRecipe URL. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMERecipe URLTELEGRAMTELEGRAM1 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.15 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

Telegram Trigger - people join…

8 Execution Links

  1. Start

    Telegram Trigger - people join bot

    Trigger

  2. Step 2

    Airtable

    Integration

    Telegram - Welcome Message

    Integration

  3. Step 3

    IF

    Decision

    Get recipes

    Integration

  4. Step 4

    Set1

    Transform

    Telegram Recipe Image

    Integration

  5. Outcome

    Airtable1

    Integration

    Telegram Recipe URL

    Integration

02

Run Group

Cron

5 Execution Links

  1. Start

    Cron

    Integration

  2. Step 2

    Airtable2

    Integration

  3. Step 3

    Set

    Transform

  4. Step 4

    Get recipes from API

    Integration

  5. Step 5

    Recipe Photo

    Integration

  6. Outcome

    Recipe URL

    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