How to use BounceBan with Clay?

Integrating BounceBan with Clay allows you to clean and verify your email lists directly within your Clay tables, streamlining your waterfall enrichment workflows.

Here is the step-by-step guide to setting up the integration.

Prerequisite: Before starting, ensure you have your BounceBan API Key ready. You can retrieve it from your account settings here: https://bounceban.com/app/api/settings.

Step 1: Add the Enrichment

1. Open your Clay table.

2. Scroll to the right of your table and click Add column.

3. Select Add enrichment from the menu.

1. In the search bar of the enrichment panel, type BounceBan.

2. Click on the option labeled BounceBan: Verify email.

1. Email Field: In the 'Query parameters' section, look for the 'Email' field.

2. Type / to bring up the column selector.

3. Select the column in your Clay table that contains the email addresses you wish to verify. 

1. Navigate to the Headers section (or API Key section depending on your Clay version).

2. In the Authorization field, enter your BounceBan API Key.

3. Click Save changes.

4. Click Save and run 10 rows (or run for all rows) to test the integration. BounceBan will now begin verifying the emails from your selected column.

Once the integration runs, the results will appear in a new column as a JSON object. To make this data usable:

1. Click on a cell in the new BounceBan column that contains data.

2. Hover over the Result field (e.g., deliverable, risky, undeliverable).

3. Click Add as column.

4. Repeat this for other useful fields such as score or Status if needed.

FAQ

1. How long does the email verification process take? 

Most verifications are completed within a few seconds. However, some emails—specifically those protected by greylisting or advanced security measures—may take up to 10 minutes to verify. Unlike other services that might return an "Unknown" result immediately to save time, BounceBan takes the necessary time to ensure the highest accuracy.

2. If a result isn't returned immediately, do I need to set up a separate API call to check the status? 

No. The Clay integration is designed to handle this automatically. It will manage the waiting period and polling for you, ensuring you receive the final result without needing to build complex loop logic or separate API calls.

3. Which processing mode should I choose (Sequential vs. Concurrent)?

• Verify Email Sequentially (default): Use this default mode if your trigger sends data to BounceBan one item at a time (e.g., a webhook trigger).

• Verify Email in Batch (Concurrent): If your trigger processes multiple emails at once (e.g., a Google Sheets trigger reading rows), we highly recommend this mode. It submits requests to BounceBan concurrently rather than waiting for one verification to finish before starting the next, resulting in significantly faster processing speeds.

4. How are credits calculated when using the Clay integration? 

The pricing is identical to using our Web App or direct APIs. Each successful verification costs 1 credit. There are no additional fees for using the Clay integration.

5. Am I charged for repeated verifications of the same email? 

If you resubmit the same email address for verification via the Clay integration within 30 minutes of the initial submission, no credits will be deducted. This ensures you are not charged twice if you need to re-run a workflow shortly after the first attempt.