Integrations
Ken + Close Integration
Ken sends five email events (sent, clicked, replied, interested and unsubscribed) to the matching Close lead through OutboundSync, a partner app that supports Close in beta, in near real time.
What the Integration Does
In short Sends Ken email events to Close through OutboundSync, one way.
Ken does not connect to Close directly today. OutboundSync, a partner app, receives Ken's webhooks and syncs each email event into the matching Close lead as email activity. It matches by the email address in each event.
Your team sees sends, clicks, replies, interested leads and unsubscribes in the Close lead, next to the rest of your sales activity.
What Syncs
In short One-way: Ken to Close.
| Object | Direction | Frequency |
|---|---|---|
| Email sent (email_sent) | Ken to Close | Near real time |
| Lead clicked a link (lead_clicked) | Ken to Close | Near real time |
| Lead replied, with the reply body (lead_replied) | Ken to Close | Near real time |
| Lead interested (lead_interested) | Ken to Close | Near real time |
| Lead unsubscribed (lead_unsubscribed) | Ken to Close | Near real time |
| Reply opened by the lead (reply_opened) | Ken to Close | Near real time, if added through the Ken API |
Checked against production on 2026-10-17.
How to Connect Close
In short Connect Close in 5 steps.
Open Close in Ken
In Ken, open Settings, then Integrations, and pick Close under CRM. Click Continue to OutboundSync.
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.
Connect Close in OutboundSync
Connect your Close account in OutboundSync. It matches each Ken event to a Close lead by email address.
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.
Check the first events
Send a campaign email and confirm the email sent event shows in the Close lead.
Use Cases
In short 3 ways teams use Ken with Close.
- See every cold email touch in the Close lead without exporting from Ken.
- Spot interested leads in Close in near real time, as Ken marks them.
- Check for a Ken unsubscribe in Close before anyone on your team emails that lead again.
Limits
In short One way only: Ken does not read Close, and changes in Close do not flow back to Ken.
- One way only: Ken does not read Close, and changes in Close 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, and its Close connector is in beta too.
- 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 confirms the exact Close event coverage with you during onboarding.
- 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 Close.
Does Ken sync with Close directly?
Not today. Ken sends webhooks and OutboundSync writes them to Close. Native two-way sync between Ken CRM (Coming) and Close is in development.
Which Ken events reach Close?
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 Close data flow back into Ken?
No. The sync is one way, from Ken to Close.
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 Close
Point a Ken webhook at your OutboundSync source URL and every campaign email event reaches Close.
- Open Settings, then Integrations, then Webhooks.
- Click Add endpoint and paste your OutboundSync source URL.
- Select the campaign events and save.
- Module
- Campaigns
- Open in Ken
- app.ken.so/settings/integrations
- Cost
- Webhooks are free on every Ken plan
The new Ken opens to the waiting list in batches.
Related
- All Ken integrations
Every live integration by category
- Ken + HubSpot Integration
Sends Ken email events to HubSpot through OutboundSync, one way.
- Ken + Salesforce Integration
Sends Ken email events to Salesforce through OutboundSync, one way.
- Ken + Pipedrive Integration
Sends Ken email events to Pipedrive through OutboundSync, one way.
- Ken + Attio Integration
Sends Ken email events to Attio through OutboundSync, one way.
- Ken + GoHighLevel Integration
Sends Ken email events to GoHighLevel through OutboundSync, one way.
- Ken + Google Workspace Integration
Send campaigns from your Gmail and Google Workspace inboxes and read replies in Ken.
- Ken features
What Ken runs before events reach your CRM
- Ken pricing
Plans and credit prices
Sources
| Source | Checked |
|---|---|
| OutboundSync: Ken AI integration | |
| OutboundSync docs: Ken AI guide | |
| OutboundSync: Close integration | |
| OutboundSync pricing | |
| Ken API v2 developer docs (webhooks) |
Changelog
- Page published.