Skip to content

Furnace

When to use this guide: Read this before configuring Furnace with OutboundSync to confirm what the integration covers today.

OutboundSync connects Furnace to HubSpot, Salesforce, and supported beta CRMs as a one-way sync for cold email campaign activity. Furnace push webhooks are received by OutboundSync and written to the matching CRM record as structured outbound activity.

What this integration does

Section titled “What this integration does”

Furnace builds and runs cold outbound email systems for B2B teams. OutboundSync receives Furnace webhook events and maps them to standard CRM fields, so sends, replies, category updates, and bounces stay visible on the matching CRM record without manual exports.

Contact matching uses the email address in each Furnace payload. Campaign metadata, timestamps, and event context are preserved where Furnace includes them and OutboundSync maps them.

What syncs into your CRM

Section titled “What syncs into your CRM”

Furnace sends four webhook event types. OutboundSync maps each to a canonical activity type on the matching CRM record:

Furnace event (type)OutboundSync activityWhat syncs
email.sentEmail sentOutbound send logged to CRM (subject, campaign, mailbox)
reply.receivedEmail replyInbound reply body and metadata
reply.categorizedLead category updatedReply category or disposition signal
bounce.detectedEmail bounceBounce logged to the matched lead email

Where it syncs

Section titled “Where it syncs”
  • HubSpot — direct integration
  • Salesforce — direct integration
  • Close — supported during the current Close beta
  • Attio — supported during the current Attio beta
  • HighLevel — supported during the current HighLevel beta
  • Pipedrive — supported during the current Pipedrive beta

Combo-specific landing pages and field mappings for Furnace are not yet published. Use this page for the current support scope.

Scope and current limitations

Section titled “Scope and current limitations”
  • One-way sync. Data flows Furnace → CRM. Updates in your CRM are not written back to Furnace.
  • Email channel only. Social, phone, and inbox-management events are out of scope.
  • Push webhooks only. Furnace does not require an API key in OutboundSync; configure webhook delivery from Furnace to your OutboundSync source URL.
  • No filtered-events mode. All supported Furnace events sync when received; approved-events filtering is not available for this platform.
  • Four events only. Opens, clicks, and unsubscribes are out of scope.
  • Guided setup. Setup is currently handled with the OutboundSync team during onboarding. See the Furnace email-activity webhook docs for webhook configuration on the Furnace side.

Get help and next steps

Section titled “Get help and next steps”