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

Automated Slack to Google Calendar Event Manager

Automated Slack to Google Calendar Event Manager is a 22-node automation blueprint connecting Slack, Google Calendar, OpenAI. Inspect its trigger, execution graph, branches, and implementation requirements.

SlackGoogle CalendarOpenAILangchainSerpAPIWikipedia

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.

22

Nodes

21

Links

1

Run groups

Connected tools

6 integrations

  • Slack
  • Google Calendar
  • OpenAI
  • LangChain
  • SerpAPI
  • Wikipedia

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Slack to Google Calendar Event Manager execution lanes1 run groups containing 22 workflow nodes and 21 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 OUTSearch for Invite Requests. Slack node, slack. 1 incoming and 1 outgoing connections.STEP 02Search for Invite RequestsSLACKSLACK1 IN / 1 OUTGet Invite Replies. Slack node, slack. 1 incoming and 1 outgoing connections.STEP 03Get Invite RepliesSLACKSLACK1 IN / 1 OUTGet Existing Invite EventID. transform node, code. 1 incoming and 1 outgoing connections.STEP 04Get Existing Invite EventIDTRANSFORMCODE1 IN / 1 OUTShould Create Event?. decision node, if. 1 incoming and 2 outgoing connections.STEP 05Should Create Event?DECISIONIF1 IN / 2 OUTCalendar Event Booking Agent. ai node, agent. 5 incoming and 1 outgoing connections.STEP 06Calendar Event Booking Ag…AIAGENT5 IN / 1 OUTGet Old EventId. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Get Old EventIdTRANSFORMSET1 IN / 1 OUTCreate Event. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 07Create EventGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTGet Event Details. Google Calendar node, googleCalendar. 1 incoming and 1 outgoing connections.STEP 07Get Event DetailsGOOGLE CALENDARGOOGLECALENDAR1 IN / 1 OUTReply Invite with EventId. Slack node, slack. 1 incoming and 0 outgoing connections.STEP 08Reply Invite with EventIdSLACKSLACK1 IN / 0 OUTGet Invite Reactions. Slack node, slack. 1 incoming and 1 outgoing connections.STEP 08Get Invite ReactionsSLACKSLACK1 IN / 1 OUTExtract Invite Reactions. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 09Extract Invite ReactionsTRANSFORMSPLITOUT1 IN / 1 OUTIs Attending. decision node, filter. 1 incoming and 1 outgoing connections.STEP 10Is AttendingDECISIONFILTER1 IN / 1 OUTFor Each User ID.... transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 11For Each User ID...TRANSFORMSPLITOUT1 IN / 1 OUTGet User. Slack node, slack. 1 incoming and 1 outgoing connections.STEP 12Get UserSLACKSLACK1 IN / 1 OUTShould Add Attendee?. decision node, if. 1 incoming and 1 outgoing connections.STEP 13Should Add Attendee?DECISIONIF1 IN / 1 OUTGet User Email. transform node, set. 1 incoming and 1 outgoing connections.STEP 14Get User EmailTRANSFORMSET1 IN / 1 OUTAdd Attendee to Event. Google Calendar node, googleCalendar. 1 incoming and 0 outgoing connections.OUTCOMEAdd Attendee to EventGOOGLE CALENDARGOOGLECALENDAR1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTSerpAPI. ai node, toolSerpApi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1SerpAPIAITOOLSERPAPI0 IN / 1 OUTWikipedia. ai node, toolWikipedia. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1WikipediaAITOOLWIKIPEDIA0 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.22 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

17 Execution Links4 Support Dependencies

  1. Start

    Schedule Trigger

    Trigger

  2. Step 2

    Search for Invite Requests

    Integration

  3. Step 3

    Get Invite Replies

    Integration

  4. Step 4

    Get Existing Invite EventID

    Transform

  5. Step 5

    Should Create Event?

    Decision

  6. Step 6

    Calendar Event Booking Agent

    AI reasoning

    Get Old EventId

    Transform

  7. Step 7

    Create Event

    Integration

    Get Event Details

    Integration

  8. Step 8

    Reply Invite with EventId

    Integration

    Get Invite Reactions

    Integration

  9. Step 9

    Extract Invite Reactions

    Transform

  10. Step 10

    Is Attending

    Decision

  11. Step 11

    For Each User ID...

    Transform

  12. Step 12

    Get User

    Integration

  13. Step 13

    Should Add Attendee?

    Decision

  14. Step 14

    Get User Email

    Transform

  15. Outcome

    Add Attendee to Event

    Integration

Attached dependencies

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

4 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • Structured Output Parser

    AI reasoning dependency

  • SerpAPI

    AI reasoning dependency

  • Wikipedia

    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