File validation
In addition to single and bulk email validation, our Zapier integration allows you to validate multiple email addresses specified in a .csv file and pass the results along to the next stage.
Follow these steps to start using ZeroBounce Single Email Validation with your Zaps.
Step 1 - Create a new Zap (see Create a New Zap section above)
Step 2 - Select a trigger
- A trigger external to ZeroBounce will be required (an event listener on a different app to initiate our Zap). For this example, we’ll use a new csv file uploaded to our Google Drive. Type “google drive” into the search bar and select the Google Drive option.
- Select New File in Folder for our triggering Event. Click Continue.
- If you’ve yet to do so, you will need to grant Zapier access to your Gmail account. See the Link Gmail account section above for more details. Click Continue.
- Select the appropriate Drive and Folder, and click Continue.
Note: Our zap will be triggered by all files created here, not just uploaded csv files. You should be careful not to add any files not intended for this Zap here.
- This will now fetch a file from your account.
Step 3 - ZeroBounce file validation
- Type “ZeroBounce” into the search bar and select the ZeroBounce option.
- Select File Validation from the dropdown and click Continue.
- If you’ve yet to do so, you will need to link your ZeroBounce account to Zapier. For more details on how to do this, please refer to the Link ZeroBounce Account section above. Click Continue.
- File Validation takes four parameters:
File - the .csv file to be evaluated
Email Address Column - what column the email address is within the .csv file (starts at 1)
Has Header Row - boolean specifying whether the first row should be ignored when processing
Remove Duplicate - boolean value specifying whether duplicate entries should be ignored when processing (to conserve credits).
We will input the uploaded file from the previous Google Drive Step. Click Continue.
- To verify our action, click Test Action.
- You should receive a response similar to this, showing that the file has been uploaded successfully for processing. This integration uses a callback to transfer data to the next step, which will happen at a later time. The output of that callback is a file, and we can still use it to chain more actions.
Step 4 - Add a new action
- The result from the previous step does not do much by itself, but we can chain another action that uses it. We’ll uploadthe resulting file to Google Drive. To add a new action, click the (+) symbol at the end of the previous one.
- Select the Google Drive option.
- For the triggering Event, select Upload File.
- If you’ve yet to do so, you will need to grant Zapier access to your Google Drive account. See the Link Google Drive section above for more details. Click Continue.
- Fill in the appropriate options for Drive and Folder. Be careful not to set the target upload folder the same as the trigger input folder as this will trigger infinite loops or errors.
Set Convert to Document? to False (we’ll upload as is).
For File, we’ll use the ZB File option. It should display no data as our action uses a callback and the data is not available yet.
For File Name we’ll use the Google Drive Original Filename (the filename the file was uploaded as) and csv for extension. Click Continue.
- We will be unable to test this part as the callback data is unavailable. Click Test Action.
- As expected, our test has failed. We’ll skip it for now and verify that it works later. Click Skip test.
- Click Publish Zap.
- Click Publish & Turn On.
Step 5 - Verify that our Zap works
- Go to your Zapier Dashboard and select Zaps from the left menu. Make sure that an appropriate file is uploaded to our trigger directory.
- If your app does not trigger by itself, click on the three dots and select Run from the menu
- You should see output like this. If not, ensure that the file exists and was uploaded after Zap creation, or that the Zap has not already run.
- From the same dot menu, click on History.
- You should see a list of all runs for this Zap. We can see that the last one awaits. Click on it.
- You will see a list of all actions of our Zap and intermediate results for this run. You will notice that the first stage (the trigger) was successful, while the second one is “Waiting” for the callback from ZeroBounce execute.
- If you click on Data out, you will see the output from all stages. Stage 2 shows the intermediate output that was passed along to the ZeroBounce server.
- After some time, the callback will execute, and the output will either show success or display an error. At this point, you can check the target drive folder for the uploaded file. It should be there.
Was this page helpful?
Interested in our partner programs?
