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

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.

6

Nodes

6

Links

1

Run groups

Connected tools

4 integrations

  • Google Sheets
  • Gmail
  • Slack
  • TwentyCRM

Canvas controls

Fit wide systems, then zoom into any run group.

TwentyCRM Event Notifications Workflow execution lanes1 run groups containing 6 workflow nodes and 6 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.on new twentycrm event. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTon new twentycrm eventTRIGGERWEBHOOK0 IN / 1 OUTfilter required data #eventType mandatory. transform node, set. 1 incoming and 2 outgoing connections.STEP 02filter required data #eve…TRANSFORMSET1 IN / 2 OUTevents log. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 03events logGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTmessage channel evaluation. decision node, if. 2 incoming and 2 outgoing connections.STEP 04message channel evaluationDECISIONIF2 IN / 2 OUTemail channel for delete eventType. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMEemail channel for delete …GMAILGMAIL1 IN / 0 OUTmessage channel for all other eventTypes. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMEmessage channel for all o…SLACKSLACK1 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.6 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

on new twentycrm event

6 Execution Links

  1. Start

    on new twentycrm event

    Trigger

  2. Step 2

    filter required data #eventType mandatory

    Transform

  3. Step 3

    events log

    Integration

  4. Step 4

    message channel evaluation

    Decision

  5. Outcome

    email channel for delete eventType

    Integration

    message channel for all other eventTypes

    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.

Create a build planReturn to the atlas