How to use a Righthand with Clearbit

Quick answer

Use Righthand to review owner-provided Clearbit enrichment against an accepted account list. Confirm your current product and access before treating an old integration name as a new standalone setup.

Start with a reviewable deliverable, keeping Clearbit as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

Evidence and access

Clearbit's official site states that it has joined HubSpot. See the official Clearbit reference. Provider capabilities and Righthand's available tools are separate checks.

Ask the account owner to identify the actual current Clearbit or HubSpot arrangement and supply the permitted enrichment packet with source dates. Verify the required tools and owner-approved scope through Righthand integrations; use the supplied packet when a native read is unavailable.

Define the objects and authority

Include these fields in the working input: company domain, source identifier, enrichment date, selected firmographic fields, existing CRM value, proposed value. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Provider enrichment is not automatically authoritative. Keep existing-account availability and the specific current HubSpot or Clearbit arrangement explicit.

Illustrative first-run brief

Use the owner-provided Clearbit snapshot or approved read-only view. Compare twenty supplied company matches with our approved CRM account list. Flag conflicting domains and outdated enrichment. Propose field updates without writing them. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the CRM owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

Expected result and verification

An unmatched domain remains unresolved rather than merging into a similarly named company. A newer field becomes a reviewed proposal, not an automatic replacement.

Check one match against the company's official page and the accepted CRM record. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.

Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

Common failure and recovery

Older credentials or retired packaging may not work. Have the owner confirm current access and use an approved export rather than promising a legacy endpoint.

When product access or provenance is unclear, preserve the existing CRM values and request an owner-confirmed source. Do not promise a new standalone setup.

FAQ

What should the reviewer verify first?

Verify the product arrangement, record identifier, source date, and permitted fields. A domain match is a candidate association, not proof of a current employment fact.

How should a repeat run be scoped?

Retain source and observation date for every proposal. Revalidate changed company domains and ownership; do not overwrite newer owner-confirmed information with an older enrichment snapshot.

For connection and permission details, use Righthand Docs. Review Pricing alongside any separate provider charges before expanding the workflow.