Einstein Activity Capture connects each rep's Microsoft 365 or Google Workspace mailbox. Sent and received emails and calendar events are matched to the right leads, contacts, accounts and opportunities and shown on the activity timeline, with no manual logging. The Outlook and Gmail side panel shows the matching Salesforce records while you read an email, so you can log it, add a contact or open a case without leaving your inbox.
Into Salesforce
- Emails and meetings, auto-matched to records
- Contacts added in your mailbox
Out of Salesforce
- Salesforce events and contacts to your calendar and address book
- Emails sent from Salesforce with templates
What we set up
We set up the capture rules, sharing defaults and the side panel layout, and decide with you whether Activity Capture or classic email logging fits your reporting, since captured activity lives in Salesforce-managed storage rather than standard objects.
DocuSign eSignature for Salesforce lets a rep send a contract from the opportunity, quote or any record, with names, amounts and terms merged from Salesforce. As people sign, DocuSign writes status back: sent, viewed, completed, date signed. The finished PDF lands on the record.
Into Salesforce
- Envelope status and date signed
- Completed PDF attached to the record
- Values signers enter, written back to fields
Out of Salesforce
- Envelopes sent from records with merged data
- Recipients and templates chosen in Salesforce
What we set up
Envelope templates, writeback field mapping, and Flow automation, for example moving the opportunity to Closed Won and starting onboarding the moment the envelope completes.
Create proposals and quotes from an opportunity with PandaDoc tokens filled from Salesforce and the pricing table built from opportunity products. It is a true two-way sync: as the buyer edits or signs, PandaDoc updates the opportunity.
Into Salesforce
- Document status to opportunity stage
- Completed PDF saved to the record
- Pricing table edits back to opportunity products
- Fillable fields back to Salesforce fields
Out of Salesforce
- Documents created from opportunities, accounts or custom objects
- Record data into tokens and pricing tables
What we set up
Token and field mapping, status-driven automations, and custom triggers through the PandaDoc API when the standard ones do not fit. Needs Enterprise, or Professional with the API add-on.
S-Docs runs entirely inside your org, with no external servers. A button on a record generates a quote, contract or statement from a template that pulls data from any related records, then emails it or sends it for e-signature with S-Sign.
Into Salesforce
- Nothing leaves Salesforce. Generated documents attach to the record
What we set up
Template design, related-list data, conditional sections, and buttons or Flow steps that generate documents automatically.
With Breadwinner for QuickBooks installed natively in Salesforce, invoices, customers and payments exist as Salesforce records. Reps raise an invoice from the opportunity, finance sees it in QuickBooks, and payments and balances flow back to the account.
Into Salesforce
- Invoice status, payments and credit memos
- Customer balances and overdue amounts on the account
Out of Salesforce
- Customers and invoices created from Salesforce
- Products and estimates
What we set up
Object and field mapping, invoicing flows tied to stages, and when a connector is the wrong fit, a direct build on the QuickBooks API.
The same pattern as QuickBooks. Breadwinner for Xero pipes Xero contacts, invoices, payments and credit notes into native Salesforce objects in near real time, and lets you create Xero invoices from Salesforce without double entry.
Into Salesforce
- Invoices, payments and credit notes on the account
- Contact changes made in Xero
Out of Salesforce
- Invoices and contacts created from Salesforce
What we set up
Mapping Salesforce accounts to Xero contacts (one account can hold several Xero customers), invoice automation, and custom Apex against the Xero API for edge cases.
Flywire takes the payment and Salesforce stays the record of truth. From an opportunity or invoice, a rep sends a secure payment link. The customer pays on a checkout page that carries your brand, and Flywire calls back to Salesforce with the result, so a Payment record with the amount, method and reference lands on the record within seconds and the balance updates.
Into Salesforce
- Payment status, amount, method and Flywire reference as a Payment record
- Optional: a saved payment method for future invoices
Out of Salesforce
- Payment requests created from opportunities or invoices, with the customer and amount
- The branded payment link, emailed from Salesforce
What we set up
We have built this end to end: the Salesforce action and email, the branded payment page, the Flywire webhook that writes the payment back, and the reporting on top. It is the same flow shown in the hero above.
Customers, orders, products and fulfilment status flow from your store into Salesforce so sales and service see the whole picture. Most clients only need the inbound sync. Updates can be pushed back to the store when that earns its keep.
Into Salesforce
- Customers to contacts and accounts
- Orders, line items and fulfilment status
- Products and inventory
Out of Salesforce
- Optional: customer and product updates back to the store
What we set up
Choosing between an AppExchange connector and a direct webhook build, de-duplication rules, and mapping orders onto your Salesforce data model.
A submission creates or updates records in any object, including custom ones, with uploads and the submission PDF attached to the record. In the other direction, forms are prefilled from Salesforce, including live prefill that finds the matching record as someone types.
Into Salesforce
- Submissions to leads, cases, contacts or custom records
- Uploaded files and the submission PDF
Out of Salesforce
- Prefilled forms and personalised links built from Salesforce data
What we set up
Object mapping, duplicate handling, and Flow that emails a prefilled link at the right step.
The HubSpot to Salesforce connector keeps contacts, companies and deals in step in both directions. An inclusion list decides which HubSpot contacts are allowed to sync, and marketing activity shows on the Salesforce record.
Into Salesforce
- Contacts, companies and deals from HubSpot
- Marketing emails, form fills and activity
Out of Salesforce
- Leads or contacts, accounts and opportunities to HubSpot
What we set up
Lead versus contact strategy, field mapping, sync rules and the inclusion list, so the two systems stop fighting over ownership.
Leads and contacts sync into Mailchimp audiences on a schedule with the fields you choose. Engagement flows back: opens, clicks, bounces and unsubscribes appear on the lead, so sales knows who is warm.
Into Salesforce
- Opens, clicks, bounces and unsubscribes on the lead or contact
- Campaign membership
Out of Salesforce
- Leads and contacts to audiences and tags, hourly
What we set up
Audience mapping, what qualifies a record to sync, and engagement reporting inside Salesforce.
Salesforce for Slack sends record alerts to channels, a big deal closing or a case escalating, and lets people act from Slack: search records, add notes, or attach a message to a record with Add to Salesforce. Flow posts to Slack with clicks, not code.
Into Salesforce
- Messages attached to records
- Notes and updates made from Slack
Out of Salesforce
- Record alerts and digests to channels
- Salesforce channels per account or deal
What we set up
Alert rules built in Flow, channel conventions, and Agentforce answering questions in Slack.
Schedule and launch Zoom meetings from leads, contacts and events. When the meeting ends, Zoom writes attendees, duration, recording links and AI summaries back to the record as activity.
Into Salesforce
- Attendance, duration, recording and transcript links
- AI meeting summaries
Out of Salesforce
- Meetings scheduled from records
- Invites sent with Salesforce templates
What we set up
Field mapping and the page layouts that put meeting history where reps look.
When an opportunity closes, a project is created in Asana from a template with the deal data mapped in. As delivery progresses, status flows back so account managers can see it on the account without leaving Salesforce.
Into Salesforce
- Project and task status on the opportunity or account
Out of Salesforce
- Projects and tasks created from closed-won deals, with customer, value and dates
What we set up
The AppExchange app was retired in 2026, so we pick the right route for you: Asana Rules, a sync platform such as Unito, or a direct build.