Hello! Is anyone here good with webhook on SF? I keep getting an error on my Clay webhook and can’t understand why Goal is to enrich in real time our accounts based on enrichment from Clay
This error typically happens when your Salesforce Flow can't access the Clay webhook credentials. The issue is usually with your API key configuration or permissions.
First, grab your Clay API key from Settings > Your Profile > API Key section in Clay. Then check that this API key is properly added to your Salesforce external credential "Clay_Webhook_External_Cred" - make sure it's saved correctly there. [1]
Also verify that your Salesforce user has the required permissions: Access Identity Information, Manage User Data via APIs, and Perform Requests Anytime. [2]
Can you click into the specific error cell in your Flow to see if there are more detailed error messages that might help pinpoint the exact credential issue?
Inputs
body = {!Claywebhook_body} (ClayWebhook_Clayx20Webhook_IN_body : { "website_set" : true, "sfx5faccountx5fid_set" : true, "sfx5faccountx5fid" : "001Ph00000uEzYAIA0", "linkedinx5furl_set" : true, "industry_set" : true, "employee_set" : true, "domain_set" : true, "accountx5fname_set" : true, "accountx5fname" : "HEADWAY Consultoria e Tecnologia" })
The error you're seeing means Salesforce can't access your Clay API key through the external credential. This usually happens when the API key isn't properly configured in your "Clay_Webhook_External_Cred" external credential.
First, grab your Clay API key from Settings > Your Profile > API Key section in Clay. Then check that this API key is correctly added to your Salesforce external credential "Clay_Webhook_External_Cred" and saved properly. [1]
Also verify your Salesforce user has these required permissions: Access Identity Information, Manage User Data via APIs, and Perform Requests Anytime. [2]
Can you click into the specific error cell in your Flow to see if there are more detailed error messages about the credential issue?
where do i need to see the API key in the credentials?
In Clay, go to Settings > Your profile > API key. You'll find your API key there - you can copy it from that section. [1]
Once you have it copied, you need to add it to your Salesforce external credential "Clay_Webhook_External_Cred" in Salesforce (not in Clay). That's where Salesforce is looking for the credential to authenticate the webhook calls. [2]
Did that answer your question?
What is the authentication protocol I need to add? Do I need to add the API Key in the Related Named Credentials URL?
You'll add your Clay API key (which you can find in Settings > Your Profile > API Key) to the Salesforce external credential "Clay_Webhook_External_Cred" - not in the Named Credentials URL itself. The external credential handles the authentication token that gets passed in the Authorization header when Salesforce makes the webhook call to Clay.
Are you setting this up in the external credential configuration, or are you still having trouble locating where to add the Bearer token in Salesforce?
trouble locating where to add the Bearer token in Salesforce
In Salesforce, you'll add the Bearer token in your External Credential configuration. Go to Setup → Named Credentials & External Credentials → External Credentials, then find your "Clay_Webhook_External_Cred" external credential. [1]
In the external credential setup, you'll configure the authentication with your Clay API key as a Bearer token. The token type should be set to "Bearer" and the auth header name should be "Authorization" (which are typically the defaults). [2]
Are you able to locate the External Credentials section in your Salesforce Setup, or do you need help navigating there?
You'll want to select "Custom" as your Authentication Protocol (which you already have selected).
For Clay webhooks, you need to set up Bearer token authentication. In the custom authentication setup, configure:
Auth Header Name: Authorization
Token Type: Bearer
Token value: Your Clay API key (from Settings > Your Profile > API Key in Clay) [1]
The authorization header should follow this format: Authorization: Bearer YOUR_API_KEY [2]
After you configure these settings in your external credential, save it and try your webhook again.
Is that what you were looking for?
If you still need help resolving the webhook authentication issue, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific difficulties you’re encountering?
