Actions for Salesforce #
- Send Data to Salesforce. Sends a custom set of Lucidum data to Salesforce.
Use Cases #
Below are the possible use cases for these actions:
-
If you want to run Lucidum “headless”, you can send relevant data to Salesforce on a regular schedule.
- You can send normalized, enriched Lucidum data to Salesforce to be indexed, searched, and analyzed.
Prerequisites #
To execute Salesforce actions, you must:
- Configure a Salesforce API connection beforehand. The required parameters are described in the instructions for creating a Salesforce connector in Lucidum https://lucidum.io/docs/salesforce/.
NOTE. The specified account should have read and write permissions.
Workflows #
- Creating a new Configuration and a new Action
- Cloning an Existing Action
- Creating a new Action from the Location Results page
- Editing a Configuration
- Editing an Action
- Viewing Information about an Action
Salesforce Configuration #
To create a configuration for Salesforce actions:
-
Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.
-
URL. The URL of the Salesforce API.
-
Username. User name for a user account with read and write access to the Salesforce APIs.
-
Password. User name for a user account with read and write access to the Salesforce APIs.
-
User Secret. The user secret for a user account with read and write access to the Salesforce APIs. Refer to Create a Secure Salesforce API User.
-
Consumer Secret. The consumer secret. Refer to https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/CR_quickstart_oauth.htm.
-
Consumer Key. The consumer key. Refer to https://developer.salesforce.com/docs/atlas.en-us.chatterapi.meta/chatterapi/CR_quickstart_oauth.htm.
-
Max # of Records per Payload. The maximum number of records to send to Salesforce in each action. The default value is “50”.
Create a New Action
Kate Gibsonkate.gibsonEdit Profile #
To create an action for Salesforce, contact Lucidum customer care.
