Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

Automated Meeting Insights and Reporting

Automated Meeting Insights and Reporting is a 14-node automation blueprint connecting Google Calendar, Gmail, Custom API. 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.

14

Nodes

15

Links

1

Run groups

Connected tools

3 integrations

  • Google Calendar
  • Gmail
  • Custom API

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Meeting Insights and Reporting execution lanes1 run groups containing 14 workflow nodes and 15 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.Google Calendar Trigger. Google Calendar node, googleCalendarTrigger. 0 incoming and 1 outgoing connections.STARTGoogle Calendar TriggerGOOGLE CALENDARGOOGLECALENDARTRIGGER0 IN / 1 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Edit FieldsTRANSFORMSET1 IN / 1 OUTSplit Out Attendees. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 03Split Out AttendeesTRANSFORMSPLITOUT1 IN / 1 OUTFilter Out Myself. decision node, filter. 1 incoming and 1 outgoing connections.STEP 04Filter Out MyselfDECISIONFILTER1 IN / 1 OUTFor Each Attendee. integration node, splitInBatches. 2 incoming and 2 outgoing connections.STEP 05For Each AttendeeINTEGRATIONSPLITINBATCHES2 IN / 2 OUTCombine All Research. transform node, aggregate. 1 incoming and 1 outgoing connections.STEP 06Combine All ResearchTRANSFORMAGGREGATE1 IN / 1 OUTIs Company Email?. decision node, if. 1 incoming and 2 outgoing connections.STEP 07Is Company Email?DECISIONIF1 IN / 2 OUTWrite HTML. integration node, markdown. 1 incoming and 1 outgoing connections.STEP 08Write HTMLINTEGRATIONMARKDOWN1 IN / 1 OUTCompany Prompt. transform node, set. 1 incoming and 1 outgoing connections.STEP 09Company PromptTRANSFORMSET1 IN / 1 OUTSend Report. Gmail node, gmail. 1 incoming and 0 outgoing connections.STEP 10Send ReportGMAILGMAIL1 IN / 0 OUTResearch Company. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 11Research CompanyINTEGRATIONHTTPREQUEST1 IN / 1 OUTPerson Prompt. transform node, set. 2 incoming and 1 outgoing connections.STEP 12Person PromptTRANSFORMSET2 IN / 1 OUTResearch Person. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 13Research PersonINTEGRATIONHTTPREQUEST1 IN / 1 OUTCollect Fields. transform node, set. 1 incoming and 1 outgoing connections.OUTCOMECollect FieldsTRANSFORMSET1 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.14 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

Google Calendar Trigger

15 Execution Links
  1. Start

    Google Calendar Trigger

    Trigger

  2. Step 2

    Edit Fields

    Transform

  3. Step 3

    Split Out Attendees

    Transform

  4. Step 4

    Filter Out Myself

    Decision

  5. Step 5

    For Each Attendee

    Integration

  6. Step 6

    Combine All Research

    Transform

  7. Step 7

    Is Company Email?

    Decision

  8. Step 8

    Write HTML

    Integration

  9. Step 9

    Company Prompt

    Transform

  10. Step 10

    Send Report

    Integration

  11. Step 11

    Research Company

    Integration

  12. Step 12

    Person Prompt

    Transform

  13. Step 13

    Research Person

    Integration

  14. Outcome

    Collect Fields

    Transform

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.