Integrations and data imports
Verify email deliverability
Verify email deliverability with ZeroBounce and write the signal to a HubSpot contact.
Make it your own
Review the setup and limits below, then open an editable copy in Turbyn.
Use this recipeYour selection stays with you through signup.
What it does
Valid, invalid, and temporary results stay distinct; unknown preserves an existing definitive value by default.
What to customize
Bind ZeroBounce key and map contact ID.
Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.
Expected outcome
This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.
Sample input
sample-input.json
{
"inputFields": {
"field1": "{\"email\":\"person@example.com\",\"contactId\":\"123\"}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "dry_run",
"output2": "",
"output3": "person@example.com"
}
}Returned fields
- output1
- valid, invalid, unknown, failed
- output2
- output3
- reason and definitiveness
What changes when it runs
Reads existing deliverability, calls ZeroBounce validate, and patches deliverability fields only for definitive or explicitly actionable results.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.