CRM connectors
Native CRM connector status
This page is generated from the same connector registry the app uses. A connector is only called available after it passes live acceptance with the provider. Until then it is in validation: the adapter exists and can be tested with credentials you supply, but it is not a generally available, self-serve integration.
Last reviewed:
What works today
Signed webhooks (Starter and Pro) and the REST API (Pro) send submissions to any system that accepts HTTPS requests, including these CRMs through their own APIs or an automation tool you already use.
| Connector | Status | Authentication | Objects | Setup path (validation) |
|---|---|---|---|---|
| Salesforce | In validation | OAuth 2.0 | Contact, Account, Lead, Opportunity | Use the secure Connect with Salesforce flow. An administrator must configure the Klarstig OAuth app on the test deployment first. |
| HubSpot | In validation | OAuth 2.0 | contacts, companies, deals | Use the secure Connect with HubSpot flow. An administrator must configure the Klarstig OAuth app on the test deployment first. |
| Zoho CRM | In validation | OAuth 2.0 | Contacts, Accounts, Leads, Deals | Use the secure Connect with Zoho CRM flow. An administrator must configure the Klarstig OAuth app on the test deployment first. |
| Pipedrive | In validation | OAuth 2.0 | persons, organizations, deals | Use the secure Connect with Pipedrive flow. An administrator must configure the Klarstig OAuth app on the test deployment first. |
| ActiveCampaign | In validation | API key / token | Contacts | ActiveCampaign Settings → Developer: enter the API URL and API key here. The current validation scope is standard contact fields; account, deal and custom-field writes remain blocked. |
| Zendesk | In validation | OAuth 2.0 | users, organizations, tickets | Enter your https://subdomain.zendesk.com URL, then connect with OAuth. Local clients are for development; customer distribution requires Zendesk Global OAuth approval. |
| Insightly | In validation | API key / token | Contacts, Organisations, Leads, Opportunities | Insightly User Settings → API: enter the pod-specific API URL and API key here. Standard fields are supported; custom fields require a reviewed nested-field mapping. |
| Keap | In validation | OAuth 2.0 | Contact, Company | Use the secure Connect with Keap flow. An administrator must configure the Klarstig OAuth app on the test deployment first. |
| EngageBay | In validation | API key / token | Contacts, Companies, Deals | EngageBay Account Settings → API & Tracking Code: enter the REST API key here, not the JavaScript key. Standard contact, company and deal fields are implemented for validation. Contacts match email; companies match name or URL; deals match name. |
How a connector becomes available: the provider app registration (OAuth client credentials) must be issued to Klarstig, then a live acceptance test must pass. Neither has been completed for these connectors, so none is marked available.