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

Automated Recipe Sharing Workflow

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

AirtableTelegram

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.

15

Nodes

13

Edges

6

Zones

System stack

2 integrations

  • Airtable
  • Telegram
Automated Recipe Sharing Workflow interactive execution graphStructural view of 15 workflow nodes and 13 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Telegram Trigger - people join bot. Telegram node, telegramTrigger. 0 incoming and 2 outgoing connections.Telegram Trigger - people…TELEGRAMTELEGRAMTRIGGER0 IN / 2 OUTCron. integration node, cron. 0 incoming and 1 outgoing connections.CronINTEGRATIONCRON0 IN / 1 OUTAirtable. Airtable node, airtable. 1 incoming and 1 outgoing connections.AirtableAIRTABLEAIRTABLE1 IN / 1 OUTTelegram - Welcome Message. Telegram node, telegram. 1 incoming and 1 outgoing connections.Telegram - Welcome MessageTELEGRAMTELEGRAM1 IN / 1 OUTAirtable2. Airtable node, airtable. 1 incoming and 1 outgoing connections.Airtable2AIRTABLEAIRTABLE1 IN / 1 OUTIF. decision node, if. 1 incoming and 1 outgoing connections.IFDECISIONIF1 IN / 1 OUTGet recipes. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get recipesINTEGRATIONHTTPREQUEST1 IN / 1 OUTSet. transform node, set. 1 incoming and 1 outgoing connections.SetTRANSFORMSET1 IN / 1 OUTTelegram Recipe Image. Telegram node, telegram. 1 incoming and 1 outgoing connections.Telegram Recipe ImageTELEGRAMTELEGRAM1 IN / 1 OUTGet recipes from API. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get recipes from APIINTEGRATIONHTTPREQUEST1 IN / 1 OUTSet1. transform node, set. 1 incoming and 1 outgoing connections.Set1TRANSFORMSET1 IN / 1 OUTTelegram Recipe URL. Telegram node, telegram. 1 incoming and 0 outgoing connections.Telegram Recipe URLTELEGRAMTELEGRAM1 IN / 0 OUTRecipe Photo. Telegram node, telegram. 1 incoming and 1 outgoing connections.Recipe PhotoTELEGRAMTELEGRAM1 IN / 1 OUTAirtable1. Airtable node, airtable. 1 incoming and 0 outgoing connections.Airtable1AIRTABLEAIRTABLE1 IN / 0 OUTRecipe URL. Telegram node, telegram. 1 incoming and 0 outgoing connections.Recipe URLTELEGRAMTELEGRAM1 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 08defb579cb5659fEnter 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

2 nodes

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

Cron

Integration

Telegram Trigger - people join bot

Trigger

02

Data & operations

9 nodes

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

Airtable2

Integration

Set

Transform

Recipe Photo

Integration

Airtable

Integration

Telegram Recipe Image

Integration

Set1

Transform

+ 3 more in system map
03

Intelligence & routing

1 node

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

IF

Decision

04

Terminal actions

3 nodes

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

Recipe URL

Integration

Airtable1

Integration

Telegram Recipe URL

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
exact
Quality score
14 / 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