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

AirtableLinkedInSMTP Email

Interactive system map

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

12

Nodes

13

Edges

6

Zones

System stack

3 integrations

  • Airtable
  • LinkedIn
  • SMTP Email
Automated Training Feedback Workflow interactive execution graphStructural view of 12 workflow nodes and 13 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.Webhook - Action Task Poor. trigger node, webhook. 0 incoming and 1 outgoing connections.Webhook - Action Task PoorTRIGGERWEBHOOK0 IN / 1 OUTAirtable Trigger. Airtable node, airtableTrigger. 0 incoming and 1 outgoing connections.Airtable TriggerAIRTABLEAIRTABLETRIGGER0 IN / 1 OUTSwitch1. decision node, switch. 1 incoming and 2 outgoing connections.Switch1DECISIONSWITCH1 IN / 2 OUTSwitch. decision node, switch. 1 incoming and 5 outgoing connections.SwitchDECISIONSWITCH1 IN / 5 OUTSend Email after WebHook. integration node, emailSend. 1 incoming and 0 outgoing connections.Send Email after WebHookINTEGRATIONEMAILSEND1 IN / 0 OUTCall Usertask - Create task. integration node, httpRequest. 1 incoming and 0 outgoing connections.Call Usertask - Create taskINTEGRATIONHTTPREQUEST1 IN / 0 OUTCall Usertask - Create Task - Dissatisfaction. integration node, httpRequest. 1 incoming and 1 outgoing connections.Call Usertask - Create Ta…INTEGRATIONHTTPREQUEST1 IN / 1 OUTCall Usertask - Create Task - Pair and good. integration node, httpRequest. 2 incoming and 1 outgoing connections.Call Usertask - Create Ta…INTEGRATIONHTTPREQUEST2 IN / 1 OUTLinkedIn. integration node, linkedIn. 2 incoming and 1 outgoing connections.LinkedInINTEGRATIONLINKEDIN2 IN / 1 OUTCall Usertask - Detail Task. integration node, httpRequest. 2 incoming and 1 outgoing connections.Call Usertask - Detail TaskINTEGRATIONHTTPREQUEST2 IN / 1 OUTSend Email - Information for marcketing. integration node, emailSend. 1 incoming and 0 outgoing connections.Send Email - Information …INTEGRATIONEMAILSEND1 IN / 0 OUTPoor - Send Email. integration node, emailSend. 1 incoming and 0 outgoing connections.Poor - Send EmailINTEGRATIONEMAILSEND1 IN / 0 OUT

Signal inspector

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

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.12 connected nodesEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The workflow is grouped into operational zones, then reviewed for the controls needed to adapt the pattern safely.

01

Entry signals

2 nodes

Events, schedules, and unconnected roots that can start an execution.

Airtable Trigger

Trigger

Webhook - Action Task Poor

Trigger

02

Data & operations

4 nodes

Transformations and external-system actions that move the work forward.

LinkedIn

Integration

Call Usertask - Create Task - Pair and good

Integration

Call Usertask - Detail Task

Integration

Call Usertask - Create Task - Dissatisfaction

Integration

03

Intelligence & routing

2 nodes

Model calls and control points that interpret, branch, or govern the run.

Switch1

Decision

Switch

Decision

04

Terminal actions

4 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Poor - Send Email

Integration

Call Usertask - Create task

Integration

Send Email after WebHook

Integration

Send Email - Information for marcketing

Integration

Adjacent systems

Keep tracing the stack.

Related workflows share tools and similar system patterns.

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