Create Accounts in CRM Action Node

The Create Accounts in CRM action node creates net-new accounts in your CRM. It currently supports the following CRMs:

• Salesforce

• HubSpot

• Microsoft Dynamics

Account identification and duplication rules

6sense identifies accounts by name, country and domain. This means that 6sense considers “XYZCorp, USA” and “XYZCorp, Canada” to be separate accounts. Therefore, if you have one name/country/domain in your CRM, and the new account from 6sense uses another, 6sense creates the other. However, you may want to treat both of these accounts as the same account in your CRM; in which case you can set custom duplicate prevention rules in 6sense so that 6sense does not create a new account if you want to use the existing account. To set up duplication prevention rules, see Custom Match Rules.

Create Accounts in CRM action node requirements

• You cannot use the same label text on more than one action node in a workflow.

Dependencies

• Integration with the 3rd party systems involved in the workflow.

• Pre-configured custom match rules for account creation, to prevent duplicates.

• A pre-configured mapping profile that includes the name, display domain, and country fields.

• 6sense credits allocated to the Audience Workflows application. See Distribute Credits Between Applications.

Properties

• Node Name: A brief description that displays on the node’s icon.

• Description: A lengthier description of what the node does.

• The node uses custom match rules to avoid creating duplicates. Edit them if needed.

• Select the Mapping Profile.

  • You can override which fields to enrich when creating an account for this node only.

• For Advanced Options, you can set the batch size per API call. 6sense sets a default that varies depending on the CRM. Reducing the batch size may inversely affect the number of API calls. For example, decreasing the batch size from 200 to 50 results in 4x more API calls. The smaller the batch size, the longer the processing times. Changes to this setting take effect the next time the action node runs.

  
  Document changelog

  Aug 12 2026: Reorganized action node pages