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.
Errors
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. One common issue is the disconnection of the Clay integration after being turned on. This often happens due to an invalid webhook URL, which results in a 404 NotFound error. When RB2B encounters this error, it automatically disables the integration to prevent further issues.
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. To resolve issues with the Clay integration:
Verify the Webhook URL: Ensure the webhook URL pasted into RB2B matches the URL generated by your Clay table. If necessary, recreate or copy the URL again.
Check Authentication Settings: Confirm that the webhook is not set to require an authentication token.
Update the URL in RB2B: If the URL has changed on the Clay side (e.g., due to table settings being updated), update the URL in RB2B accordingly.
Re-enable the Integration: After correcting the URL, re-enable the integration in RB2B.
Once the integration is re-enabled in RB2B, no additional steps are required. The system will automatically resume pushing data when Clay sends it.
Best Practices for Maintaining Webhook Connections
Regularly verify the webhook URL to ensure it remains valid and matches the configuration in Clay.
Avoid making changes to the Clay table settings that could alter the webhook URL without updating it in RB2B.
Monitor logs in RB2B for any error messages related to webhook connections and address them promptly.
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
}
Testing
To test your integration, follow these steps:
Enter the URL of your Webhook and click the "Save" button to save it.
Send a Test Event: After saving the URL, click the "Send a Test Event To Your [integration] Account" button. This action will send a test payload to the provided URL, simulating the data that would be sent during actual use.
Monitor Feedback: Observe the top right corner of your screen for feedback and error messages. These notifications will inform you whether the test event was successful or if there were any issues with the integration.
By following these steps, you can ensure that your integration with RB2B is functioning correctly.
Test Payload
The test payload sent will be formatted in the same manner as the example below:
{
"LinkedIn URL": "https://www.linkedin.com/in/retentionadam/",
"First Name": "RB2B",
"Last Name": "Test Payload",
"Title": "Webhook Test Payload from RB2B",
"Company Name": "RB2B",
"Business Email": "[email protected]",
"Website": "https://rb2b.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://google.com",
"Captured URL": "https://rb2b.com/pricing",
"Tags": "Hot Pages, ICP",
}