Skip to Workflow Atlas
Event-Driven AutomationAI systemIntermediate

Automated Training Feedback Workflow

Automated Training Feedback Workflow is a 12-node automation blueprint connecting Airtable, LinkedIn, SMTP Email. 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.

12

Nodes

13

Links

2

Run groups

Connected tools

3 integrations

  • Airtable
  • LinkedIn
  • SMTP Email

Canvas controls

Fit wide systems, then zoom into any run group.

Automated Training Feedback Workflow execution lanes2 run groups containing 12 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.Webhook - Action Task Poor. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhook - Action Task PoorTRIGGERWEBHOOK0 IN / 1 OUTSwitch1. decision node, switch. 1 incoming and 2 outgoing connections.STEP 02Switch1DECISIONSWITCH1 IN / 2 OUTSend Email after WebHook. integration node, emailSend. 1 incoming and 0 outgoing connections.OUTCOMESend Email after WebHookINTEGRATIONEMAILSEND1 IN / 0 OUTCall Usertask - Create task. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMECall Usertask - Create taskINTEGRATIONHTTPREQUEST1 IN / 0 OUTAirtable Trigger. Airtable node, airtableTrigger. 0 incoming and 1 outgoing connections.STARTAirtable TriggerAIRTABLEAIRTABLETRIGGER0 IN / 1 OUTSwitch. decision node, switch. 1 incoming and 5 outgoing connections.STEP 02SwitchDECISIONSWITCH1 IN / 5 OUTCall Usertask - Create Task - Dissatisfaction. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Call Usertask - Create Ta…INTEGRATIONHTTPREQUEST1 IN / 1 OUTCall Usertask - Create Task - Pair and good. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 03Call Usertask - Create Ta…INTEGRATIONHTTPREQUEST2 IN / 1 OUTLinkedIn. integration node, linkedIn. 2 incoming and 1 outgoing connections.STEP 03LinkedInINTEGRATIONLINKEDIN2 IN / 1 OUTCall Usertask - Detail Task. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 04Call Usertask - Detail TaskINTEGRATIONHTTPREQUEST2 IN / 1 OUTSend Email - Information for marcketing. integration node, emailSend. 1 incoming and 0 outgoing connections.STEP 04Send Email - Information …INTEGRATIONEMAILSEND1 IN / 0 OUTPoor - Send Email. integration node, emailSend. 1 incoming and 0 outgoing connections.OUTCOMEPoor - Send EmailINTEGRATIONEMAILSEND1 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

Webhook - Action Task Poor

3 Execution Links
  1. Start

    Webhook - Action Task Poor

    Trigger

  2. Step 2

    Switch1

    Decision

  3. Outcome

    Send Email after WebHook

    Integration

    Call Usertask - Create task

    Integration

02

Run Group

Airtable Trigger

10 Execution Links
  1. Start

    Airtable Trigger

    Trigger

  2. Step 2

    Switch

    Decision

  3. Step 3

    Call Usertask - Create Task - Dissatisfaction

    Integration

    Call Usertask - Create Task - Pair and good

    Integration

    LinkedIn

    Integration

  4. Step 4

    Call Usertask - Detail Task

    Integration

    Send Email - Information for marcketing

    Integration

  5. Outcome

    Poor - Send Email

    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.