Help center Core configuration Integrations & migrations Configure HunterIO customer enrichment Updated Wednesday, October 28, 2026 · Marc Staine HunterIO supplies additional person and Company data for Supportbench customer records. Configure the connection and automation according to your data-maintenance process: enrichment can replace supported saved fields, and the current new-contact, existing-contact and manual-refresh paths have different effects. Returned information is context to review, not proof of identity, Company membership or customer entitlement. Applies to: Supportbench Core. Location: Settings → Integrations → HunterIO. Configuration requires permission to administer integrations and edit this settings section. Manual Company/Contact refresh separately requires permission to edit the selected saved record. Before you begin Identify the intended Hunter account, its approved API key, plan and available enrichment usage. Core uses HunterIO; retired Clearbit setup instructions and credentials are not the current connection procedure.Decide which customer fields may be replaced by provider information. Manual Contact refresh can replace first name, last name and biography with blank returned values; manual Company refresh can similarly replace name, description and phone. Other supported optional values replace existing data when supplied.Review Company domains and Contact relationships before allowing automatic Company creation. A provider match is not an authorization decision and may not represent your customer’s contractual organization.Prepare approved sample records and record important before-values. Keep API keys and unnecessary customer data out of screenshots, articles and ordinary support diagnostics.Understand the existing-contact behavior before enabling it: the post-update provider path does not persist a second enriched Contact profile, and Company creation there does not explicitly link the returned Company back to the Contact. Configure and verify Open Settings → Integrations → HunterIO and select Connection. Confirm that the displayed installation is the intended one. If Needs attention reports multiple configurations, have Supportbench resolve that conflict before changing it.Enter the Hunter API key when setting up or intentionally replacing the credential. Leave it blank to preserve an existing saved key. The saved key is never returned to the page; Show or hide the newly entered API key applies only to your new entry.Open Automation. Review each switch below and choose only the behavior you have accepted and tested. Manual refresh does not require enabling every automation switch.Use the integration toolbar Save action. New/replaced credentials are verified through a real provider Company lookup before being saved; this may consume provider usage under the account plan. There is no separate Test connection button.Reopen the configuration and review Status and the saved automation choices. Audit shows configuration creation/modification information, not proof that a particular Contact was enriched.Test one approved saved Company or Contact through its editor’s Integrations → Refresh from HunterIO action. Save local edits first; the action runs immediately without a separate confirmation dialog.Compare the saved record with its before-values and expected relationship/domain changes. Run new-contact and existing-contact automation tests separately before relying on either path broadly. Settings reference Connection and automation controlsSettingWhat it controlsHow to chooseAPI keyWrite-only Hunter credential. A blank field preserves the saved key; a new/replaced key is provider-verified.Use the intended account’s private API key and review usage/credits with its owner. Do not substitute a historical Clearbit key.Show or hide the newly entered API keyReveals or masks only the new value in the current editor. The saved server key is not returned.Use away from observers/screenshots and leave the field blank when no key replacement is intended.Synchronize new incoming ContactsEnriches a supported new Contact before save when its prerequisites, including email and configured key, are present.Test resulting person fields, blank-value overwrites and customer association on a controlled new Contact.Synchronize existing Contacts when updatingRuns the established post-update provider path, but does not persist a second set of enriched Contact fields.Do not rely on this switch to refresh an existing saved person profile. Use a deliberate manual refresh when that is intended.Create new Companies from new ContactsWith new-contact synchronization enabled, usable person data including a non-empty first name, a named Company result and an unlinked Contact are required. The path can then create a Company with unowned domains and link the new Contact.Review existing Company/domain ownership first. In the existing-contact post-update path a Company may be created without explicitly linking the Contact; inspect the actual result.Status / Needs attentionShows configured/active state or a multiple-configuration conflict.Connected does not guarantee a match or quota for every future lookup. Resolve duplicate configuration warnings before saving or uninstalling.AuditConfiguration creation/modification and author information.Use for who changed the settings and when; inspect records/provider results to verify enrichment.Uninstall HunterIORemoves the saved key and automation settings while keeping existing Contacts and Companies.Review affected consumers and the confirmation. Uninstalling does not restore values previously overwritten by enrichment. Behavior to knowRefresh from HunterIO runs immediately from the saved record editor’s Integrations section. The Contact path blocks unsaved edits; the Company response can refill the editor, so save Company changes first as well.Manual Contact refresh uses the saved email and person data. It does not create/link a Company or change company_id. Manual Company refresh queries saved domains in order, uses the first usable response and may add returned domains to that same Company.There is no bulk-refresh control established by this configuration. Existing-contact update automation should not be described as a complete saved-profile refresh.Provider verification and enrichment use real requests. Hunter credit and rate behavior varies by plan; inspect the actual account rather than assuming a fixed price or unlimited lookups.A no-data result can be valid. It does not establish that the customer is invalid, and it should not cause an agent to use a different business’s email/domain to obtain a match. Recommended use Start with controlled manual refreshes and inspect exact fields. Enable a specific automation path only when the overwrite and relationship behavior meets the customer-data policy.Keep customer-confirmed organization relationships authoritative for support decisions. Do not grant case visibility or service entitlements solely from provider enrichment.Assign an owner to review provider quota, credentials, unexpected data replacements and Company/domain associations. Record the operating decision without copying secrets.Use the provider’s current API-key and plan guidance. Retain older Clearbit records only as history; they are not instructions for current Core setup. Worked example: verify a saved Company refresh Choose an approved test Company with known saved domains and meaningful existing name, description and phone values. Record the relevant before-values.Save pending edits, open the Company editor’s Integrations section and select Refresh from HunterIO once. The request begins without another confirmation.Read the result and inspect the saved Company fields and domains. Confirm that the returned organization is the one the support team intends to represent.Repeat the appropriate new-Contact automation test separately if you intend to enable it. Verify the actual Company relationship instead of assuming the manual and automatic paths are equivalent. Troubleshooting ProblemWhat to checkConfiguration is read-only or refresh is rejectedConfirm integration administration/section edit access for settings and record edit permission for Company/Contact refresh.API key field is blank on reopeningThe saved key is intentionally not displayed. A blank field preserves it unless a replacement is entered.Provider rejected the keyCheck the intended Hunter account and credential, including whether the plan supports the enrichment lookup used for validation.Existing Contact update did not change its profileThe current post-update path does not persist a second enriched Contact profile. Use the supported manual refresh for an intentional update.A Company was created but an existing Contact remains unlinkedThat post-update path does not explicitly assign the returned Company ID. Review and correct the actual relationship deliberately.A supported field became blankSome fields are overwritten even when the provider returns blank values. Restore customer-confirmed data through an authorized edit and review automation use.No Company data was foundCheck saved domains and their order and whether the provider has a usable Company match.Rate-limit, quota, timeout or provider failure messageInspect the actual provider account usage/status and returned error category. Avoid repeated blind refreshes; there is no user-facing per-record retry queue in this procedure.Needs attention reports more than one configurationContact Supportbench to resolve the installation conflict before modifying or uninstalling it. Related configuration Integrations → Use the data synchronization logOrganization → Configure agent roles and division accessMaintain Company and Contact relationshipsFind the Hunter API keyHunter API guidance and usageHunter API for Data Plans Was this article helpful? Yes No Thank you for your feedback.