My Zap keeps assigning a record or object to the same owner
Check your Salesforce account to see:
- If there is a workflow rule/auto-assignment rule that's overriding your Zap settings.
- If your Salesforce Profile has Transfer Record enabled. Transfer Record allows you to change the owner of most records. You may need a Salesforce Systems Administrator to help adjust your profile settings.
- If you have the correct permissions to set the
ownerIdfield. Read more on the limitations of setting the
Connected app access limits to Salesforce
Salesforce allows a user to have 5 access tokens authorized to one Salesforce account to all third-party applications, including Zapier. After those 5 access tokens are generated, older tokens are automatically revoked without notification. This does not mean you're limited to only having five total Zaps using the Salesforce integration, just number of Connected App Access across all the third-party apps you use.
You can manage your connected apps access to directly in Salesforce and view your Zapier account connections which are called "Zapier CLI App".
What Salesforce account types and editions are supported on Zapier?
We support Sales/Support Accounts and any edition (including Essentials). Unfortunately, we don’t support Marketing Cloud accounts.
How search actions work
Salesforce search actions return the most recently created record that meets the search criteria, even if there are multiple records that match.
Custom fields/objects not loading
Sometimes when you add custom fields or objects in Salesforce, there is a delay between when they will appear in the Zap editor. To fix this with a trigger you can scroll to the bottom of the Salesforce Object menu and select to reload and bring in new choices.
If you are dealing with actions, here's a couple steps that may help:
- Hard refreshing the page (Shift+F5 on a PC or CMD+Shift+R on a Mac) a couple times
- Click ‘Refresh fields’ at the bottom of the Zap step
- Copy that Zap and edit the copied version to see if the fields appear
- Recreate the Zap from scratch
- Wait a while longer, sometimes it takes a little while for the cache to refresh with those fields
Error: "This connection to Salesforce appears to no longer be working"
If you run into this error this means your Salesforce account has exceeded the 5 connection app access limit. To resolve this, follow these steps:
- Review your connected apps in Salesforce to make sure you have a token that you can use with Zapier.
- Connect/reconnect your Salesforce account either within the Zap Editor or on your My Apps.
Error: "TotalRequests Limit exceeded"
This error means the number of times Zapier is allowed to ask Salesforce for data has been exceeded for your connected account, as there are Salesforce API Request Limits.
There are 2 ways Salesforce limits requests to their API:
1. Requests within a 20-second period (called "concurrent" requests)
2. Total API requests within a 24-hour period
To resolve you have a couple of options:
- Upgrading to a Salesforce plan with more users and higher request limits will stop this error from occurring.
- If you have Zaps using the Updated Record Triggers, you can consider using the Updated Field on Record Trigger to scope down the number of updates your Zap triggers on.
- If you have Zaps using New/Updated Record Triggers, you can consider creating a Salesforce outbound message workflow and switching the Trigger to “New Outbound message”.
If you see this error, there may be a "Duplicate Rule" in place on your Salesforce account preventing Zapier from creating the record. Here is an example of a "Duplicate Rule" for Account objects:
If the Actions are set to 'Alert', the rule will block these "fuzzy duplicates" from getting created and throw the "DUPLICATE_VALUE" error).
Unchecking the 'Alert' box will allow the "duplicate" to be created.
Salesforce's help docs cover more details on duplicate rules for standard objects and how to customize a duplicate rule.
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:
- Lots of data in your Salesforce Account, specifically of the type you're trying to access. (think: enterprise level)
- Your object contains many computed fields
- Ephemeral outages or Salesforce API issues. Check our API Status Board for possible issues.
Most of the time these errors are transient and you need to wait. If the error happened on a trigger for a Zap that is turned on (ie. Salesforce as a trigger), you can safely ignore it (we will automatically recover this scenario). If the error occurred on the action step for a Zap that is turned on, you can attempt to replay failed Tasks within our Task History interface.
A Salesforce admin for your organization has blocked the Zapier integration from your account. To unblock, an admin will need to do the following:
- Navigate to Setup > Manage Apps > Connect Apps OAuth Usage
- Look for the 'Zapier' Connected App
- If the "Action' button for the Zapier app says "Unblock", then this Connected App has been blocked.
- To unblock Zapier, click the "Unblock" button
- To proceed, review the dialog box that appears and click "OK"
Error: "we’re having trouble loading ‘Object’ data"
If you run into this error, this means we couldn't find new objects with the name
<Object Name> or that we're currently not able to use this object type. You can report this to support.
Double check what type of field you're trying to update. It could be encrypted and isn’t able to be unencrypted. Salesforce has this help on how a Salesforce admin can unencrypt these fields .
This usually means that a Salesforce admin has restricted updates or insertions on that particular field(s) listed in the error message. You’ll need to contact your Salesforce admin to get the necessary permissions for the action.
Double check if one of the fields/objects has a custom validation rule. You would need to check that rule and ensure that the record we are creating through the Zap adheres to that rule.
My Updated Field on Record trigger returns a sample that doesn't match the settings I selected
When looking for a sample, the Updated Field on Record trigger will bring the most recently updated record, even if it doesn't match the value selected in the Field Updated To field. This is expected behavior, but it doesn't affect the Zap when it runs. It will only trigger for the specific value selected for that field.