Troubleshooting SFDC Sandbox Connection Errors with Clay Integrations | Clay

Troubleshooting SFDC Sandbox Connection Errors with Clay Integrations

Aloha Team! I was attempting to do some web hook testing from our SFDC sandbox and I'm seeing an error with the connection. Both "Partial" and "UAT" are sandboxes and they both show errors. When I'm setting up a connection, do I need to have certain SFDC permissions to be able to set up the connection with Clay?

5 comments

Clay
APP
·
·
Yes, you need specific Salesforce permissions to connect Clay to your SFDC sandbox. Your Clay user requires: 1. Access Identity Information - Permission to access identity URL services (profile, email, address, phone) 2. Manage User Data via APIs - Permission to manage data through APIs 3. Perform Requests Anytime - Permission for refresh_token and offline_access You'll also need OAuth permissions enabled for the initial connection setup. Once connected, any user in your Clay workspace can use the integration. The connection scope is limited to objects and fields accessible to your OAuth user, so ensure your sandbox user has appropriate permissions for the data you want to access. Since you're experiencing JSON-related webhook errors, please copy and paste the specific error JSON into the chat so we can troubleshoot further.
Sources: Salesforce integration overview | Documentation | Clay University Salesforce Integration Guide FAQ: What permissions and scope do I need for the Salesforce enrichment? Salesforce integration overview | Documentation | Clay University
Eric N.
·
·
Here is the error message that my SFDC shared with me: {"responseStatus":"Forbidden","default":"\"{\\\"type\\\":\\\"Forbidden\\\",\\\"message\\\":\\\"Record limit reached for webhook\\\",\\\"details\\\":null}\"","responseCode":"403"}|HttpResponseStatus:403
Clay
APP
·
·
The error indicates your webhook has reached Clay's 50,000 record limit. Once this limit is reached, new records cannot be added, which explains the "Record limit reached for webhook" message. To resolve this, you'll need to create a new webhook table since the 50,000 limit persists even after deleting rows. We recommend splitting your records into several tables to prevent hitting these limitations. Enterprise customers have access to auto-delete features to help manage this limit more efficiently.
Source: Webhooks in Clay | Documentation | Clay University
Eric N.
·
·
I activated auto-delete on the table I was trying to write to and it began populating. That said, I tried to run a "lookup record" in SFDC and received an error that reads "Rate Limited, Please try again". What does that mean? (See screenshot)
Clay
APP
·
·
The "Rate Limited, Please try again" error means you've hit Clay's rate limits for processing requests. Rate limits ensure system stability and performance, particularly for columns using heavier prompts or operations. For webhooks specifically, Clay limits processing to 10 records per second with a maximum burst capacity of 20 records per workspace. To resolve this: - Wait a moment before retrying the lookup - Monitor which columns face frequent rate limit issues - Consider spacing out your requests if running large batches Clay is deploying features like retries and smarter pacing to better handle rate limits and reduce these errors.
Source: Import Data to Clay Using Webhooks