Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Duplicate Notion Page Archiver

Duplicate Notion Page Archiver is a 7-node automation blueprint connecting Notion. Inspect its trigger, execution graph, branches, and implementation requirements.

Notion

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.

7

Nodes

6

Links

1

Run groups

Connected tools

1 integrations

  • Notion

Canvas controls

Fit wide systems, then zoom into any run group.

Duplicate Notion Page Archiver execution lanes1 run groups containing 7 workflow nodes and 6 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.When a page is added to the database. Notion node, notionTrigger. 0 incoming and 1 outgoing connections.STARTWhen a page is added to t…NOTIONNOTIONTRIGGER0 IN / 1 OUTEvery day. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTEvery dayTRIGGERSCHEDULETRIGGER0 IN / 1 OUTGet pages from database. Notion node, notion. 2 incoming and 1 outgoing connections.STEP 02Get pages from databaseNOTIONNOTION2 IN / 1 OUTFormat items properly. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Format items properlyTRANSFORMSET1 IN / 1 OUTAggregate all items. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 04Aggregate all itemsTRANSFORMAGGREGATE1 IN / 1 OUTFilter duplicates. transform node, code. 1 incoming and 1 outgoing connections.STEP 05Filter duplicatesTRANSFORMCODE1 IN / 1 OUTArchive pages. Notion node, notion. 1 incoming and 0 outgoing connections.OUTCOMEArchive pagesNOTIONNOTION1 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.7 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

When a page is added to the da…

6 Execution Links

  1. Start

    When a page is added to the database

    Trigger

    Every day

    Trigger

  2. Step 2

    Get pages from database

    Integration

  3. Step 3

    Format items properly

    Transform

  4. Step 4

    Aggregate all items

    Transform

  5. Step 5

    Filter duplicates

    Transform

  6. Outcome

    Archive pages

    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