> 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/abstract.md). # Abstract email and IP checks Abstract Email Reputation and Abstract IP Geolocation are separate connections and workflow actions. ## Connect the right API An admin opens the appropriate Abstract card in **Settings → Integrations** and enters the key for that API product. Saving Email Reputation checks a sample email and can use one Abstract credit. Saving IP Geolocation looks up a sample public IP and can use a credit. A key for one Abstract API is not interchangeable with a key for the other. ## Use a workflow action For email reputation, map the prospect email. Inspect the quality, deliverability or risk fields returned by the action before branching. For IP geolocation, map a real public IP. Inspect location, network and VPN-related output where returned. A private or missing IP should follow your fallback branch. ## Keep policy explicit A connection does not automatically reject a form submission. Add the action and a condition for the result your team wants to treat as valid, risky or unknown. Enrichment-chain email/IP switches are not a substitute for these standalone workflow actions. The IP switch has no automatic execution path in the current chain implementation. If a check fails, distinguish invalid credentials, quota, rate limits and missing input. Decide how provider failure should affect the visitor before publishing. --- # 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/abstract.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.