Salesforce Component

A component enables you to manage your organization’s sales, marketing and customer support assets, far beyond email addresses and phone numbers.

---

A component enables you to manage your organization’s sales, marketing and customer support assets, far beyond email addresses and phone numbers.

Please Note: The component works with the Salesforce API. This means you must make sure your Salesforce edition has API Access enabled. To check which editions have API access see the Salesforce editions with API Access document. If your edition has no API Access by default this component will not work for you..

API version

The component uses Salesforce - API Version 46.0 by defaults but can be overwritten by the environment variable SALESFORCE_API_VERSION.

Please note: Deprecated Actions and Triggers - API Version 25.0.

Environment variables

Please Note: From the platform version 20.51 we deprecated the component LOG_LEVEL environment variable. Now you can control logging level per each step of the flow.

Technical Notes

The technical notes page gives some technical details about Salesforce component like changelog and the completeness matrix.

Credentials

Authentication occurs via OAuth 2.0.

In order to make OAuth work, you need a new App in your Salesforce. During app creation process you will be asked to specify the callback URL, to process OAuth authentication via elastic.io platform your callback URL should be /callback/oauth2.

More information you can find here.

Please note: Salesforce migration or any changes that affect endpoints, single sign-on (SSO), OAuth and JSON web tokens (JWT), and other connections can lead to unpredictable behavior that can cause authentication issues. To avoid this after making changes you need to create new credentials and authenticate again, once this is done the old ones can be safely removed from the platform.

Warning: To maintain a smooth experience, we recommend reusing stored credentials where possible. Duplicating secrets across OAuth clients can result in errors and complications.

Credentials creation

During credentials creation you would need to:

• select existing Auth-Client from drop-down list Choose Auth Client or create the new one.

For creating Auth Client you should specify following fields:

• fill field Name Your Credential.
• click on Authenticate button - if you have not logged in Salesforce before then log in by entering data in the login window that appears.
• click on Verify button for verifying your credentials.
• click on Save button for saving your credentials.

Here you can see how to select an existing client:

For more information pleas read our Creating OAuth App for Salesforce article.

Please Note: When you deploy the Salesforce component separately into a dedicated tenant or into your developer team it can not use the OAuth App specifically created for our main AVA tenant. For this purposes you must create a different OAuth App and add the required environment variables to the component setup.

Triggers

Salesforce component includes the following triggers:

1. Query trigger Continuously runs the same SOQL query and emits results one-by-one. Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information.
2. Get New and Updated Objects Polling trigger Polls existing and updated objects. You can select any custom or built-in object for your Salesforce instance.
3. Subscribe to platform events This trigger will subscribe for any platform Event using Salesforce streaming API. Realtime flows only.
4. Subscribe to PubSub This trigger will subscribe for any platform Event using Pub/Sub API.

You can find information on deprecated triggers here.

Actions

Use this list to navigate to the action you seek.

1. Query action Executing a SOQL query that may return many objects. Each resulting object is emitted one-by-one. Use the Salesforce Object Query Language (SOQL) to search your organization’s Salesforce data for specific information.
2. Create Object action Creates a new Selected Object. Action creates a single object.
3. Delete Object action Deletes an object by a selected field. One can filter by either unique fields or all fields of that object.
4. Upsert Object action Creates or Updates Selected Object. Action creates a single object.
5. Lookup Object action(at most 1) Lookup an object by a selected field. Action creates a single object.
6. Lookup Objects action Lookup a list of objects satisfying specified criteria.
7. Bulk Create/Update/Delete/Upsert action Bulk API provides a simple interface for quickly loading large amounts of data from CSV file into Salesforce.
8. Bulk Query action Fetches records to a CSV file.
9. Raw Request action Make raw request.

You can find information on deprecated actions here.

Permissions

By default, certain user profiles in Salesforce have disabled permissions. In order to ensure the visibility of an object in the metadata of component’s actions and triggers, it is necessary to enable the required standard object permissions.

To enable these permissions, please follow these steps:

1. Go to the Salesforce Setup page.
2. Navigate to the “ADMINISTRATION” section.
3. Under “Profiles”, select the profile that needs modification.
4. Click on the “Edit” button to proceed.

Once you are on the profile editing page, ensure that all the required standard object permissions are enabled. For instance, if you intend to utilize the Get New and Updated Objects Polling trigger, the following permissions are necessary: Read, Create, and Edit.

Carefully review the permissions and make any necessary adjustments to enable the required access.

Known limitations

Attachments mechanism doesn’t work with Local Agent Installation.