Salesforce is very well supported on Zapier. You can Trigger off the creation of any object inside of Salesforce, including Custom Objects which might have been installed by another 3rd party application. Likewise, you can create any object inside of Salesforce as an Action.
If the object type you want to Trigger off of, or create, isn't visible inside the dropdown menu, choose the "Custom Object".
Later on inside the Zap editor, you'll be given the chance to decide which Custom Object you want to Trigger off of, or create.
Note: You can generally choose any object from the list for triggering. However, on the Action side, certain objects may not allow creation. If after choosing a Custom Object type, you can see no fields (and just see a "Continue" button) this implies there are no fields to create and you'll need to either choose a different Custom Object or an administrator will need to modify the object definition inside Salesforce, first. Here is an example of a Custom Object that does not allow creation (it has no fields):
Zapier already uses TLS 1.2 for apps which support it (including Salesforce) so their new minimum of TLS 1.1 will work fine with Zapier. You will not need to make any changes to your Zaps, and they will keep running as-is.
This is a somewhat common class of errors for Salesforce, which might manifest itself when working inside the Zap Editor or when receiving automated alert emails. Timeout errors indicate that Zapier's request to Salesforce took too long to get an answer.
Timeout errors can be caused by any number of things:
Most of the time these errors are transient and you simply need to wait a while. If the error happened for an On Zap on the Trigger side (ie. Salesforce as a Trigger), you can safely ignore it (we will automatically recover this scenario). If the error happened for an On Zap on the Action side, you can attempt to replay failed Tasks within our Task History interface.
Right now, Salesforce can trigger up to 200 items at one time. If you attempt to add more than 200 items at once, Zapier will only be able to see the last 200.
Sometimes when you add custom fields or objects in Salesforce, they won't show up right away in the portion of your zap where you map trigger data to the action template. An easy way to fix this on the trigger side is to submit a new entry with those custom fields filled in.
If you are dealing with actions, here's a couple steps that may help:
We don't yet support the standard Middle Name and Suffix fields that Salesforce released in 2015. A workaround is to create custom fields for the Middle Name and the Suffix. We plan to upgrade this in the future so the standard fields are available.
We do not support Salesforce communities at this point in time.
That error means that the number of times Zapier is allowed to ask Salesforce for data has been exceeded for your connected account.
There are 2 ways Salesforce limits requests to their API (how Zapier asks for data): 1. Requests within a 20-second period (called "concurrent" requests) 2. Total API requests within a 24-hour period
Upgrading to a Salesforce plan with more users and higher request limits will stop this error from occurring.
When you use the Create Task action, you can connect a task to a person or an object using these two fields:
If you're getting a Field Integrity Exception error, it means that you're trying to connect a person using the Related To field or an object using the Name field. If you want to connect the task to a person (like a contact or lead), use the Name field. If you want to connect the task to an object (such as an opportunity or an account), use the Related To field.
Pick the correct field and select "Use A Custom Value," then pass the ID of the person/object from a previous step.
Salesforce search actions will return the most recently created record that meets the search criteria, even if there are multiple records that match.
The Create Note action adds notes to the legacy 'Notes & Attachments' (also called "Classic Mode") function in Salesforce. The notes are not viewable in the new HTML version of Salesforce.
When using the Create Event action, if you just want to specify a Due Date, use the
Due Date Only field. If you want to specify both a Due Date and Time, use the
Due Date Time field, but fill in both a date and a time. If you only put a time in this field, you'll end up with an event on today's date at that time.
Zaps set up like this will ignore the Date field:
Zaps set up like this will properly set the Date and Time field in Salesforce:
Salesforce requires that multi-pick items have a
; between them. You can set it up like this:
Or if you're passing data from a previous step, you can use the Formatter to build a string with
; as the separator.
Whilst there is no official Trigger for updated objects (like updated opportunities, updated custom objects, updated contacts, etc.) you can likely get the same result by using the New Outbound Message Trigger.
Please note for this handy workaround, your Salesforce account must support workflow rules.
To do this, please follow these steps:
Firstly, create a Zap using the New Outbound Message Trigger. This trigger will create a webhook you can use on whatever workflow/trigger you want in Salesforce later.
Next, in your Salesforce setup area, you will need to create a new Workflow Rule. This rule will allow you to set the conditions that will trigger the outbound message to be sent out. This is what will trigger your Zap. In the example below, this workflow will trigger when a lead is updated: You can read more on creating workflows on Salesforce here.
Once you have saved that workflow, on the new screen that appears under "Immediate Workflow Actions" use the "Add Workflow Action" dropdown, choose "New Outbound Message" like this:
Here you can choose the object and the fields from that object that you want to send to your Zap. You will also need to enter the Webhook URL from your Zap's Trigger options in the "Endpoint URL" field like this:
When you have done that you can come back and finish setting up your Zap. This workflow will send an Outbound Message when your workflow triggers, which will trigger your Zap!