Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

Live Data Insights Automation

Live Data Insights Automation is a 19-node automation blueprint connecting OpenAI, Notion, Supabase. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAINotionSupabase

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.

19

Nodes

19

Links

1

Run groups

Connected tools

3 integrations

  • OpenAI
  • Notion
  • Supabase

Canvas controls

Fit wide systems, then zoom into any run group.

Live Data Insights Automation execution lanes1 run groups containing 19 workflow nodes and 19 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 OUTNotion Trigger. Notion node, notionTrigger. 0 incoming and 1 outgoing connections.STARTNotion TriggerNOTIONNOTIONTRIGGER0 IN / 1 OUTWhen chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTGet updated pages. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 02Get updated pagesNOTIONNOTION1 IN / 1 OUTQuestion and Answer Chain. ai node, chainRetrievalQa. 3 incoming and 0 outgoing connections.STEP 02Question and Answer ChainAICHAINRETRIEVALQA3 IN / 0 OUTInput Reference. integration node, noOp. 2 incoming and 1 outgoing connections.STEP 03Input ReferenceINTEGRATIONNOOP2 IN / 1 OUTLoop Over Items. integration node, splitInBatches. 2 incoming and 1 outgoing connections.STEP 04Loop Over ItemsINTEGRATIONSPLITINBATCHES2 IN / 1 OUTDelete old embeddings if exist. integration node, supabase. 1 incoming and 1 outgoing connections.STEP 05Delete old embeddings if …INTEGRATIONSUPABASE1 IN / 1 OUTLimit. integration node, limit. 1 incoming and 1 outgoing connections.STEP 06LimitINTEGRATIONLIMIT1 IN / 1 OUTGet page blocks. Notion node, notion. 1 incoming and 1 outgoing connections.STEP 07Get page blocksNOTIONNOTION1 IN / 1 OUTConcatenate to single string. transform node, summarize. 1 incoming and 1 outgoing connections.STEP 08Concatenate to single str…TRANSFORMSUMMARIZE1 IN / 1 OUTSupabase Vector Store. ai node, vectorStoreSupabase. 3 incoming and 1 outgoing connections.STEP 09Supabase Vector StoreAIVECTORSTORESUPABASE3 IN / 1 OUTLimit1. integration node, limit. 1 incoming and 1 outgoing connections.OUTCOMELimit1INTEGRATIONLIMIT1 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTVector Store Retriever. ai node, retrieverVectorStore. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Vector Store RetrieverAIRETRIEVERVECTORSTORE1 IN / 1 OUTDefault Data Loader. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Default Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTEmbeddings OpenAI. OpenAI node, embeddingsOpenAi. 0 incoming and 2 outgoing connections.DEPENDENCY · DEPTH 1Embeddings OpenAIOPENAIEMBEDDINGSOPENAI0 IN / 2 OUTToken Splitter. ai node, textSplitterTokenSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Token SplitterAITEXTSPLITTERTOKENSPLITT0 IN / 1 OUTSupabase Vector Store1. ai node, vectorStoreSupabase. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Supabase Vector Store1AIVECTORSTORESUPABASE1 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.19 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

12 Execution Links7 Support Dependencies

  1. Start

    Schedule Trigger

    Trigger

    Notion Trigger

    Trigger

    When chat message received

    Trigger

  2. Step 2

    Get updated pages

    Integration

    Question and Answer Chain

    AI reasoning

  3. Step 3

    Input Reference

    Integration

  4. Step 4

    Loop Over Items

    Integration

  5. Step 5

    Delete old embeddings if exist

    Integration

  6. Step 6

    Limit

    Integration

  7. Step 7

    Get page blocks

    Integration

  8. Step 8

    Concatenate to single string

    Transform

  9. Step 9

    Supabase Vector Store

    AI reasoning

  10. Outcome

    Limit1

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

6 nodes

  • Default Data Loader

    AI reasoning dependency

  • Token Splitter

    AI reasoning dependency

  • OpenAI Chat Model

    AI reasoning dependency

  • Vector Store Retriever

    AI reasoning dependency

  • Supabase Vector Store1

    AI reasoning dependency

  • Embeddings OpenAI

    AI reasoning dependency

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