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

Morning Meeting Insights & Notifications

Morning Meeting Insights & Notifications is a 18-node automation blueprint connecting Google Calendar, Clearbit, LinkedIn API. Inspect its trigger, execution graph, branches, and implementation requirements.

Google CalendarClearbitLinkedIn APITwitter APIOpenAIGmail

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.

18

Nodes

19

Links

1

Run groups

Connected tools

6 integrations

  • Google Calendar
  • Clearbit
  • LinkedIn API
  • Twitter API
  • OpenAI
  • Gmail

Canvas controls

Fit wide systems, then zoom into any run group.

Morning Meeting Insights & Notifications execution lanes1 run groups containing 18 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.Every morning @ 7. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTEvery morning @ 7TRIGGERSCHEDULETRIGGER0 IN / 1 OUTSetup. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SetupTRANSFORMSET1 IN / 1 OUTGet meetings for today. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 03Get meetings for todayGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTGet attendees email domains. transform node, set. 1 incoming and 1 outgoing connections.STEP 04Get attendees email domainsTRANSFORMSET1 IN / 1 OUTSplit Out. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 05Split OutTRANSFORMSPLITOUT1 IN / 1 OUTKeep only ones with the domain. decision node, filter. 1 incoming and 1 outgoing connections.STEP 06Keep only ones with the d…DECISIONFILTER1 IN / 1 OUTEnrich attendee company. integration node, clearbit. 1 incoming and 1 outgoing connections.STEP 07Enrich attendee companyINTEGRATIONCLEARBIT1 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 2 outgoing connections.STEP 08SwitchDECISIONSWITCH1 IN / 2 OUTGet recent LinkedIn posts. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 09Get recent LinkedIn postsINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet latest tweets. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 09Get latest tweetsINTEGRATIONHTTPREQUEST1 IN / 1 OUTExtract important data. transform node, set. 1 incoming and 1 outgoing connections.STEP 10Extract important dataTRANSFORMSET1 IN / 1 OUTExtract important data again. transform node, set. 1 incoming and 1 outgoing connections.STEP 10Extract important data ag…TRANSFORMSET1 IN / 1 OUTCombine all activity for a company. decision node, merge. 2 incoming and 2 outgoing connections.STEP 11Combine all activity for …DECISIONMERGE2 IN / 2 OUTAsk AI to summerize. OpenAI node, openAi. 1 incoming and 1 outgoing connections.STEP 12Ask AI to summerizeOPENAIOPENAI1 IN / 1 OUTExtract data for email. transform node, set. 1 incoming and 1 outgoing connections.STEP 12Extract data for emailTRANSFORMSET1 IN / 1 OUTWrap everything together. decision node, merge. 2 incoming and 1 outgoing connections.STEP 13Wrap everything togetherDECISIONMERGE2 IN / 1 OUTPrepare email template. integration node, html. 1 incoming and 1 outgoing connections.STEP 14Prepare email templateINTEGRATIONHTML1 IN / 1 OUTGmail. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMEGmailGMAILGMAIL1 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.18 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

Every morning @ 7

19 Execution Links

  1. Start

    Every morning @ 7

    Trigger

  2. Step 2

    Setup

    Transform

  3. Step 3

    Get meetings for today

    Integration

  4. Step 4

    Get attendees email domains

    Transform

  5. Step 5

    Split Out

    Transform

  6. Step 6

    Keep only ones with the domain

    Decision

  7. Step 7

    Enrich attendee company

    Integration

  8. Step 8

    Switch

    Decision

  9. Step 9

    Get recent LinkedIn posts

    Integration

    Get latest tweets

    Integration

  10. Step 10

    Extract important data

    Transform

    Extract important data again

    Transform

  11. Step 11

    Combine all activity for a company

    Decision

  12. Step 12

    Ask AI to summerize

    AI reasoning

    Extract data for email

    Transform

  13. Step 13

    Wrap everything together

    Decision

  14. Step 14

    Prepare email template

    Integration

  15. Outcome

    Gmail

    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