HotHawk social events now supported
OutboundSync now syncs HotHawk social messages and conversation tag events into HubSpot and Salesforce alongside existing email events.
Harris Kenny


HotHawk → Salesforce
Your team triages replies in HotHawk. OutboundSync logs that triage in Salesforce: every message, label, assignment, and opportunity change on the Lead or Contact.
HotHawk connects to Salesforce through OutboundSync. HotHawk email sends, received emails, bounces, labels, thread assignments, threads marked done, opportunity updates, and social messages and tags are logged as Tasks on the matching Lead or Contact, or as EmailMessage records for email. The OutboundSync team sets up the HotHawk source with you.
| Status | Beta (HotHawk setup is guided by the OutboundSync team) |
|---|---|
| Channels | Email and social |
| Direction | One-way, HotHawk → Salesforce |
| Salesforce records | Leads, or Contacts and Accounts |
| Block lists | Not available for this pairing |
| HotHawk plan | Needs webhook access |
| Setup | Self-serve: create an External Client App, then connect it in OutboundSync; HotHawk source set up with our team |
Salesforce leaders want to know two things about outbound replies: how many turned into something, and how fast the team responded. HotHawk knows both, and OutboundSync writes it down in Salesforce. Label, assignment, done, and opportunity events each become a Task you can report on.
Because HotHawk covers social inboxes too, social messages and conversation tags land on the same Lead or Contact as email. A Flow can react to a HotHawk opportunity win the same way it reacts to any other Task, so Salesforce stays the system of record while the team works in HotHawk.
Every event below arrives in near-real time and lands on the matched Salesforce record. Pick the ones you want per source.
| Event | Channel | Where it lands in Salesforce |
|---|---|---|
| Email sent— Includes sends to leads with a specific label | Task or EmailMessage on the Lead or Contact | |
| Email received— Includes replies from leads with a specific label | Task or EmailMessage on the Lead or Contact | |
| Email bounced | Task on the Lead or Contact, plus optional OutboundSync fields | |
| Label added— A specific label, or any label | Task plus optional OutboundSync fields on the Lead or Contact | |
| Opportunity updates— Opportunity created, won, or lost, and deal stage changes | Task plus optional OutboundSync fields on the Lead or Contact | |
| Thread updates— Thread marked done or assigned | Task plus optional OutboundSync fields on the Lead or Contact | |
| Social message sent | Social | Task on the Lead or Contact |
| Social message received | Social | Task on the Lead or Contact |
| Social conversation tag added | Social | Task plus optional OutboundSync fields on the Lead or Contact |
Event names come from the HotHawk webhooks OutboundSync receives. See the HotHawk event reference.
Count HotHawk opportunity-created Tasks by campaign to see which outreach produces deals.
Compare received-email and thread-done Tasks to see how quickly replies are handled.
Fire a Salesforce Flow when HotHawk marks an opportunity won.
The options teams weigh before they commit a production sync.
| Option | What it does | Trade-off |
|---|---|---|
| Zapier, Make, or n8nCompare integration platforms | Catch HotHawk webhooks and write each event to Salesforce 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 buy | Write your own service against the HotHawk and Salesforce APIs. | You own matching, deduplication, API limits, and every upstream schema change. |
| OutboundSync | Pre-built email and social activity sync into Salesforce Leads and Contacts. | Self-serve setup, searchable event logs, and support from the team that maintains the connector. |
A Salesforce admin creates an External Client App, then connects it in OutboundSync and picks Task or EmailMessage logging.
The OutboundSync team creates your HotHawk source with you and points HotHawk's webhooks at it.
Pick which HotHawk events to log, whether they write Tasks or EmailMessage records, and which OutboundSync fields to fill.
Trigger one HotHawk event and confirm it on a real Lead or Contact.
Turn on the source and start building Salesforce reports, dashboards, and Flows on real HotHawk data.
Needs webhook access
OutboundSync receives HotHawk activity through webhooks. Confirm your HotHawk plan includes webhook access, or ask us to check during setup.
OutboundSync works across Salesforce editions. The difference is API capacity: plan for roughly 6 API calls per sent email once replies and status events are counted.
| Edition | Fit | What to know |
|---|---|---|
| Professional | Limited support - API limits may restrict ongoing sync. |
|
| EnterpriseMost common | Recommended - Best balance of capability, API capacity, and cost. |
|
| Unlimited | Ideal - Best for scale and high activity volume. |
|
Millions of activities synced every month
EliseAI
Yotpo
Ona
HG Insights
Finout
HologramTutorials, case studies, and updates related to HotHawk.
OutboundSync now syncs HotHawk social messages and conversation tag events into HubSpot and Salesforce alongside existing email events.
Harris Kenny
A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.
