Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
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

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

  • Airtable
  • Telegram
  • LinkedIn

Canvas controls

Fit wide systems, then zoom into any run group.

LinkedIn Content Automation Workflow 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.Morning 9 Clock. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTMorning 9 ClockTRIGGERSCHEDULETRIGGER0 IN / 1 OUTget random tags. transform node, code. 2 incoming and 1 outgoing connections.STEP 02get random tagsTRANSFORMCODE2 IN / 1 OUTIf. decision node, if. 1 incoming and 2 outgoing connections.STEP 03IfDECISIONIF1 IN / 2 OUTGet List of records used. Airtable node, airtable. 1 incoming and 1 outgoing connections.STEP 04Get List of records usedAIRTABLEAIRTABLE1 IN / 1 OUTFetch Medium post content. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Fetch Medium post contentINTEGRATIONHTTPREQUEST1 IN / 1 OUTmap used articls ids. transform node, code. 1 incoming and 1 outgoing connections.STEP 06map used articls idsTRANSFORMCODE1 IN / 1 OUTUpdate the used node. Airtable node, airtable. 1 incoming and 1 outgoing connections.STEP 07Update the used nodeAIRTABLEAIRTABLE1 IN / 1 OUTfetch article ids from tag. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 08fetch article ids from tagINTEGRATIONHTTPREQUEST1 IN / 1 OUTdownload image for post. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 09download image for postINTEGRATIONHTTPREQUEST1 IN / 1 OUTsent the status. Telegram node, telegram. 1 incoming and 0 outgoing connections.STEP 10sent the statusTELEGRAMTELEGRAM1 IN / 0 OUTfilter only unused Ids. decision node, filter. 1 incoming and 1 outgoing connections.STEP 11filter only unused IdsDECISIONFILTER1 IN / 1 OUTmake Linkedin post. integration node, linkedIn. 1 incoming and 1 outgoing connections.STEP 12make Linkedin postINTEGRATIONLINKEDIN1 IN / 1 OUTFetch Medium post using Article Id. integration node, httpRequest. 1 incoming and 1 outgoing connections.OUTCOMEFetch Medium post using A…INTEGRATIONHTTPREQUEST1 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

Morning 9 Clock

13 Execution Links

  1. Start

    Morning 9 Clock

    Trigger

  2. Step 2

    get random tags

    Transform

  3. Step 3

    If

    Decision

  4. Step 4

    Get List of records used

    Integration

  5. Step 5

    Fetch Medium post content

    Integration

  6. Step 6

    map used articls ids

    Transform

  7. Step 7

    Update the used node

    Integration

  8. Step 8

    fetch article ids from tag

    Integration

  9. Step 9

    download image for post

    Integration

  10. Step 10

    sent the status

    Integration

  11. Step 11

    filter only unused Ids

    Decision

  12. Step 12

    make Linkedin post

    Integration

  13. Outcome

    Fetch Medium post using Article Id

    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