Skip to Workflow Atlas
ETL PipelineIntermediate

Salesforce & Google Sheets Account Sync

Salesforce & Google Sheets Account Sync is a 12-node automation blueprint connecting Google Sheets, Salesforce. 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

15

Links

1

Run groups

Connected tools

2 integrations

  • Google Sheets
  • Salesforce

Canvas controls

Fit wide systems, then zoom into any run group.

Salesforce & Google Sheets Account Sync execution lanes1 run groups containing 12 workflow nodes and 15 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 clicking 'execute'. trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTOn clicking 'execute'TRIGGERMANUALTRIGGER0 IN / 1 OUTRead Google Sheet. Google Sheets node, googleSheets. 1 incoming and 3 outgoing connections.STEP 02Read Google SheetGOOGLE SHEETSGOOGLESHEETS1 IN / 3 OUTSearch Salesforce accounts. integration node, salesforce. 1 incoming and 2 outgoing connections.STEP 03Search Salesforce accountsINTEGRATIONSALESFORCE1 IN / 2 OUTKeep new companies. decision node, merge. 2 incoming and 2 outgoing connections.STEP 04Keep new companiesDECISIONMERGE2 IN / 2 OUTMerge existing account data. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04Merge existing account dataDECISIONMERGE2 IN / 1 OUTRemove duplicate companies. transform node, itemLists. 1 incoming and 1 outgoing connections.STEP 05Remove duplicate companiesTRANSFORMITEMLISTS1 IN / 1 OUTAccount found?. decision node, if. 1 incoming and 1 outgoing connections.STEP 05Account found?DECISIONIF1 IN / 1 OUTCreate Salesforce account. integration node, salesforce. 1 incoming and 1 outgoing connections.STEP 06Create Salesforce accountINTEGRATIONSALESFORCE1 IN / 1 OUTSet Account ID for existing accounts. integration node, renameKeys. 1 incoming and 1 outgoing connections.STEP 06Set Account ID for existi…INTEGRATIONRENAMEKEYS1 IN / 1 OUTSet new account name. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Set new account nameTRANSFORMSET1 IN / 1 OUTRetrieve new company contacts. decision node, merge. 2 incoming and 1 outgoing connections.STEP 08Retrieve new company cont…DECISIONMERGE2 IN / 1 OUTCreate Salesforce contact. integration node, salesforce. 2 incoming and 0 outgoing connections.OUTCOMECreate Salesforce contactINTEGRATIONSALESFORCE2 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

On clicking 'execute'

15 Execution Links
  1. Start

    On clicking 'execute'

    Trigger

  2. Step 2

    Read Google Sheet

    Integration

  3. Step 3

    Search Salesforce accounts

    Integration

  4. Step 4

    Keep new companies

    Decision

    Merge existing account data

    Decision

  5. Step 5

    Remove duplicate companies

    Transform

    Account found?

    Decision

  6. Step 6

    Create Salesforce account

    Integration

    Set Account ID for existing accounts

    Integration

  7. Step 7

    Set new account name

    Transform

  8. Step 8

    Retrieve new company contacts

    Decision

  9. Outcome

    Create Salesforce contact

    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.