Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
ETL PipelineAI systemIntermediate

LinkedIn Content Automation Workflow

LinkedIn Content Automation Workflow is a 13-node automation blueprint connecting Airtable, Telegram, LinkedIn. Inspect its trigger, execution graph, branches, and implementation requirements.

AirtableTelegramLinkedIn

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.

13

Nodes

13

Edges

6

Zones

System stack

3 integrations

  • Airtable
  • Telegram
  • LinkedIn
LinkedIn Content Automation Workflow interactive execution graphStructural view of 13 workflow nodes and 13 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Morning 9 Clock. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.Morning 9 ClockTRIGGERSCHEDULETRIGGER0 IN / 1 OUTget random tags. transform node, code. 2 incoming and 1 outgoing connections.get random tagsTRANSFORMCODE2 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.IfDECISIONIF1 IN / 2 OUTGet List of records used. Airtable node, airtable. 1 incoming and 1 outgoing connections.Get List of records usedAIRTABLEAIRTABLE1 IN / 1 OUTFetch Medium post content. integration node, httpRequest. 1 incoming and 1 outgoing connections.Fetch Medium post contentINTEGRATIONHTTPREQUEST1 IN / 1 OUTmap used articls ids. transform node, code. 1 incoming and 1 outgoing connections.map used articls idsTRANSFORMCODE1 IN / 1 OUTUpdate the used node. Airtable node, airtable. 1 incoming and 1 outgoing connections.Update the used nodeAIRTABLEAIRTABLE1 IN / 1 OUTfetch article ids from tag. integration node, httpRequest. 1 incoming and 1 outgoing connections.fetch article ids from tagINTEGRATIONHTTPREQUEST1 IN / 1 OUTdownload image for post. integration node, httpRequest. 1 incoming and 1 outgoing connections.download image for postINTEGRATIONHTTPREQUEST1 IN / 1 OUTsent the status. Telegram node, telegram. 1 incoming and 0 outgoing connections.sent the statusTELEGRAMTELEGRAM1 IN / 0 OUTfilter only unused Ids. decision node, filter. 1 incoming and 1 outgoing connections.filter only unused IdsDECISIONFILTER1 IN / 1 OUTFetch Medium post using Article Id. integration node, httpRequest. 1 incoming and 1 outgoing connections.Fetch Medium post using A…INTEGRATIONHTTPREQUEST1 IN / 1 OUTmake Linkedin post. integration node, linkedIn. 1 incoming and 1 outgoing connections.make Linkedin postINTEGRATIONLINKEDIN1 IN / 1 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 beedd4da19a455d2Enter 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

1 node

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

Morning 9 Clock

Trigger

02

Data & operations

9 nodes

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

Get List of records used

Integration

Update the used node

Integration

map used articls ids

Transform

get random tags

Transform

fetch article ids from tag

Integration

Fetch Medium post using Article Id

Integration

+ 3 more in system map
03

Intelligence & routing

2 nodes

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

filter only unused Ids

Decision

If

Decision

04

Terminal actions

1 node

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

sent the status

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