Templates / Sales / RevOps | Sync SFDC Accounts > Netsuite Customers
RevOps | Sync SFDC Accounts > Netsuite Customers
This integration is a live sync between Accounts in Salesforce and Customers in Netsuite.
Once enabled, any time a new account is created or updated in SFDC it will be synced to Netsuite.
The following connectors are used in this template. This is mostly provided for reference only - there is no need to read through the linked connector pages. All you need to know for this template is explained here, although you will likely need to look up service authentication instructions:
The following screenshot illustrates the stages in the process of syncing SFDC Accounts > Netsuite customers.
It works in several stages.
Section 1 The workflow is triggered by notifications from Salesforce when an account is either created or updated. It then:
- Takes the ID that is passed via the webhook and looks up the account’s information in Salesforce.
- Checks to see if the account status is “Active” to prevent deactivated accounts from updating Netsuite.
Section 2 Validates the domain of the account. Netsuite requires that all domains have proper addresses. If it is missing, the workflow automatically adds http:// or https:// to the domain to prevent Netsuite from throwing an error.
Section 3 Checks Netsuite to see if an account has a match. If a match is found, then Netsuite updates that customer. If no match is found, Netsuite creates a new customer.
This workflow assumes the following:
(Optional but strongly recommended) You have added a custom field to Netsuite to hold the Salesforce Account ID of the customer
To configure the workflow for your own use:
For educational purposes, the rest of this page will take you through how the workflow template is built to achieve the desired results.
This will help deepen your understanding of Tray.io and will give you the power to maintain and edit your workflow as necessary.
You will see that the steps below have both a step name (Get Account Information, Check URL etc.) and a programmatic name (salesforce-1 storage-2 text-helpers-2 etc.)
The programmatic name is what enables the use of jsonpaths such as
$.steps.storage-2.result to pull data from previous steps in your workflow.
Please note that the numbering of these may appear to be out of sequence in your workflow. This is because your workflow may contain nested loops, multiple branches, booleans etc. which means that a strict top-to-bottom sequence of steps does not always occur.
Steps may also be moved or deleted after they have been created.