Skip to content
HotHawk logo
Close logo

HotHawk → Close

HotHawk + Close integration

HotHawk sorts replies across inboxes. OutboundSync logs what happens there on the matching Close Lead, so reps calling from Close know where each conversation stands.

BetaOne-way syncEmail and social

HotHawk + Close at a glance

HotHawk works with Close through OutboundSync. HotHawk email sends, received emails, bounces, labels, thread assignments, threads marked done, opportunity updates, and social messages and tags are logged as activity on the matching Close Lead. The sync is one-way, HotHawk into Close, and the OutboundSync team handles onboarding.

HotHawk + Close integration facts
StatusBeta (Close is a one-way beta CRM)
ChannelsEmail and social
DirectionOne-way, HotHawk → Close
Close recordsLeads
Block listsNot available for this pairing
HotHawk planNeeds webhook access
SetupGuided: the OutboundSync team runs onboarding

Some teams split the work: an inbox team triages replies in HotHawk, and closers work Leads in Close. The split breaks down when closers can't see what triage decided. OutboundSync carries HotHawk labels, assignments, and opportunity changes onto the Close Lead so the closer picks up with full context.

Both email and social threads come across. A Lead that replied on social and was labeled interested in HotHawk shows that in Close, ready for a Smart View that feeds the closer's queue.

What syncs from HotHawk to Close

Every event below arrives in near-real time and lands on the matched Close record. Pick the ones you want per source.

HotHawk events OutboundSync syncs to Close
EventChannelWhere it lands in Close
Email sent— Includes sends to leads with a specific labelEmailActivity on the Close Lead
Email received— Includes replies from leads with a specific labelEmailActivity on the Close Lead
Email bouncedEmailActivity on the Close Lead
Label added— A specific label, or any labelEmailActivity on the Close Lead
Opportunity updates— Opportunity created, won, or lost, and deal stage changesEmailActivity on the Close Lead
Thread updates— Thread marked done or assignedEmailActivity on the Close Lead
Social message sentSocialActivity on the Close Lead
Social message receivedSocialActivity on the Close Lead
Social conversation tag addedSocialActivity on the Close Lead

Event names come from the HotHawk webhooks OutboundSync receives. Close is a one-way beta, so exact event coverage is confirmed during onboarding. See the HotHawk event reference.

What teams do with HotHawk + Close

  • Hand off labeled replies

    Build a Smart View from HotHawk labels so closers see triaged Leads first.

  • Follow opportunity stages

    HotHawk opportunity updates show on the Lead, so everyone sees the current stage.

  • Cover both inboxes

    Email and social messages from HotHawk land on the same Close Lead.

Ways to connect HotHawk and Close

The options teams weigh before they commit a production sync.

Ways to connect HotHawk and Close, compared
OptionWhat it doesTrade-off
Zapier, Make, or n8nCompare integration platformsCatch HotHawk webhooks and write each event to Close with a workflow you build.Every event type, retry, and field change is a workflow you maintain, billed per task or step.
Custom buildBuild vs buyWrite your own service against the HotHawk and Close APIs.You own matching, deduplication, API limits, and every upstream schema change.
OutboundSyncPre-built email and social activity sync into Close Leads.One-way beta with guided onboarding. Lighter configuration than HubSpot or Salesforce today.

How to set up HotHawk + Close

  1. Step 1: Connect Close

    Authorize OutboundSync from the Close App Marketplace. The OutboundSync team adds Close as a Connected Account with you.

  2. Step 2: Connect HotHawk

    The OutboundSync team creates your HotHawk source with you and points HotHawk's webhooks at it.

  3. Step 3: Create the Close source

    Select HotHawk when you create the Close source, and confirm how contacts are matched.

  4. Step 4: Send a test event

    Trigger one HotHawk event and confirm it on a real Close Lead.

  5. Step 5: Go live

    Launch with the OutboundSync team watching the first production events in Close.

Plan requirements

HotHawk plan

Needs webhook access

OutboundSync receives HotHawk activity through webhooks. Confirm your HotHawk plan includes webhook access, or ask us to check during setup.

Close

Close is a one-way beta. There is no Close plan gate on our side; onboarding runs with the OutboundSync team.

Trusted by outbound teams

Redis
Windsurf
Gainsight
Sendoso
Crescendo
Tapcheck

HotHawk + Close FAQ

  • What HotHawk activity does OutboundSync sync to Close?
    Email sent, email received, email bounced, label added, opportunity updates, thread updates, social message sent, social message received, and social conversation tag added.
  • Which Close records does it write to?
    OutboundSync matches or creates Close Leads. HotHawk events land as activity on the Close Lead. See the Close beta guide for details.
  • Can HotHawk labels drive Close Smart Views?
    Yes. Label events are logged as Close activity, and teams use them in the Smart Views they build. OutboundSync does not ship prebuilt views.
  • Is the integration one-way or two-way?
    One-way. Activity flows from HotHawk into Close, and nothing is written back to HotHawk.
  • Can I use Close records as a block list?
    Not today. Block lists come from HubSpot lists or Salesforce reports. The Close beta syncs activity in only.
  • Do I need admin access to set it up?
    A Close admin authorizes OutboundSync from the Close App Marketplace during guided onboarding.
  • Which HotHawk plan do I need?
    OutboundSync receives HotHawk activity through webhooks. Confirm your HotHawk plan includes webhook access, or ask us to check during setup.
  • How is HotHawk + Close priced?
    Beta access is scoped with the OutboundSync team during onboarding. Billing follows the same model as every plan: sent messages per month. Replies, opens, clicks, and lead-category updates are not billed. See the pricing page.
  • Can I do this with Zapier, Make, or n8n?
    Yes, for lightweight automation. Zapier, Make, and n8n are good for prototypes and simple routing, but they need ongoing maintenance and bill by task or step. OutboundSync is pre-built for outbound CRM sync, keeps searchable event logs beyond 30 days, and prices by outbound volume.
  • What breaks first when this scales?
    Data quality and reliability break first: duplicate events, retries, out-of-order webhooks, and bursts during big sends. OutboundSync handles idempotency, timing buffers, and queue recovery, and flags suspicious or mismapped payloads instead of writing them.

HotHawk resources

Tutorials, case studies, and updates related to HotHawk.

See HotHawk activity in Close

A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.