Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
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.

Google CalendarGmailCustom API

Interactive system map

Execution flows, separated by connected path.

Each horizontal lane is one connected flow. Solid lines show runtime execution; dashed lines show AI, model, memory, or tool dependencies.

14

Nodes

15

Links

1

Flows

Connected tools

3 integrations

  • Google Calendar
  • Gmail
  • Custom API
Automated Meeting Insights and Reporting execution lanes1 connected flows containing 14 workflow nodes and 15 visible links. Solid lines are execution links and dashed lines are support dependencies. Focus any node to inspect its immediate path.Google Calendar Trigger. Google Calendar node, googleCalendarTrigger. 0 incoming and 1 outgoing connections.Google Calendar TriggerGOOGLE CALENDARGOOGLECALENDARTRIGGER0 IN / 1 OUTEdit Fields. transform node, set. 1 incoming and 1 outgoing connections.Edit FieldsTRANSFORMSET1 IN / 1 OUTSplit Out Attendees. transform node, splitOut. 1 incoming and 1 outgoing connections.Split Out AttendeesTRANSFORMSPLITOUT1 IN / 1 OUTFilter Out Myself. decision node, filter. 1 incoming and 1 outgoing connections.Filter Out MyselfDECISIONFILTER1 IN / 1 OUTFor Each Attendee. integration node, splitInBatches. 2 incoming and 2 outgoing connections.For Each AttendeeINTEGRATIONSPLITINBATCHES2 IN / 2 OUTCombine All Research. transform node, aggregate. 1 incoming and 1 outgoing connections.Combine All ResearchTRANSFORMAGGREGATE1 IN / 1 OUTIs Company Email?. decision node, if. 1 incoming and 2 outgoing connections.Is Company Email?DECISIONIF1 IN / 2 OUTWrite HTML. integration node, markdown. 1 incoming and 1 outgoing connections.Write HTMLINTEGRATIONMARKDOWN1 IN / 1 OUTCompany Prompt. transform node, set. 1 incoming and 1 outgoing connections.Company PromptTRANSFORMSET1 IN / 1 OUTSend Report. Gmail node, gmail. 1 incoming and 0 outgoing connections.Send ReportGMAILGMAIL1 IN / 0 OUTResearch Company. integration node, httpRequest. 1 incoming and 1 outgoing connections.Research CompanyINTEGRATIONHTTPREQUEST1 IN / 1 OUTPerson Prompt. transform node, set. 2 incoming and 1 outgoing connections.Person PromptTRANSFORMSET2 IN / 1 OUTResearch Person. integration node, httpRequest. 1 incoming and 1 outgoing connections.Research PersonINTEGRATIONHTTPREQUEST1 IN / 1 OUTCollect Fields. transform node, set. 1 incoming and 1 outgoing connections.Collect FieldsTRANSFORMSET1 IN / 1 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

Execution linkSupport dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.14 connected nodesEnter or click to lock · Escape to clear

Execution breakdown

Follow each connected flow from start to outcome.

The readable view below uses the same graph relationships as the interactive map. Each row is a connected flow; columns advance only when an actual link connects the nodes.

01

Connected Flow

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.

Create a build planReturn to the atlas