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

Acuity Scheduling Support Automation

Acuity Scheduling Support Automation is a 12-node automation blueprint connecting OpenAI, Acuity Scheduling. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIAcuity Scheduling

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.

12

Nodes

10

Links

2

Run groups

Connected tools

2 integrations

  • OpenAI
  • Acuity Scheduling

Canvas controls

Fit wide systems, then zoom into any run group.

Acuity Scheduling Support Automation execution lanes2 run groups containing 12 workflow nodes and 10 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.When chat message received. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTWhen chat message receivedTRIGGERCHATTRIGGER0 IN / 1 OUTAcuityScheduling Support Chatbot. ai node, agent. 4 incoming and 0 outgoing connections.OUTCOMEAcuityScheduling Support …AIAGENT4 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTSimple Memory. ai node, memoryBufferWindow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Simple MemoryAIMEMORYBUFFERWINDOW0 IN / 1 OUTKnowledgebase Tool. ai node, toolWorkflow. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Knowledgebase ToolAITOOLWORKFLOW0 IN / 1 OUTKnowledgeBase Tool Subworkflow. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTKnowledgeBase Tool Subwor…TRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTAcuity Support Search API. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Acuity Support Search APIINTEGRATIONHTTPREQUEST1 IN / 1 OUTHas Results?. decision node, if. 1 incoming and 2 outgoing connections.STEP 03Has Results?DECISIONIF1 IN / 2 OUTResults to Items. transform node, splitOut. 1 incoming and 1 outgoing connections.STEP 04Results to ItemsTRANSFORMSPLITOUT1 IN / 1 OUTEmpty Response. transform node, set. 1 incoming and 0 outgoing connections.STEP 04Empty ResponseTRANSFORMSET1 IN / 0 OUTExtract Relevant Fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 05Extract Relevant FieldsTRANSFORMSET1 IN / 1 OUTAggregate Response. transform node, aggregate. 1 incoming and 0 outgoing connections.OUTCOMEAggregate ResponseTRANSFORMAGGREGATE1 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.12 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

When chat message received

1 Execution Link3 Support Dependencies

  1. Start

    When chat message received

    Trigger

  2. Outcome

    AcuityScheduling Support Chatbot

    AI reasoning

Attached dependencies

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

3 nodes

  • OpenAI Chat Model

    AI reasoning dependency

  • Simple Memory

    AI reasoning dependency

  • Knowledgebase Tool

    AI reasoning dependency

02

Run Group

KnowledgeBase Tool Subworkflow

6 Execution Links

  1. Start

    KnowledgeBase Tool Subworkflow

    Trigger

  2. Step 2

    Acuity Support Search API

    Integration

  3. Step 3

    Has Results?

    Decision

  4. Step 4

    Results to Items

    Transform

    Empty Response

    Transform

  5. Step 5

    Extract Relevant Fields

    Transform

  6. Outcome

    Aggregate Response

    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