> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/integrations/zerobounce.md). # ZeroBounce Connect ZeroBounce when you use supported form email validation settings. ## Connect An admin opens **Settings → Integrations → ZeroBounce**, enters the provider credentials and saves. Review the connection status and last reported credits where available. Then configure email validation on the supported form or legacy routing surface that offers it. Connecting the provider alone does not apply a validation rule to every workflow. ## Test the policy Submit representative valid, invalid and uncertain test addresses through the actual form path. Check whether the visitor sees a helpful message and whether a workflow run should start. Do not assume a saved enrichment-chain validation switch runs ZeroBounce during Workflow Enrich Lead. Use supported explicit verification actions for new workflow-based checks; see [Abstract](/integrations/abstract.md) and [Icypeas](/integrations/icypeas.md). ## If validation stops working Review the connection's Needs attention state, credentials, provider balance and latest validation error. A reported balance is a snapshot, not a guarantee that every upcoming submission will fit the quota. A provider outage and an invalid email are different outcomes. Confirm your form's behavior for both before making validation a required path. See [Form troubleshooting](/forms/troubleshooting.md) and [Provider usage](/settings/provider-usage.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/integrations/zerobounce.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.