Ken AI
When to use this guide: Read this before configuring Ken AI with OutboundSync to confirm what the integration covers today.
OutboundSync connects Ken AI to HubSpot, Salesforce, and supported beta CRMs as a one-way sync for cold email campaign activity. Ken AI push webhooks are received by OutboundSync and written to the matching CRM record as structured outbound activity.
What this integration does
Section titled “What this integration does”Ken AI is an AI-powered cold email platform for building, personalizing, and sending B2B outbound campaigns. OutboundSync receives Ken AI webhook events and maps them to standard CRM fields, so sends, engagement, replies, and disposition signals stay visible in your CRM timeline without manual exports.
Contact matching uses the email address in each Ken AI payload. Campaign metadata, timestamps, and event context are preserved where Ken AI includes them.
What syncs into your CRM
Section titled “What syncs into your CRM”Ken AI sends six webhook event types. OutboundSync maps each to a canonical activity type on the matching CRM record:
Ken AI event (eventType) | OutboundSync activity | What syncs |
|---|---|---|
email_sent | Email sent | Outbound email send logged to CRM |
reply_opened | Email open | Reply-thread open tracked |
lead_clicked | Link click | Link click on campaign email |
lead_replied | Email reply | Inbound reply body and metadata |
lead_interested | Lead category updated | Positive interest or disposition signal |
lead_unsubscribed | Unsubscribe | Opt-out or unsubscribe event |
Where it syncs
Section titled “Where it syncs”- HubSpot — direct integration
- Salesforce — direct integration
- Close — supported during the current Close beta
- Attio — supported during the current Attio beta
- HighLevel — supported during the current HighLevel beta
- Pipedrive — supported during the current Pipedrive beta
Combo-specific landing pages and field mappings for Ken AI are not yet published. Use this page for the current support scope.
Scope and current limitations
Section titled “Scope and current limitations”- One-way sync. Data flows Ken AI → CRM. Updates in your CRM are not written back to Ken AI.
- Email channel only. Social, phone, and inbox-management events are out of scope.
- Push webhooks only. Ken AI does not require an API key in OutboundSync; configure webhook delivery from Ken AI to your OutboundSync receiver URL.
- No filtered-events mode. All supported Ken AI events sync when received; approved-events filtering is not available for this platform.
- Guided setup. Setup is currently handled with the OutboundSync team during onboarding. See the Ken AI developer docs for webhook configuration on the Ken AI side.
Get help and next steps
Section titled “Get help and next steps”- Talk to the team to start a Ken AI connection
- Ken AI integration page — full details, FAQ, and pricing context
- Engagement platform docs — browse related platform setup guides