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

Monthly Payroll Event Summary Automation

Monthly Payroll Event Summary Automation is a 13-node automation blueprint connecting Google Calendar, SMTP Email. Inspect its trigger, execution graph, branches, and implementation requirements.

Google CalendarSMTP Email

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.

13

Nodes

13

Links

1

Run groups

Connected tools

2 integrations

  • Google Calendar
  • SMTP Email

Canvas controls

Fit wide systems, then zoom into any run group.

Monthly Payroll Event Summary Automation execution lanes1 run groups containing 13 workflow nodes and 13 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.1st of Every month at 8am. integration node, cron. 0 incoming and 1 outgoing connections.START1st of Every month at 8amINTEGRATIONCRON0 IN / 1 OUTPrevious Month. integration node, dateTime. 1 incoming and 1 outgoing connections.STEP 02Previous MonthINTEGRATIONDATETIME1 IN / 1 OUTGet previous months events. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 03Get previous months eventsGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTCheck Summary for Illness or Holiday. decision node, switch. 1 incoming and 2 outgoing connections.STEP 04Check Summary for Illness…DECISIONSWITCH1 IN / 2 OUTHoliday. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 05HolidayINTEGRATIONNOOP1 IN / 1 OUTIllness. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 05IllnessINTEGRATIONNOOP1 IN / 1 OUTFilter Holiday Days. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Filter Holiday DaysTRANSFORMSET1 IN / 1 OUTFilter Illness Days. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Filter Illness DaysTRANSFORMSET1 IN / 1 OUTCombine Holiday Counts. transform node, code. 1 incoming and 1 outgoing connections.STEP 07Combine Holiday CountsTRANSFORMCODE1 IN / 1 OUTCombine Illness Counts. transform node, code. 1 incoming and 1 outgoing connections.STEP 07Combine Illness CountsTRANSFORMCODE1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 08MergeDECISIONMERGE2 IN / 1 OUTBuild the message to send. transform node, code. 1 incoming and 1 outgoing connections.STEP 09Build the message to sendTRANSFORMCODE1 IN / 1 OUTSend email to payroll. integration node, emailSend. 1 incoming and 0 outgoing connections.OUTCOMESend email to payrollINTEGRATIONEMAILSEND1 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.13 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

1st of Every month at 8am

13 Execution Links

  1. Start

    1st of Every month at 8am

    Integration

  2. Step 2

    Previous Month

    Integration

  3. Step 3

    Get previous months events

    Integration

  4. Step 4

    Check Summary for Illness or Holiday

    Decision

  5. Step 5

    Holiday

    Integration

    Illness

    Integration

  6. Step 6

    Filter Holiday Days

    Transform

    Filter Illness Days

    Transform

  7. Step 7

    Combine Holiday Counts

    Transform

    Combine Illness Counts

    Transform

  8. Step 8

    Merge

    Decision

  9. Step 9

    Build the message to send

    Transform

  10. Outcome

    Send email to payroll

    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