Connecting Salesforce to Automate.io
There are two methods to connect Salesforce to Automate.io.
Go to APPS in your dashboard. Click the blue ‘+’ button on the top-right. You will see a ‘Add a new app’ pop-up.
Type Salesforce in the search box. Select Salesforce.
Enter the app name and select the environment. Select 'Sandbox' if you wish to run tests and experiments on your Bots. Select 'Production' to work with live data. Click 'Authorize'.
In the next window, enter your Salesforce 'Username' and 'Password' and click Login. Then click Save. Salesforce is successfully connected to Automate.io.
While creating a Bot, you can directly connect Salesforce either as a Trigger or an Action app. Refer to 'Connecting the Trigger app' or 'Connecting the Action app' in How to create a Bot.
Supported Triggers and Actions
A Trigger is the event that starts the Bot. So it’s always the first event in the Bot. An Action is the event a Bot performs. It occurs as a response to the Trigger in your Bot.
Automate.io supports the following Triggers and Actions for Salesforce.
- New Contact: Triggers when there is a new Contact
- New Custom Object: Triggers when there is a new Custom Object (of the type selected) is created
- New Lead: Triggers when there is a new Lead
- Updated Opportunity: Triggers when an existing Opportunity is updated
- New Opportunity: Triggers when there is a new Opportunity
- New Task: Triggers when there is a new Task
- New Account: Triggers when there is a new Account
- Updated Opportunity Property: Triggers when an existing Opportunity's property is updated
- New Event: Triggers when there is a new Event
- Updated Lead: Triggers when an existing Lead is updated
- Updated Account: Triggers when an existing Account is updated
- Updated Custom Object: Triggers when an existing Custom Object is updated
- Updated Contact: Triggers when an existing Contact is updated
- Updated Contact Property: Triggers when an existing Contact's property is updated
- Updated Account Property: Triggers when an existing Account's property is updated
- New Case: Triggers when there is a new Case
- New Note: Triggers when there is a new Note
- Updated Opportunity Stage: Triggers when an existing Opportunity's Stage is changed
- New Case Comment: Triggers when there is a new Comment on a Case
- Add or Update a Contact: Creates a new Contact or updates an existing Contact
- Add or Update a Lead: Creates a new Lead or updates an existing Lead
- Add or Update an Account: Creates a new Account or updates an existing Account
- Add or Update a Custom Object: Creates a new Custom Object or updates an existing Custom Object
- Add or Update an Event: Creates a new Event or updates an existing Event
- Add a Note: Creates a new Note
- Add or Update an Opportunity: Creates a new Opportunity or updates an existing Opportunity
- Add or Update a Task: Creates a new Task or updates an existing Task
- Add a Campaign Member: Creates a new Campaign Member (Existing Lead or Contact)
- Add or Update a Case: Creates a new Case or updates an existing Case
- Search a User: Search Users
- Get Account of a Contact: Get Accountof a Contact
- Add a Call Log: Creates a new Call log
- Get Contacts for a Opportunity: Get Contacts for Opportunity
- Search an Account: Search Accounts
- Search a Task: Search Tasks
- Search an Opportunity: Search Opportunities
- Search a Contact: Search Contacts
- Search a Custom object: Search Custom Objects
- Search an Event: Search Events
- Search a Lead: Search Leads
- Get Opportunities of a Contact: Get Opportunity for Contact
- Search a Folder: Search Folders
- Search a Case: Search Cases
- Search a Campaign: Search Campaigns
Frequently Asked Questions
What Salesforce Editions work?
We support all editions of Salesforce.
What is the difference between the Input fields 'Update if existing' and 'Update existing data'?
'Update if existing' and 'Update existing data' are fields in the 'Update' section that come in useful when you want to make changes to existing records.
Case 1: If 'Update if existing' is set to No, the record won’t be updated. Instead, a duplicate will be created.
Case 2: If 'Update if existing' is set to Yes, and 'Update existing data' is also set to Yes, then the new data coming in will be added along with the existing data. For example, say a record has the following data.
Here, only the Email Address column has been filled and the rest are blank. Now, in your Bot's Input fields, set 'Check for duplicates using' to Email and map the 'Value to check for' to Email.
If you are updating the columns 'First Name', 'Last Name', and 'Phone', your updated record will look like this.
Case 3: If 'Update if existing' is set to No, only the new data will be added against that field (say Email Address) and the other fields will be removed.
For example, if a record has 'First Name' and 'Email Address' columns filled and you are updating the 'Last Name' and 'Phone' columns by checking against 'Email Address', then the updated record will show 'Last Name', 'Email Address', and 'Phone' and erases the 'First Name' field.
Your Bot will be able to trigger up to 200 contacts successfully during each data check.
Common issues with solutions
1. I'm unable to see the input fields in my Bot.
If you're unable to see the input fields, it's likely that you don't have the access to view them. We recommend you to reach out to your Salesforce administrator for access.
2. Error: Add or Update an Account INVALID_CROSS_REFERENCE_KEY: Record Type ID: this ID value isn't valid for the user: 012O0000000C20XIAS
There are two workarounds for this error.
- Make sure that you are on the correct environment while creating or running your Bots. If you are trying to run the Bots that you've created in the Sandbox environment on the Production environment or vice-versa, your Bot can throw this error.
- Make sure that you are connected to the correct Salesforce account.
3. Error: Add or Update an Account DUPLICATES_DETECTED
It looks like you are creating a duplicate Account. This can happen if you have a Duplicate Rule in place which is preventing the Bot from adding or updating an account. The Bot basically believes a duplicate already exists (when it might not.) Here is an example of setting a Duplicate Rule for Account objects.
To navigate to Duplicate Rules, click on Setup (the gear button) on the top-right in your Salesforce dashboard and then click 'Setup'.
The Setup window opens. Search for 'duplicate rules' in the search box on the top-left.
Under 'Rule Name', select 'Standard Account Duplicate Rule'. Then click Edit.
If 'Action On Create' and 'Action On Edit' are set to Alert, the rule will block these duplicates from getting created and show the error above.
Uncheck these boxes to allow the "duplicates" to be created. Then click Save.
For more info on duplicate rules for other objects, check out these Salesforce's help docs.
If you see this error with "API_DISABLED_FOR_ORG", you will need to get API enabled for your account. Please contact your Salesforce Admin or support.
We recommend you to enable History Tracking when using the triggers 'Updated Contact Property', 'Updated Opportunity Property', and 'Updated Account Property'.
- To set History Tracking for Opportunity fields, go to Setup -> Object Manager -> Opportunity -> Fields & Relationships -> Set History Tracking -> Enable -> Select fields
- To set History Tracking for Contact fields, go to Setup -> Object Manager -> Contact -> Fields & Relationships -> Set History Tracking -> Enable -> Select fields
- To set History Tracking for Account fields, go to Setup -> Object Manager -> Account -> Fields & Relationships -> Set History Tracking -> Enable -> Select fields