Skip to Workflow Atlas
ETL Pipeline with Event-Driven AutomationIntermediate

Notion to Webflow Blog Sync

Notion to Webflow Blog Sync is a 24-node automation blueprint connecting Notion, Webflow, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

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.

24

Nodes

29

Links

1

Run groups

Connected tools

3 integrations

  • Notion
  • Webflow
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Notion to Webflow Blog Sync execution lanes1 run groups containing 24 workflow nodes and 29 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 OUTGet all blog posts1. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 02Get all blog posts1NOTIONNOTION1 IN / 1 OUTIs sync checked?1. decision node, filter. 1 incoming and 1 outgoing connections.STEP 03Is sync checked?1DECISIONFILTER1 IN / 1 OUTSlug uniqueness checker and differentiator1. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Slug uniqueness checker a…TRANSFORMCODE1 IN / 1 OUTFor each blog post1. integration node, splitInBatches. 2 incoming and 3 outgoing connections.STEP 05For each blog post1INTEGRATIONSPLITINBATCHES2 IN / 3 OUTGet all page data. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 06Get all page dataNOTIONNOTION1 IN / 1 OUTSuccess message1. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 07Success message1SLACKSLACK1 IN / 0 OUTGet simple page data. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 08Get simple page dataNOTIONNOTION1 IN / 1 OUTTake cover url. transform node, set. 1 incoming and 1 outgoing connections.STEP 09Take cover urlTRANSFORMSET1 IN / 1 OUTMerge1. decision node, merge. 2 incoming and 2 outgoing connections.STEP 10Merge1DECISIONMERGE2 IN / 2 OUTGet blocks1. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 11Get blocks1NOTIONNOTION1 IN / 1 OUTTurn blocks into HTML1. transform node, code. 1 incoming and 1 outgoing connections.STEP 12Turn blocks into HTML1TRANSFORMCODE1 IN / 1 OUTCraft the rich text element1. transform node, code. 1 incoming and 1 outgoing connections.STEP 13Craft the rich text eleme…TRANSFORMCODE1 IN / 1 OUTFinal Notion post data. Notion node, merge. 2 incoming and 2 outgoing connections.STEP 14Final Notion post dataNOTIONMERGE2 IN / 2 OUTData transporter, Notion posts to sync1. Notion node, noOp. 1 incoming and 1 outgoing connections.STEP 15Data transporter, Notion …NOTIONNOOP1 IN / 1 OUTGet all collection posts1. integration node, webflow. 1 incoming and 1 outgoing connections.STEP 16Get all collection posts1INTEGRATIONWEBFLOW1 IN / 1 OUTCompare by slug1. decision node, compareDatasets. 2 incoming and 3 outgoing connections.STEP 17Compare by slug1DECISIONCOMPAREDATASETS2 IN / 3 OUTCreate post1. integration node, webflow. 1 incoming and 1 outgoing connections.STEP 18Create post1INTEGRATIONWEBFLOW1 IN / 1 OUTAdd Webflow item id to Notion data. Notion node, code. 1 incoming and 1 outgoing connections.STEP 19Add Webflow item id to No…NOTIONCODE1 IN / 1 OUTMerge2. decision node, merge. 2 incoming and 1 outgoing connections.STEP 20Merge2DECISIONMERGE2 IN / 1 OUTUpdate in "Blog Posts". integration node, webflow. 1 incoming and 1 outgoing connections.STEP 21Update in "Blog Posts"INTEGRATIONWEBFLOW1 IN / 1 OUTAdd slug to posts1. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 22Add slug to posts1NOTIONNOTION1 IN / 1 OUTUpdate slug on posts1. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 23Update slug on posts1NOTIONNOTION1 IN / 1 OUTData transporter1. integration node, noOp. 2 incoming and 1 outgoing connections.OUTCOMEData transporter1INTEGRATIONNOOP2 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.24 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

29 Execution Links
  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Get all blog posts1

    Integration

  3. Step 3

    Is sync checked?1

    Decision

  4. Step 4

    Slug uniqueness checker and differentiator1

    Transform

  5. Step 5

    For each blog post1

    Integration

  6. Step 6

    Get all page data

    Integration

  7. Step 7

    Success message1

    Integration

  8. Step 8

    Get simple page data

    Integration

  9. Step 9

    Take cover url

    Transform

  10. Step 10

    Merge1

    Decision

  11. Step 11

    Get blocks1

    Integration

  12. Step 12

    Turn blocks into HTML1

    Transform

  13. Step 13

    Craft the rich text element1

    Transform

  14. Step 14

    Final Notion post data

    Decision

  15. Step 15

    Data transporter, Notion posts to sync1

    Integration

  16. Step 16

    Get all collection posts1

    Integration

  17. Step 17

    Compare by slug1

    Decision

  18. Step 18

    Create post1

    Integration

  19. Step 19

    Add Webflow item id to Notion data

    Transform

  20. Step 20

    Merge2

    Decision

  21. Step 21

    Update in "Blog Posts"

    Integration

  22. Step 22

    Add slug to posts1

    Integration

  23. Step 23

    Update slug on posts1

    Integration

  24. Outcome

    Data transporter1

    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.