Clay integration is only available for RB2B Pro users.
Setting up an integration between RB2B and Clay enables efficient data synchronization, but incorrect setup or errors can disrupt this process. This guide will cover both essential setup requirements and troubleshooting strategies for common issues.
To initiate your Clay integration, navigate to Integrations from the sidebar menu. Locate and select Clay among the integration options or visit https://app.rb2b.com/integrations/clay
By default, RB2B only sends net-new contact profiles to Clay. Ensure new, unique visitors have been identified since setting up the integration to avoid redundancy. This can be changed by toggling the "Send repeat visitor data" setting.
In the input field provided, add your full Clay Webhook URL then click Save to publish your changes.
The URL used must be secure and include https://
Settings
After connecting Webhook, you can toggle on/off the following settings:
Sync company-only profiles: If enabled, RB2B will send identified company-level visitor information to Webhook.
Send repeat visitor data: If enabled, RB2B will send all subsequent visits by a visitor to Webhook. Please be aware that many integrations may not be configured to handle duplicate or similar data properly, which could result in the creation of duplicate entries instead of updating existing ones. You are proceeding with this action at your own discretion, and we are not responsible for any impact it may have on your data.
Adding Webhook as a Source in Your Clay Table
If your Clay table does not already monitor a Webhook for incoming data, you'll need to add Webhook as a source of data for your table. To do that, follow these steps:
Click Actions then Import.
Search for and select Monitor Webhook in the list of available options.
Click Copy to copy the Webhook URL to your clipboard to paste in the RB2B dashboard.
In order to connect, your Clay webhook must not be configured to require an auth token.
If your webhook integration encounters issues such as endpoint failures (e.g., timeouts or errors), RB2B automatically disables the integration as a safety feature. Ensure the webhook endpoint is responsive before re-enabling the integration via the RB2B dashboard.
Monitor the RB2B dashboard for any error messages that indicate issues with the Clay integration. Address these issues, such as invalid webhook URLs or temporary endpoint errors, based on the error details provided.
Retrieving an Existing Webhook Source's URL
If your Clay table already monitors a Webhook for incoming data, you can get its URL by following these steps:
Click the + icon on the righthand side of the Webhook column in your Clay table.
Click Copy to copy the Webhook URL to your clipboard to paste in the RB2B dashboard.
In order to connect, your Clay webhook must not be configured to require an auth token.
Required Fields
Some, but not all, fields are required to have values for the payload to send. Required fields include:
LinkedIn URL
First Name
Content Preview
{
"LinkedIn URL": "https://www.linkedin.com/in/retentionadam/",
"First Name": "Adam",
"Last Name": "Robinson",
"Title": "CEO @ Retention.com. We help Ecomm brands grow & monetize their first-party audience",
"Company Name": "Retention.com",
"Business Email": "[email protected]",
"Website": "https://retention.com",
"Industry": "Internet Technology & Services",
"Employee Count": "1-10",
"Estimate Revenue": "$22M rev",
"City": "Austin",
"State": "Texas",
"Zipcode": "73301",
"Seen At": "2024-01-01T12:34:56:00.00+00.00",
"Referrer": "https://retention.com",
"Captured URL": "https://rb2b.com/pricing",
"Tags": "Hot Page, Hot Lead",
}
Repeat Visitor Information
If you have "Send repeat visitor data" enabled, an additional field will be appended to the data for repeat visitors only.
{
"is_repeat_visit": true
}