Salesforce trigger
The Salesforce trigger lets you listen to either Change Data Capture (CDC) or Enterprise Messaging Platform events. With this trigger, you can start your integration based on any of the CDC events (Create, Update, Delete, or Undelete) or the platform events in your Salesforce instance.
For more information, see the following tutorials:
- To use Application Integration to automate the business process flow of routing and assigning a Salesforce customer case, see the Automate Salesforce case routing assignments tutorial.
- To use Application Integration to automate an order management flow between a customer relationship management (CRM) application and an enterprise resource planning (ERP) application, see the Automate Salesforce opportunity to BigQuery order tutorial.
- To use the Salesforce trigger to invoke an integration in Application Integration for a Salesforce Change Data Capture (CDC) event, see the Invoke an integration for a Salesforce Change Data Capture (CDC) event tutorial.
Before you begin
This section outlines the steps required to connect and configure a Salesforce instance to use Change Data Capture (CDC) or Platform events to stream changes to your Application Integration in a pub/sub manner. The following steps must be completed before configuring any Salesforce-related task or trigger in Application Integration:
- Set up an integration user
- Configure a permission set
- Set up a security token
- Create a connected app
Set up an integration user
Set up an integration user with the following steps:
- Log in to your Salesforce instance with your
sysadmincredentials. - Click the Gear icon and then select Setup, as shown in the image below:


- Click Users > Users from the Administration menu.
- From the Users pane, select the New User button.
- In the User Edit dialog, fill in the following details:
- First Name: First name of the integration user.
- Last Name: Last name of the integration user.
- Email Address: Email for the integration user. Ideally, this should be a group email.
- Username: User name that complies with any org-level naming conventions.
If you are creating a new integration user, use the following format:
EMAIL.SALESFORCE_ORG_NAME.SANDBOX_NAMEIf you have an existing integration user, confirm that the username is entered here.
- Role: Select from the dropdown of options.
- User License: Enter
Salesforceor, if using a trial org, enterSalesforce Platform. - Profile: Select the permissions profile for integration users from the dropdown.
We recommend assigning a profile with no permissions, to protect your integration user Salesforce access from unauthorized usage.
- Click Save.
- To update the password for the new integration user, follow these steps:
- Click the Reset password(s) button on the Users pane. A password reset email is sent to the email address associated with the user.
- Follow the reset password flow from the email account. Take note of the new password, as you will need it for a later step.
Configure a Permission Set
If you have already have access to a Permission Set that is appropriate for an integration user, you can skip this step and proceed to Set up a security token. Otherwise, follow these steps to configure a Permission Set for the integration user and the Salesforce object.
To configure a Permission Set for the integration user:
- From the Setup menu, click Users > Permission Sets.
- In the Permission Sets pane, click the New button.
- In the Permission Sets dialog, enter the following details:
- Label: Enter a name for the Permission Set.
- License: Select Salesforce from the License dropdown.
- Click Save.
- From the list of System setting options, scroll down and select System Permissions
- On the System Permissions page, click the Edit button.
- Scroll down the list of available permissions and select the API Enabled checkbox.
The Api Only User permission is also required, but cannot be enabled until the required security token is reset. This permission is added in a later step.
- (Optional) Scroll and select Modify All Data and View All Data, if applicable. These permissions are not required, but can be helpful if you want to automatically give the integration user access to new objects. We recommend only enabling these permissions for testing in a sandbox.
- Scroll to the top of the permissions list and click Save.