--- title: "Ken + Salesforce Integration: Setup and What Syncs" description: "Connect Ken to Salesforce through OutboundSync: Ken email events sync one way in near real time. What syncs, setup steps, costs and limits." path: /integrations/salesforce family: integrations updated: 2026-10-17 html: /integrations/salesforce sources: - "https://outboundsync.com/integrations/kenai/" - "https://outboundsync.com/docs/integrations/engagement/kenai/" - "https://outboundsync.com/integrations/salesforce/" - "https://outboundsync.com/pricing/" - "https://developer.ken.so/" facts: partner: "Salesforce" status: "Live" sync_direction: "One-way: Ken to Salesforce" connects_through: "OutboundSync" plans: "Ken webhooks are on every plan, Free included. OutboundSync bills separately." ken_module: "Campaigns" --- # Ken + Salesforce Integration Ken sends five email events (sent, clicked, replied, interested and unsubscribed) to the matching Salesforce lead or contact through OutboundSync, a partner app, in near real time. ## What the Integration Does **In short:** Sends Ken email events to Salesforce through OutboundSync, one way. Ken does not connect to Salesforce directly today. OutboundSync, a partner app, receives Ken's webhooks and logs each email event as a Task or an EmailMessage record, depending on your setup, on the matching Salesforce lead or contact. It matches by the email address in each event. Your team sees sends, clicks, replies, interested leads and unsubscribes in the Salesforce lead or contact activity, next to the rest of your sales activity. Salesforce Flows can act on that activity, for example to assign an owner or send a notification. ## What Syncs **In short:** One-way: Ken to Salesforce. **What syncs between Ken and Salesforce** | Object | Direction | Frequency | | --- | --- | --- | | Email sent (email_sent) | Ken to Salesforce | Near real time | | Lead clicked a link (lead_clicked) | Ken to Salesforce | Near real time | | Lead replied, with the reply body (lead_replied) | Ken to Salesforce | Near real time | | Lead interested (lead_interested) | Ken to Salesforce | Near real time | | Lead unsubscribed (lead_unsubscribed) | Ken to Salesforce | Near real time | | Reply opened by the lead (reply_opened) | Ken to Salesforce | Near real time, if added through the Ken API | Checked against production on 2026-10-17. ## How to Connect Salesforce **In short:** Connect Salesforce in 5 steps. 1. **Open Salesforce in Ken**: In Ken, open Settings, then Integrations, and pick Salesforce under CRM. Click Continue to OutboundSync. 2. **Book OutboundSync onboarding**: Ken AI setup is handled with the OutboundSync team during onboarding. You create a Ken AI webhook receiver in OutboundSync, and Ken delivers its webhooks to that receiver's source URL. 3. **Connect Salesforce in OutboundSync**: Connect your Salesforce account in OutboundSync. It matches each Ken event to a Salesforce lead or contact by email address. 4. **Add the webhook in Ken**: In Ken, open Settings, then Integrations, then Webhooks, and click Add endpoint. Paste your OutboundSync source URL as the Endpoint URL and select the campaign events: Email sent, Lead replied, Lead interested, Lead unsubscribed and Lead clicked. 5. **Check the first events**: Send a campaign email and confirm the email sent event shows in the Salesforce lead or contact activity. ## Use Cases **In short:** 4 ways teams use Ken with Salesforce. - See every cold email touch in the Salesforce lead or contact activity without exporting from Ken. - Spot interested leads in Salesforce in near real time, as Ken marks them. - Trigger a Salesforce Flow when a lead replies, for example to assign an owner. - Check for a Ken unsubscribe in Salesforce before anyone on your team emails that lead again. ## Limits **In short:** One way only: Ken does not read Salesforce, and changes in Salesforce do not flow back to Ken. - One way only: Ken does not read Salesforce, and changes in Salesforce do not flow back to Ken. - Email only: LinkedIn activity from Ken campaigns does not sync. - OutboundSync lists the Ken AI integration as a beta. HubSpot and Salesforce are its direct, non-beta CRMs. - Ken's Settings screen offers five of the six events OutboundSync maps. To also send reply opens (reply_opened), add the endpoint through the Ken API instead. - OutboundSync syncs every supported event it receives. It has no event filter for Ken. - OutboundSync is a separate subscription, from $99 a month for 2,000 sent messages (checked 2026-10-17). Opens, clicks and replies are not billed. ## Frequently Asked Questions **In short:** 4 common questions about Ken and Salesforce. ### Does Ken sync with Salesforce directly? Not today. Ken sends webhooks and OutboundSync writes them to Salesforce. Native two-way sync between Ken CRM (Coming) and Salesforce is in development. ### Which Ken events reach Salesforce? Five from Ken's Settings screen: email sent, lead replied (with the reply body), lead interested, lead unsubscribed and lead clicked. OutboundSync also maps reply opened, which you can subscribe to through the Ken API. ### Does Salesforce data flow back into Ken? No. The sync is one way, from Ken to Salesforce. ### What does it cost? Ken's webhooks are included on every plan, Free included. OutboundSync starts at $99 a month for 2,000 sent messages and bills only sent messages (checked 2026-10-17). ## Do this in Ken ### Send Ken activity to Salesforce Point a Ken webhook at your OutboundSync source URL and every campaign email event reaches Salesforce. 1. Open Settings, then Integrations, then Webhooks. 2. Click Add endpoint and paste your OutboundSync source URL. 3. Select the campaign events and save. - Link: [Send Ken activity to Salesforce](https://app.ken.so/settings/integrations) - Cost: Webhooks are free on every Ken plan ## Related - [All Ken integrations](/integrations): Every live integration by category - [Ken + HubSpot Integration](/integrations/hubspot): Sends Ken email events to HubSpot through OutboundSync, one way. - [Ken + Pipedrive Integration](/integrations/pipedrive): Sends Ken email events to Pipedrive through OutboundSync, one way. - [Ken + Attio Integration](/integrations/attio): Sends Ken email events to Attio through OutboundSync, one way. - [Ken + Close Integration](/integrations/close): Sends Ken email events to Close through OutboundSync, one way. - [Ken + GoHighLevel Integration](/integrations/gohighlevel): Sends Ken email events to GoHighLevel through OutboundSync, one way. - [Ken + Google Workspace Integration](/integrations/google-workspace): Send campaigns from your Gmail and Google Workspace inboxes and read replies in Ken. - [Ken features](/features): What Ken runs before events reach your CRM - [Ken pricing](/pricing): Plans and credit prices ## Sources | Source | URL | Checked | | --- | --- | --- | | OutboundSync: Ken AI integration | https://outboundsync.com/integrations/kenai/ | 2026-10-17 | | OutboundSync docs: Ken AI guide | https://outboundsync.com/docs/integrations/engagement/kenai/ | 2026-10-17 | | OutboundSync: Salesforce integration | https://outboundsync.com/integrations/salesforce/ | 2026-10-17 | | OutboundSync pricing | https://outboundsync.com/pricing/ | 2026-10-17 | | Ken API v2 developer docs (webhooks) | https://developer.ken.so/ | 2026-10-17 | ## Changelog - 2026-10-17: Page published.