> 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/harmonic.md). # Harmonic Use Harmonic to enrich people and companies with your own provider account. ## Connect An admin opens **Settings → Integrations → Harmonic** and enters your Harmonic API key. Review the scope and options offered by the settings page, save and check the connection status. Select the person or company scope appropriate to the lookup. A connected credential does not guarantee a match for every identifier. ## Use the data Choose the provider in a supported enrichment step or chain and map a usable email, domain or other supported identifier. Review [Provider support by surface](/data-and-integrations/provider-support.md) before using the same chain in Workflows, Records or pre-submit enrichment. The surfaces do not execute chains in the same way. Workflow Enrich Lead merges per-field results from its configured providers; Records uses supported adapters sequentially and stops at the first usable result. ## Verify and troubleshoot Inspect one known prospect's returned fields before adding routing conditions. Branch on No match instead of treating empty data as a qualified lead. Check the provider error, scope, identifier and quota if a lookup fails. Simulation uses samples and does not verify provider billing or live coverage. Provider calls use your account’s allowance. See [Provider usage](/settings/provider-usage.md). Distro does not supply a shared managed enrichment-credit balance. --- # 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/harmonic.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.