Connect the conversation layer to the systems that run the business.
Review planned and custom connection patterns for CRM, support, automation, commerce, scheduling, identity, data, and analytics. Every production connection requires an approved scope.
CRM: Customer, pipeline, and ownership. Typed records and accountable actions stay connected.
LiveCRM eventFilter individual connection records—not a wall of provider logos.
Named providers are conservatively marked Planned. Generic connection patterns remain Custom implementation until APIs, access, controls, commercial terms, and an implementation scope are approved.
Provider and product names identify intended compatibility patterns only. Their display does not represent a live connector, certification, endorsement, or partnership.
Showing 36 of 36 connection records.
HubSpot
Connect permitted customer, opportunity, activity, ownership, and follow-up data.
HubSpot connection purpose
Sales & revenue · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
HubSpot setup requirements and limitations
- Read approved customer or opportunity context
- Create or update approved records
- Attach permitted conversation outcomes
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer CRM owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Salesforce
Connect permitted customer, opportunity, activity, ownership, and follow-up data.
Salesforce connection purpose
Sales & revenue · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Salesforce setup requirements and limitations
- Read approved customer or opportunity context
- Create or update approved records
- Attach permitted conversation outcomes
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer CRM owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Pipedrive
Connect permitted customer, opportunity, activity, ownership, and follow-up data.
Pipedrive connection purpose
Sales & revenue · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Pipedrive setup requirements and limitations
- Read approved customer or opportunity context
- Create or update approved records
- Attach permitted conversation outcomes
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer CRM owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Zoho CRM
Connect permitted customer, opportunity, activity, ownership, and follow-up data.
Zoho CRM connection purpose
Sales & revenue · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Zoho CRM setup requirements and limitations
- Read approved customer or opportunity context
- Create or update approved records
- Attach permitted conversation outcomes
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer CRM owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Airtable
Connect permitted customer, opportunity, activity, ownership, and follow-up data.
Airtable connection purpose
Sales & revenue · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Airtable setup requirements and limitations
- Read approved customer or opportunity context
- Create or update approved records
- Attach permitted conversation outcomes
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer CRM owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Custom CRM API
Connect permitted customer, opportunity, activity, ownership, and follow-up data.
Custom CRM API connection purpose
Sales & revenue · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Custom CRM API setup requirements and limitations
- Read approved customer or opportunity context
- Create or update approved records
- Attach permitted conversation outcomes
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer CRM owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Zendesk
Connect permitted tickets, customer context, assignment, escalation, and resolution evidence.
Zendesk connection purpose
Customer service · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Zendesk setup requirements and limitations
- Read approved service context
- Create or update tickets
- Share permitted handoff and resolution evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer service-system owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Intercom
Connect permitted tickets, customer context, assignment, escalation, and resolution evidence.
Intercom connection purpose
Customer service · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Intercom setup requirements and limitations
- Read approved service context
- Create or update tickets
- Share permitted handoff and resolution evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer service-system owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Freshdesk
Connect permitted tickets, customer context, assignment, escalation, and resolution evidence.
Freshdesk connection purpose
Customer service · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Freshdesk setup requirements and limitations
- Read approved service context
- Create or update tickets
- Share permitted handoff and resolution evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer service-system owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
ServiceNow
Connect permitted tickets, customer context, assignment, escalation, and resolution evidence.
ServiceNow connection purpose
Customer service · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
ServiceNow setup requirements and limitations
- Read approved service context
- Create or update tickets
- Share permitted handoff and resolution evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer service-system owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Jira Service Management
Connect permitted tickets, customer context, assignment, escalation, and resolution evidence.
Jira Service Management connection purpose
Customer service · Conversation operations with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Jira Service Management setup requirements and limitations
- Read approved service context
- Create or update tickets
- Share permitted handoff and resolution evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer service-system owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Custom ticketing
Connect permitted tickets, customer context, assignment, escalation, and resolution evidence.
Custom ticketing connection purpose
Customer service · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Custom ticketing setup requirements and limitations
- Read approved service context
- Create or update tickets
- Share permitted handoff and resolution evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer service-system owners authorize the data scope; Chatoner implements and validates the agreed mapping.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Make
Exchange approved events and actions with workflow and data infrastructure.
Make connection purpose
Conversation operations · Data workflows with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Make setup requirements and limitations
- Receive approved events
- Trigger approved downstream actions
- Reconcile delivery, retries, and failures
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer technical owners provide approved connection destinations; Chatoner implements, tests, and monitors the agreed pattern.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
n8n
Exchange approved events and actions with workflow and data infrastructure.
n8n connection purpose
Conversation operations · Data workflows with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
n8n setup requirements and limitations
- Receive approved events
- Trigger approved downstream actions
- Reconcile delivery, retries, and failures
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer technical owners provide approved connection destinations; Chatoner implements, tests, and monitors the agreed pattern.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Zapier
Exchange approved events and actions with workflow and data infrastructure.
Zapier connection purpose
Conversation operations · Data workflows with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Zapier setup requirements and limitations
- Receive approved events
- Trigger approved downstream actions
- Reconcile delivery, retries, and failures
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer technical owners provide approved connection destinations; Chatoner implements, tests, and monitors the agreed pattern.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Webhooks
Exchange approved events and actions with workflow and data infrastructure.
Webhooks connection purpose
Conversation operations · Data workflows with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Webhooks setup requirements and limitations
- Receive approved events
- Trigger approved downstream actions
- Reconcile delivery, retries, and failures
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer technical owners provide approved connection destinations; Chatoner implements, tests, and monitors the agreed pattern.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
REST APIs
Exchange approved events and actions with workflow and data infrastructure.
REST APIs connection purpose
Conversation operations · Data workflows with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
REST APIs setup requirements and limitations
- Receive approved events
- Trigger approved downstream actions
- Reconcile delivery, retries, and failures
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer technical owners provide approved connection destinations; Chatoner implements, tests, and monitors the agreed pattern.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Data warehouse
Exchange approved events and actions with workflow and data infrastructure.
Data warehouse connection purpose
Conversation operations · Data workflows with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Data warehouse setup requirements and limitations
- Receive approved events
- Trigger approved downstream actions
- Reconcile delivery, retries, and failures
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer technical owners provide approved connection destinations; Chatoner implements, tests, and monitors the agreed pattern.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Shopify
Connect approved order, payment-context, appointment, availability, and booking workflows.
Shopify connection purpose
Commerce & scheduling · Customer service with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Shopify setup requirements and limitations
- Read approved commerce or scheduling context
- Create approved appointments or workflow updates
- Return permitted status and outcome evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer commerce or scheduling owners authorize the scope; Chatoner implements and validates the workflow.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
WooCommerce
Connect approved order, payment-context, appointment, availability, and booking workflows.
WooCommerce connection purpose
Commerce & scheduling · Customer service with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
WooCommerce setup requirements and limitations
- Read approved commerce or scheduling context
- Create approved appointments or workflow updates
- Return permitted status and outcome evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer commerce or scheduling owners authorize the scope; Chatoner implements and validates the workflow.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Stripe
Connect approved order, payment-context, appointment, availability, and booking workflows.
Stripe connection purpose
Commerce & scheduling · Customer service with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Stripe setup requirements and limitations
- Read approved commerce or scheduling context
- Create approved appointments or workflow updates
- Return permitted status and outcome evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer commerce or scheduling owners authorize the scope; Chatoner implements and validates the workflow.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Calendars
Connect approved order, payment-context, appointment, availability, and booking workflows.
Calendars connection purpose
Commerce & scheduling · Customer service with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Calendars setup requirements and limitations
- Read approved commerce or scheduling context
- Create approved appointments or workflow updates
- Return permitted status and outcome evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer commerce or scheduling owners authorize the scope; Chatoner implements and validates the workflow.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Booking systems
Connect approved order, payment-context, appointment, availability, and booking workflows.
Booking systems connection purpose
Commerce & scheduling · Customer service with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Booking systems setup requirements and limitations
- Read approved commerce or scheduling context
- Create approved appointments or workflow updates
- Return permitted status and outcome evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer commerce or scheduling owners authorize the scope; Chatoner implements and validates the workflow.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Order platforms
Connect approved order, payment-context, appointment, availability, and booking workflows.
Order platforms connection purpose
Commerce & scheduling · Customer service with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Order platforms setup requirements and limitations
- Read approved commerce or scheduling context
- Create approved appointments or workflow updates
- Return permitted status and outcome evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer commerce or scheduling owners authorize the scope; Chatoner implements and validates the workflow.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
SSO
Connect approved identity, authorization, provisioning, audit, and secret-management patterns.
SSO connection purpose
Security & governance · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
SSO setup requirements and limitations
- Authorize approved identities or applications
- Apply agreed access or provisioning changes
- Export permitted audit evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer identity and security owners approve every scope; Chatoner implements within the agreed control boundary.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
SCIM
Connect approved identity, authorization, provisioning, audit, and secret-management patterns.
SCIM connection purpose
Security & governance · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
SCIM setup requirements and limitations
- Authorize approved identities or applications
- Apply agreed access or provisioning changes
- Export permitted audit evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer identity and security owners approve every scope; Chatoner implements within the agreed control boundary.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
OAuth
Connect approved identity, authorization, provisioning, audit, and secret-management patterns.
OAuth connection purpose
Security & governance · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
OAuth setup requirements and limitations
- Authorize approved identities or applications
- Apply agreed access or provisioning changes
- Export permitted audit evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer identity and security owners approve every scope; Chatoner implements within the agreed control boundary.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Role-based access
Connect approved identity, authorization, provisioning, audit, and secret-management patterns.
Role-based access connection purpose
Security & governance · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Role-based access setup requirements and limitations
- Authorize approved identities or applications
- Apply agreed access or provisioning changes
- Export permitted audit evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer identity and security owners approve every scope; Chatoner implements within the agreed control boundary.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Audit exports
Connect approved identity, authorization, provisioning, audit, and secret-management patterns.
Audit exports connection purpose
Security & governance · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Audit exports setup requirements and limitations
- Authorize approved identities or applications
- Apply agreed access or provisioning changes
- Export permitted audit evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer identity and security owners approve every scope; Chatoner implements within the agreed control boundary.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Secrets vault
Connect approved identity, authorization, provisioning, audit, and secret-management patterns.
Secrets vault connection purpose
Security & governance · Conversation operations with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Secrets vault setup requirements and limitations
- Authorize approved identities or applications
- Apply agreed access or provisioning changes
- Export permitted audit evidence
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer identity and security owners approve every scope; Chatoner implements within the agreed control boundary.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
GA4
Send permitted conversation activity and outcomes to approved analytics destinations.
GA4 connection purpose
Analytics & insights · Sales & revenue with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
GA4 setup requirements and limitations
- Export approved events or aggregates
- Map shared measurement definitions
- Monitor delivery and reconciliation
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer data owners approve events and destinations; Chatoner implements and validates the agreed export.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
PostHog
Send permitted conversation activity and outcomes to approved analytics destinations.
PostHog connection purpose
Analytics & insights · Sales & revenue with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
PostHog setup requirements and limitations
- Export approved events or aggregates
- Map shared measurement definitions
- Monitor delivery and reconciliation
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer data owners approve events and destinations; Chatoner implements and validates the agreed export.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Looker
Send permitted conversation activity and outcomes to approved analytics destinations.
Looker connection purpose
Analytics & insights · Sales & revenue with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Looker setup requirements and limitations
- Export approved events or aggregates
- Map shared measurement definitions
- Monitor delivery and reconciliation
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer data owners approve events and destinations; Chatoner implements and validates the agreed export.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Power BI
Send permitted conversation activity and outcomes to approved analytics destinations.
Power BI connection purpose
Analytics & insights · Sales & revenue with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Power BI setup requirements and limitations
- Export approved events or aggregates
- Map shared measurement definitions
- Monitor delivery and reconciliation
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer data owners approve events and destinations; Chatoner implements and validates the agreed export.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Tableau
Send permitted conversation activity and outcomes to approved analytics destinations.
Tableau connection purpose
Analytics & insights · Sales & revenue with 3 supported actions in an approved scope.
The named provider is an intended connection pattern, not a live or prebuilt connector.
Tableau setup requirements and limitations
- Export approved events or aggregates
- Map shared measurement definitions
- Monitor delivery and reconciliation
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The named provider is an intended connection pattern, not a live or prebuilt connector.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer data owners approve events and destinations; Chatoner implements and validates the agreed export.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Custom BI
Send permitted conversation activity and outcomes to approved analytics destinations.
Custom BI connection purpose
Analytics & insights · Sales & revenue with 3 supported actions in an approved scope.
The connection requires an approved, customer-specific implementation scope.
Custom BI setup requirements and limitations
- Export approved events or aggregates
- Map shared measurement definitions
- Monitor delivery and reconciliation
- Approved purpose and data scope
- Supported APIs and authorized credentials
- Security, commercial, testing, and fallback review
- The connection requires an approved, customer-specific implementation scope.
- API access, permissions, commercial terms, security review, testing, monitoring, and fallback behavior must be confirmed.
- Setup responsibility
- Customer data owners approve events and destinations; Chatoner implements and validates the agreed export.
- Confirmed markets
- No public market coverage is confirmed.
- Confirmed plan requirements
- Confirmed during the approved scope.
- Last verified
- 2026-08-10
Current provider documentation and applicable legal requirements must be reviewed before production use.
Connect scheduling, meeting methods, customer channels, outcomes, automation, and AI with clear boundaries.
Each connection needs an approved purpose, authorization, owner, data scope, health check, and safe fallback.
Calendar & scheduling
Google Calendar, Outlook / Microsoft 365, Calendly, availability, conflicts, time zones, and invitations.
Meeting methods
Chatoner Meet, Google Meet, Microsoft Teams, Phone Call, and Physical meeting details by approved scope.
Customer channels
The original message surface carries permitted context into the meeting and receives reviewed follow-up.
CRM & outcomes
Contacts, opportunities, appointments, orders, payments, and support outcomes provide a permitted source of truth.
Automation
Reviewed decisions and actions can trigger governed workflows with clear retry, fallback, and ownership.
AI model provider
Preparation, transcription, summaries, actions, and insight require approved data, provider, access, retention, and review rules.
Use events and actions with explicit ownership and failure handling.
An integration should have the minimum access required for a defined job.
- Separate development, test, and production credentials
- Scoped OAuth or API permissions
- Encrypted secret storage and rotation
- Webhook signature verification
- Idempotency and replay protection
- Data mapping and minimization
- Audit trail for configuration and use
Credential boundary
Never place private provider, CRM, payment, or AI keys directly in a public front-end bundle.
Least privilege
Request only the scopes required for the approved workflow and customer context.
Webhook trust
Verify signatures, timestamps, source, schema, and replay protection before processing.
Recovery
Use retries, dead-letter handling, reconciliation, alerts, and named resolution ownership.
Know when customer context or downstream actions stop flowing.
Healthy, degraded, disconnected, or configuration required
Timestamp, records, errors, and owner
External action and reconciliation
Alert, impact, retry, resolution, and postmortem
APIs, scopes, commercial terms, data residency, provider approval, implementation effort, and recovery ownership are confirmed before launch.