Partner spotlight: GetSales
GetSales is a team-centric multichannel outreach and GTM automation platform. See how it connects to OutboundSync to sync activity into your CRM.
Jason Ma
GetSales → Salesforce
GetSales + Salesforce integration
Bring GetSales multichannel outreach into Salesforce. OutboundSync logs email and social steps as Tasks on the Lead or Contact, so reports see the whole sequence.
BetaOne-way syncEmail and social
GetSales + Salesforce at a glance
GetSales connects to Salesforce through OutboundSync. Email sends and replies, connection requests and acceptances, and standard or premium social messages and replies from GetSales are logged on the matching Lead or Contact as Tasks, or as EmailMessage records for email. The OutboundSync team sets up the GetSales source with you.
| Status | Beta (GetSales setup is guided by the OutboundSync team) |
|---|---|
| Channels | Email and social |
| Direction | One-way, GetSales → Salesforce |
| Salesforce records | Leads, or Contacts and Accounts |
| Block lists | Not available for this pairing |
| GetSales plan | Needs webhook access |
| Setup | Self-serve: create an External Client App, then connect it in OutboundSync; GetSales source set up with our team |
Salesforce reporting tends to over-credit email, because email is the only channel that shows up. GetSales sequences lean on social just as much. Logging both as Tasks through OutboundSync gives your reports a fair picture of which channel starts the conversation and which one closes it.
Template the Task subject with the event type and campaign, and social activity becomes as easy to filter as email. A Flow can fire on an accepted connection or a social reply, and list views can show which Leads are engaged on social before they ever answer an email.
What syncs from GetSales to Salesforce
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 | Task or EmailMessage on the Lead or Contact | |
| Email reply received | Task or EmailMessage on the Lead or Contact | |
| Connection request sent | Social | Task on the Lead or Contact |
| Connection request accepted | Social | Task on the Lead or Contact |
| Social message sent— Standard and premium messages | Social | Task on the Lead or Contact |
| Social reply received— Standard and premium message replies | Social | Task on the Lead or Contact |
| Contact enriched or exported— Logged as a lead category update | Task plus optional OutboundSync fields on the Lead or Contact |
Event names come from the GetSales webhooks OutboundSync receives. See the GetSales event reference.
What teams do with GetSales + Salesforce
Credit social touches
Report on opportunities where a GetSales social reply came before the first meeting.
Flow on accepted connections
Trigger a Salesforce Flow when a GetSales connection request is accepted.
One Lead timeline
Email and social Tasks from GetSales sit together on the same Lead or Contact.
Ways to connect GetSales and Salesforce
The options teams weigh before they commit a production sync.
| Option | What it does | Trade-off |
|---|---|---|
| Zapier, Make, or n8nCompare integration platforms | Catch GetSales 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 GetSales 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. |
How to set up GetSales + Salesforce
Step 1: Connect Salesforce
A Salesforce admin creates an External Client App, then connects it in OutboundSync and picks Task or EmailMessage logging.
Step 2: Connect GetSales
The OutboundSync team creates your GetSales source with you and points GetSales's webhooks at it.
Step 3: Choose events and fields
Pick which GetSales events to log, whether they write Tasks or EmailMessage records, and which OutboundSync fields to fill.
Step 4: Send a test event
Trigger one GetSales event and confirm it on a real Lead or Contact.
Step 5: Go live
Turn on the source and start building Salesforce reports, dashboards, and Flows on real GetSales data.
Plan requirements
GetSales plan
Needs webhook access
OutboundSync receives GetSales activity through webhooks. Confirm your GetSales plan includes webhook access, or ask us to check during setup.
Salesforce
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.
Which Salesforce edition you need
| 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. |
|
Related integrations and guides
GetSales with other CRMs
Other outbound tools for Salesforce
Millions of activities synced every month
EliseAI
Yotpo
Ona
HG Insights
Finout
HologramGetSales + Salesforce FAQ
What GetSales activity does OutboundSync sync to Salesforce?
Email sent, email reply received, connection request sent, connection request accepted, social message sent, social reply received, and contact enriched or exported.Which Salesforce records does it write to?
OutboundSync matches or creates Salesforce Leads and Contacts. GetSales events land as task or EmailMessage on the Lead or Contact; or task on the Lead or Contact; or task plus optional OutboundSync fields on the Lead or Contact. See the Salesforce data model docs for details.Can GetSales email activity be logged as EmailMessage records?
Yes. Email sends and replies can be logged as EmailMessage records or Tasks, your choice. Social activity is logged as Tasks.Is the integration one-way or two-way?
One-way. Activity flows from GetSales into Salesforce, and nothing is written back to GetSales.Do I need admin access to set it up?
A Salesforce System Administrator creates the External Client App and authorizes OAuth.Which GetSales plan do I need?
OutboundSync receives GetSales activity through webhooks. Confirm your GetSales plan includes webhook access, or ask us to check during setup.How is GetSales + Salesforce priced?
OutboundSync bills on sent messages per month. Replies, opens, clicks, and lead-category updates are not billed. Plan details are on 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.
GetSales resources
Tutorials, case studies, and updates related to GetSales.
Webinar: 3 social plays your CRM is sitting on
Join GetSales' Peter Kaliuzhny and me on July 16: 3 social selling plays to run from your CRM, plus how GetSales activity syncs into HubSpot and Salesforce.
Harris Kenny
GetSales integration now available
OutboundSync now supports beta one-way sync of GetSales email and social activity into HubSpot and Salesforce CRM.
Harris Kenny
See GetSales activity in Salesforce
A quick walkthrough with your own stack. Setup takes minutes, with no long-term contract.
