Skip to content

Drippi

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

OutboundSync connects Drippi to HubSpot and Salesforce as a one-way sync, logging X (Twitter) direct message activity to the matching contact or lead record.

What this integration does

Section titled “What this integration does”

Drippi is built for X (Twitter) DM outreach at scale. OutboundSync receives Drippi webhook events and turns them into structured CRM activities — so social outreach is attributed alongside email and other channels in your pipeline reporting.

Contact matching and deduplication are handled automatically. Campaign metadata, timestamps, and message context are written to the CRM record so you can build workflows and route leads based on engagement.

What syncs into your CRM

Section titled “What syncs into your CRM”
  • DM sends and replies as activity events on the contact record
  • Campaign IDs, names, and timestamps on each activity
  • Message context for the DM thread
  • Contact matching and deduplication against existing CRM records
  • Block list sync from HubSpot or Salesforce back into Drippi exclusions

Where it syncs

Section titled “Where it syncs”
  • HubSpot — direct integration
  • Salesforce — direct integration

Combo-specific landing pages and field mappings for Drippi are not yet published. The Drippi integration page covers current capabilities.

Scope and current limitations

Section titled “Scope and current limitations”
  • One-way sync. Data flows Drippi → CRM. Updates in HubSpot or Salesforce are not written back to Drippi, except for the block list sync.
  • Social channel only. Drippi covers X (Twitter) DMs; email and other channels are out of scope.
  • Beta. The integration is live as a direct Beta. Setup is currently handled by the OutboundSync team during onboarding.

Get help and next steps

Section titled “Get help and next steps”