Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
Event-Driven AutomationAI systemIntermediate

TwentyCRM Event Notifications Workflow

TwentyCRM Event Notifications Workflow is a 6-node automation blueprint connecting Google Sheets, Gmail, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

Google SheetsGmailSlackTwentyCRM

Live system map / verified archive

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.

6

Nodes

6

Edges

5

Zones

System stack

4 integrations

  • Google Sheets
  • Gmail
  • Slack
  • TwentyCRM
TwentyCRM Event Notifications Workflow interactive execution graphStructural view of 6 workflow nodes and 6 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.on new twentycrm event. trigger node, webhook. 0 incoming and 1 outgoing connections.on new twentycrm eventTRIGGERWEBHOOK0 IN / 1 OUTfilter required data #eventType mandatory. transform node, set. 1 incoming and 2 outgoing connections.filter required data #eve…TRANSFORMSET1 IN / 2 OUTevents log. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.events logGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTmessage channel evaluation. decision node, if. 2 incoming and 2 outgoing connections.message channel evaluationDECISIONIF2 IN / 2 OUTemail channel for delete eventType. Gmail node, gmail. 1 incoming and 0 outgoing connections.email channel for delete …GMAILGMAIL1 IN / 0 OUTmessage channel for all other eventTypes. Slack node, slack. 1 incoming and 0 outgoing connections.message channel for all o…SLACKSLACK1 IN / 0 OUT

Signal inspector

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

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 0ea00561c1951b50Enter or click to lock · Escape to clear

Structured review

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

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

1 node

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

on new twentycrm event

Trigger

02

Data & operations

2 nodes

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

filter required data #eventType mandatory

Transform

events log

Integration

03

Intelligence & routing

1 node

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

message channel evaluation

Decision

04

Terminal actions

2 nodes

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

email channel for delete eventType

Integration

message channel for all other eventTypes

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
prefix
Quality score
13 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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