Provider Integration Catalog¶
This catalog is generated from serialized metadata in @cognidesk/integration-catalog. It renders the target split provider packages, manifest imports, runtime imports, and integrations/{category}/{provider} workspace paths without importing provider runtime modules during docs generation.
@cognidesk/voice-websocket is not listed here because it is the browser-facing Cognidesk voice transport, not an external Provider Integration. OpenAI Realtime voice is listed as @cognidesk/integration-voice-openai because it can be the entry channel and the LLM-backed realtime session. Speech Providers such as ElevenLabs, Azure Speech, AWS Speech, Google Cloud Speech, and Deepgram can also back Cognidesk voice sessions while the Cognidesk Agent Model Set remains the background LLM.
| Category | Provider count | Packages |
|---|---|---|
| Cobrowsing | 1 | @cognidesk/integration-cobrowsing-cognidesk |
| Community | 1 | @cognidesk/integration-community-forum |
| Contact Center | 12 | @cognidesk/integration-contact-center-8x8@cognidesk/integration-contact-center-aircall@cognidesk/integration-contact-center-amazon-connect@cognidesk/integration-contact-center-five9@cognidesk/integration-contact-center-genesys-cloud@cognidesk/integration-contact-center-genesys-engage@cognidesk/integration-contact-center-genesys-pureconnect@cognidesk/integration-contact-center-nextiva@cognidesk/integration-contact-center-nice-cxone@cognidesk/integration-contact-center-ringcentral@cognidesk/integration-contact-center-talkdesk@cognidesk/integration-contact-center-zoom |
| Ecommerce | 2 | @cognidesk/integration-ecommerce-shopify@cognidesk/integration-ecommerce-stripe |
| 6 | @cognidesk/integration-email-ses@cognidesk/integration-email-gmail@cognidesk/integration-email-imap@cognidesk/integration-email-mailgun@cognidesk/integration-email-outlook@cognidesk/integration-email-postmark |
|
| Forms | 1 | @cognidesk/integration-form-cognidesk |
| Help Center | 1 | @cognidesk/integration-help-center-cognidesk |
| Marketplace | 2 | @cognidesk/integration-marketplace-amazon@cognidesk/integration-marketplace-ebay |
| Messaging | 3 | @cognidesk/integration-messaging-discord@cognidesk/integration-messaging-rcs@cognidesk/integration-messaging-whatsapp |
| Reviews | 2 | @cognidesk/integration-review-appstore@cognidesk/integration-review-googleplay |
| SMS | 1 | @cognidesk/integration-sms-twilio |
| Social | 3 | @cognidesk/integration-social-messenger@cognidesk/integration-social-instagram@cognidesk/integration-social-tiktok |
| Ticketing | 15 | @cognidesk/integration-ticketing-freshdesk@cognidesk/integration-ticketing-front@cognidesk/integration-ticketing-gorgias@cognidesk/integration-ticketing-help-scout@cognidesk/integration-ticketing-hubspot@cognidesk/integration-ticketing-intercom@cognidesk/integration-ticketing-kustomer@cognidesk/integration-ticketing-dynamics365@cognidesk/integration-ticketing-oracle-service@cognidesk/integration-ticketing-pega-customer-service@cognidesk/integration-ticketing-salesforce@cognidesk/integration-ticketing-sap-service-cloud@cognidesk/integration-ticketing-servicenow@cognidesk/integration-ticketing-zendesk@cognidesk/integration-ticketing-zoho-desk |
| Video | 2 | @cognidesk/integration-video-whereby@cognidesk/integration-video-zoom |
| Voice Provider APIs | 9 | @cognidesk/integration-voice-aws-speech@cognidesk/integration-voice-azure-speech@cognidesk/integration-voice-deepgram@cognidesk/integration-voice-elevenlabs@cognidesk/integration-voice-sip@cognidesk/integration-voice-google-speech@cognidesk/integration-voice-openai@cognidesk/integration-voice-twilio@cognidesk/integration-voice-vonage |
| Workplace | 2 | @cognidesk/integration-workplace-teams@cognidesk/integration-workplace-slack |
Provider Modules¶
Cobrowsing¶
Cognidesk Cobrowsing¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-cobrowsing-cognidesk |
| Manifest import | @cognidesk/integration-cobrowsing-cognidesk/manifest |
| Runtime import | @cognidesk/integration-cobrowsing-cognidesk/runtime |
| Workspace | integrations/cobrowsing/cognidesk |
| Manifest ID | cobrowsing.cognidesk |
| Scope | local-protocol |
| Adapter coverage | partial |
| Implementation | local-protocol |
| Documentation | https://github.com/cognilabz/cognidesk/tree/main/packages/integrations/src/cobrowsing/cognidesk |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, receive, cobrowsing.validate-session-token, cobrowsing.verify-signed-event |
| Provider setup | required cobrowsing-session-store, cobrowsing-session-token-signing, cobrowsing-consent-policy, cobrowsing-recording-redaction-policy, cobrowsing-allowed-origins; optional cobrowsing-webhook-shared-secret |
Coverage: Coverage is limited to Cognidesk-owned local cobrowsing protocol primitives: SDK-user session store lifecycle, signed session tokens, event normalization, and HMAC signed-event parsing.
Boundary: This package provides the SDK adapter contract, readiness helpers, session lifecycle primitives, token validation, event normalization, and signed-event parsing only.
Evidence: Cognidesk cobrowsing local protocol module; CONTEXT.md Built-In Adapter definition.
Community¶
Discourse Forum¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-community-forum |
| Manifest import | @cognidesk/integration-community-forum/manifest |
| Runtime import | @cognidesk/integration-community-forum/runtime |
| Workspace | integrations/community/forum |
| Manifest ID | community.forum |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://docs.discourse.org/ |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, thread, create-provider-object, read-provider-object, search-provider-object, community.webhook-signature |
| Provider setup | required forum-base-url, forum-api-key, forum-api-username; optional forum-webhook-secret |
Coverage: Coverage is limited to Discourse-compatible topic/reply creation through posts, topic/post reads, search/latest/current-user reads, and X-Discourse-Event-Signature webhook validation.
Boundary: The SDK user chooses which forum implementation, categories, tags, moderation actions, public reply approval, and retention policies are active.
Evidence: Discourse API docs; Discourse webhook configuration and signature.
Contact Center¶
8x8 Contact Center¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-8x8 |
| Manifest import | @cognidesk/integration-contact-center-8x8/manifest |
| Runtime import | @cognidesk/integration-contact-center-8x8/runtime |
| Workspace | integrations/contact-center/8x8 |
| Manifest ID | contactCenter.8x8 |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://raw.githubusercontent.com/8x8Cloud/public-developer-docs/master/docs_oas/actions-events/8x8_contact_center_chat_api_v2.json |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, send, contact-center.call-control, update-provider-object |
| Provider setup | required 8x8-contact-center-api-base, 8x8-contact-center-api-access; optional 8x8-contact-center-routing |
Coverage: Coverage includes generated per-operation functions for 11 official machine-readable 8x8 OpenAPI specs covering Contact Center Actions/Events, Chat Gateway, public Chat API variants, campaigns, Contact Center analytics, and QMSA.
Boundary: 8x8 regional endpoints, queue/campaign IDs, contact flows, and outbound eligibility are SDK-user configuration.
Evidence: 8x8 Contact Center Chat API V2 OpenAPI; 8x8 Contact Center Dynamic Campaigns OpenAPI; 8x8 Contact Center Campaigns API OpenAPI; 8x8 Chapi Chat API OpenAPI; plus 25 more.
Aircall¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-aircall |
| Manifest import | @cognidesk/integration-contact-center-aircall/manifest |
| Runtime import | @cognidesk/integration-contact-center-aircall/runtime |
| Workspace | integrations/contact-center/aircall |
| Manifest ID | contactCenter.aircall |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developer.aircall.io/api-references/ |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff |
| Provider setup | required aircall-api-base, aircall-api-access; optional aircall-routing |
Coverage: Coverage is limited to a constructor-configured SDK-owned Aircall workflow path and the documented Aircall /v1/ping readiness check; this is not typed outbound callback/call, message, webhook, or transfer coverage.
Boundary: Aircall number ownership, callback workflows, routing, recording, transfer, messaging, webhook, and outbound consent remain SDK-user configuration.
Evidence: Aircall API References; Aircall Webhooks Guide; Aircall SMS webhook tutorial.
Amazon Connect¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-amazon-connect |
| Manifest import | @cognidesk/integration-contact-center-amazon-connect/manifest |
| Runtime import | @cognidesk/integration-contact-center-amazon-connect/runtime |
| Workspace | integrations/contact-center/amazon-connect |
| Manifest ID | contactCenter.amazon-connect |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://github.com/aws/api-models-aws/tree/main/models |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, send, transfer, read-provider-object |
| Provider setup | required amazon-connect-instance, amazon-connect-api-access |
Coverage: Coverage includes generated per-operation functions for every operation in the selected official AWS Connect-family API models bundled in aws/api-models-aws.
Boundary: Exactly one of contactFlowId, quickConnectId, or taskTemplateId should be supplied unless the task template has its own flow.
Evidence: AWS official API models for Amazon Connect family; AWS API models announcement; Amazon Connect StartTaskContact; Amazon Connect StartChatContact; plus 14 more.
Five9¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-five9 |
| Manifest import | @cognidesk/integration-contact-center-five9/manifest |
| Runtime import | @cognidesk/integration-contact-center-five9/runtime |
| Workspace | integrations/contact-center/five9 |
| Manifest ID | contactCenter.five9 |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://www.five9.com/products/capabilities/call-center-apis-and-sdks |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff |
| Provider setup | required five9-api-base, five9-api-access; optional five9-routing |
Coverage: Coverage is limited to SDK-configured handoff and readiness request paths; this is not typed outbound dialing or transfer coverage.
Boundary: Five9 domain, API product, skills, campaigns, CRM object mapping, and outbound eligibility are SDK-user configuration.
Evidence: Five9 Contact Center APIs and SDKs; Five9 development program; Five9 campaigns documentation.
Genesys Cloud CX¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-genesys-cloud |
| Manifest import | @cognidesk/integration-contact-center-genesys-cloud/manifest |
| Runtime import | @cognidesk/integration-contact-center-genesys-cloud/runtime |
| Workspace | integrations/contact-center/genesys-cloud |
| Manifest ID | contactCenter.genesys-cloud |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://api.mypurecloud.com/api/v2/docs/swagger |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, contact-center.open-messaging-ingress, send |
| Provider setup | required genesys-cloud-region, genesys-cloud-api-access; optional genesys-cloud-routing, genesys-cloud-open-messaging |
Coverage: Coverage includes generated per-operation functions for every operation in the current official Genesys Cloud Platform API Swagger exposed at /api/v2/docs/swagger.
Boundary: Genesys regions, OAuth scopes/permissions, queues, callback eligibility, Architect flows, digital integrations, and outbound policy are SDK-user configuration.
Evidence: Genesys Cloud Platform API Swagger; Genesys APIs by Service; Genesys Cloud Developer Center; Genesys Cloud API Explorer Create Callback; plus 6 more.
Genesys Engage / GMS¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-genesys-engage |
| Manifest import | @cognidesk/integration-contact-center-genesys-engage/manifest |
| Runtime import | @cognidesk/integration-contact-center-genesys-engage/runtime |
| Workspace | integrations/contact-center/genesys-engage |
| Manifest ID | contactCenter.genesys-engage |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://all.docs.genesys.com/Developer/APIbyService |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, contact-center.on-prem-configured-handoff, send |
| Provider setup | required genesys-engage-gms-base-url; optional genesys-engage-auth, genesys-engage-routing |
Coverage: Coverage includes typed Genesys Mobile Services callback creation only, typed GMS Chat API v2 customer chat lifecycle/file operations, and SDK-configured REST handoff paths for deployment-specific Genesys Engage on-premises services.
Boundary: Genesys Engage deployment topology, service names, chat version, routing targets, and authentication are SDK-user configuration.
Evidence: Genesys APIs by Service; Genesys GMS Callback Services API; Genesys GMS Chat API v2; Genesys WebChatService.
Genesys PureConnect / ICWS¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-genesys-pureconnect |
| Manifest import | @cognidesk/integration-contact-center-genesys-pureconnect/manifest |
| Runtime import | @cognidesk/integration-contact-center-genesys-pureconnect/runtime |
| Workspace | integrations/contact-center/genesys-pureconnect |
| Manifest ID | contactCenter.genesys-pureconnect |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://all.docs.genesys.com/Developer/APIbyService |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, contact-center.pureconnect-session |
| Provider setup | required genesys-pureconnect-icws-base-url; optional genesys-pureconnect-session, genesys-pureconnect-routing |
Coverage: Coverage introduces Genesys PureConnect as a separate deployment/provider mode from Genesys Cloud and Genesys Engage/GMS.
Boundary: PureConnect CIC topology, ICWS version, reverse proxy/base path, authentication, Interaction Web Tools handlers, chat forms, callback forms, and routing targets are SDK-user configuration.
Evidence: Genesys APIs by Service; PureConnect ICWS connection; PureConnect ICWS interactions; PureConnect ICWS messages; plus 3 more.
Nextiva Contact Center¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-nextiva |
| Manifest import | @cognidesk/integration-contact-center-nextiva/manifest |
| Runtime import | @cognidesk/integration-contact-center-nextiva/runtime |
| Workspace | integrations/contact-center/nextiva |
| Manifest ID | contactCenter.nextiva |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://www.nextiva.com/resources/learn/rest-apis |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, nextiva.request |
| Provider setup | required nextiva-contact-center-api-base, nextiva-contact-center-api-access; optional nextiva-contact-center-authorities, nextiva-contact-center-routing |
Coverage: Coverage is limited to SDK-configured handoff/readiness requests plus a generic authenticated request helper for SDK-user-owned Nextiva endpoints; this is not typed outbound or transfer coverage.
Boundary: Nextiva tenant endpoint, queue/campaign IDs, custom API object paths, and outbound eligibility are SDK-user configuration.
Evidence: Nextiva Contact Center REST APIs; Nextiva User Service; Nextiva ACD Service; Nextiva WorkItem Service; plus 2 more.
NICE CXone¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-nice-cxone |
| Manifest import | @cognidesk/integration-contact-center-nice-cxone/manifest |
| Runtime import | @cognidesk/integration-contact-center-nice-cxone/runtime |
| Workspace | integrations/contact-center/nice-cxone |
| Manifest ID | contactCenter.nice-cxone |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://developer.niceincontact.com/API |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff |
| Provider setup | required nice-cxone-api-base, nice-cxone-api-access; optional nice-cxone-routing |
Coverage: Coverage includes generated per-operation functions for every operation in NICE CXone's public OpenAPI catalog reachable from the official API documentation pages.
Boundary: CXone API domains, business units, skills, points of contact, WFM/QM access, and outbound eligibility are SDK-user configuration.
Evidence: NICE CXone REST APIs; NICE CXone Patron API; NICE CXone Agent API; NICE CXone Digital Engagement API; plus 4 more.
RingCentral RingCX¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-ringcentral |
| Manifest import | @cognidesk/integration-contact-center-ringcentral/manifest |
| Runtime import | @cognidesk/integration-contact-center-ringcentral/runtime |
| Workspace | integrations/contact-center/ringcentral |
| Manifest ID | contactCenter.ringcentral |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://developers.ringcentral.com/engage-voice-api |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff |
| Provider setup | required ringcentral-ringcx-api-base, ringcentral-ringcx-api-access; optional ringcentral-ringcx-routing |
Coverage: Coverage includes generated per-operation functions for the current official RingCentral RingCX Voice OpenAPI spec and the official RingCentral Engage Digital OpenAPI spec.
Boundary: RingCX API product, regional endpoint, queue/campaign IDs, and outbound eligibility are SDK-user configuration.
Evidence: RingCX Voice APIs; RingCX Voice OpenAPI; RingCX Voice API docs repository; RingCX Digital APIs; plus 5 more.
Talkdesk¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-talkdesk |
| Manifest import | @cognidesk/integration-contact-center-talkdesk/manifest |
| Runtime import | @cognidesk/integration-contact-center-talkdesk/runtime |
| Workspace | integrations/contact-center/talkdesk |
| Manifest ID | contactCenter.talkdesk |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://api-docs.talkdeskapp.com/public-api |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | handoff, send, create-provider-object |
| Provider setup | required talkdesk-api-root, talkdesk-api-access; optional talkdesk-routing |
Coverage: Coverage includes generated per-operation functions for every operation in Talkdesk's official public OpenAPI bundle.
Boundary: Talkdesk API access, scopes, localized API root, callback availability, and destination mapping are SDK-user configuration.
Evidence: Talkdesk public OpenAPI bundle; Talkdesk API Endpoints; Talkdesk Contact Center API Overview; Talkdesk Callback API; plus 3 more.
Zoom Contact Center¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-contact-center-zoom |
| Manifest import | @cognidesk/integration-contact-center-zoom/manifest |
| Runtime import | @cognidesk/integration-contact-center-zoom/runtime |
| Workspace | integrations/contact-center/zoom |
| Manifest ID | contactCenter.zoom |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://developers.zoom.us/docs/api/contact-center/ |
| Directions | inbound-only |
| Capabilities | handoff |
| Provider setup | required zoom-contact-center-account, zoom-contact-center-api-access; optional zoom-contact-center-routing |
Coverage: Coverage includes generated per-operation functions for every operation in Zoom's official Contact Center REST OpenAPI spec: all 312 operations across 176 paths.
Boundary: Zoom queues, channels, campaign setup, contact eligibility, and outbound policy are SDK-user configuration.
Evidence: Zoom Contact Center APIs; Zoom Contact Center REST OpenAPI; Zoom Contact Center Webhooks; Zoom Contact Center Webhooks OpenAPI; plus 1 more.
Ecommerce¶
Shopify¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ecommerce-shopify |
| Manifest import | @cognidesk/integration-ecommerce-shopify/manifest |
| Runtime import | @cognidesk/integration-ecommerce-shopify/runtime |
| Workspace | integrations/ecommerce/shopify |
| Manifest ID | ecommerce.shopify |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://shopify.dev/docs/api/admin-graphql/latest |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, read-provider-object, search-provider-object, create-provider-object, ecommerce.graphql |
| Provider setup | required shopify-shop-domain, shopify-admin-access; optional shopify-webhook-secret |
Coverage: Official Shopify Admin GraphQL 2026-04 docs are inventoried as 792 root fields (282 QueryRoot, 510 Mutation), but this package implements only selected typed helpers plus a raw Admin GraphQL escape hatch.
Boundary: The SDK user chooses Admin API version, scopes, webhook topics, customer visibility, fulfillment behavior, consent rules, and retention policy.
Evidence: Shopify Admin GraphQL API reference; Shopify Admin GraphQL QueryRoot 2026-04 catalog; Shopify Admin GraphQL Mutation 2026-04 catalog; Shopify Admin GraphQL products query; plus 4 more.
Stripe¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ecommerce-stripe |
| Manifest import | @cognidesk/integration-ecommerce-stripe/manifest |
| Runtime import | @cognidesk/integration-ecommerce-stripe/runtime |
| Workspace | integrations/ecommerce/stripe |
| Manifest ID | ecommerce.stripe |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://docs.stripe.com/api |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, read-provider-object, search-provider-object, create-provider-object, update-provider-object, ecommerce.payments |
| Provider setup | required stripe-secret-key, stripe-webhook-signing-secret; optional stripe-publishable-key, stripe-connect-mode, stripe-restricted-key-scopes |
Coverage: Coverage includes a generated operation catalog for every operation in the official Stripe OpenAPI spec for this API version, exposed through requestOperation(operationId, ...).
Boundary: The SDK user chooses Stripe account mode, restricted-key permissions, event destinations, webhook subscriptions, checkout UI, refund policy, dispute evidence policy, consent, and retention.
Evidence: Stripe API reference; Stripe PaymentIntents API; Stripe Checkout Sessions API; Stripe Subscriptions update API; plus 2 more.
Email¶
Amazon SES¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-email-ses |
| Manifest import | @cognidesk/integration-email-ses/manifest |
| Runtime import | @cognidesk/integration-email-ses/runtime |
| Workspace | integrations/email/ses |
| Manifest ID | email.ses |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://docs.aws.amazon.com/ses/latest/APIReference-V2/Welcome.html |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, thread, attach, read-provider-object, search-provider-object, update-provider-object |
| Provider setup | required aws-access-key-id, aws-secret-access-key, aws-region; optional ses-sender-identity, ses-event-ingestion |
Coverage: Coverage includes generated per-operation functions for every operation in the official AWS SESv2 and classic SES API models.
Boundary: The SDK user chooses regions, IAM policy, sender identities, suppression policy, configuration sets, templates, event routing, webhook verification, retention, and outbound approval policy.
Evidence: AWS official SESv2 API model; AWS official classic SES API model; AWS SDK SESv2 client API reference; AWS SDK classic SES client API reference; plus 11 more.
Gmail¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-email-gmail |
| Manifest import | @cognidesk/integration-email-gmail/manifest |
| Runtime import | @cognidesk/integration-email-gmail/runtime |
| Workspace | integrations/email/gmail |
| Manifest ID | email.gmail |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | official-sdk |
| Documentation | https://www.npmjs.com/package/@googleapis/gmail |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, read-provider-object, draft, send, update-provider-object |
| Provider setup | required google-oauth-access-token |
Coverage: Coverage is intentionally scoped to normalized Cognidesk email support workflows implemented by typed handlers.
Boundary: Available operations depend on OAuth scopes, Google Workspace policy, delegated user, and mailbox state configured by the SDK user.
Evidence: @googleapis/gmail package; Gmail API Node.js quickstart; Gmail users.threads.get; Gmail users.messages.send; plus 4 more.
IMAP Mailbox¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-email-imap |
| Manifest import | @cognidesk/integration-email-imap/manifest |
| Runtime import | @cognidesk/integration-email-imap/runtime |
| Workspace | integrations/email/imap |
| Manifest ID | email.imap |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | app-supplied-connector |
| Documentation | https://datatracker.ietf.org/doc/html/rfc9051 |
| Directions | inbound-only |
| Capabilities | read-provider-object |
| Provider setup | required imap-server, imap-mailbox-credentials, imap-connector |
Coverage: Coverage is limited to credential status and SDK-user-injected mailbox readiness checks.
Boundary: This package does not bundle an IMAP client dependency; SDK users inject a connector that matches their runtime, TLS, auth, and proxy requirements.
Evidence: RFC 9051 IMAP4rev2.
Mailgun¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-email-mailgun |
| Manifest import | @cognidesk/integration-email-mailgun/manifest |
| Runtime import | @cognidesk/integration-email-mailgun/runtime |
| Workspace | integrations/email/mailgun |
| Manifest ID | email.mailgun |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://documentation.mailgun.com/docs/mailgun |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, thread, attach, read-provider-object, search-provider-object |
| Provider setup | required mailgun-api-key, mailgun-domain; optional mailgun-webhook-signing-key, mailgun-region |
Coverage: Coverage includes generated per-operation functions for every operation in Mailgun's official public OpenAPI 3.1 API reference.
Boundary: The SDK user chooses domains, routes, templates, tracking, webhook endpoints, retention, redaction, and outbound approval policy.
Evidence: Mailgun OpenAPI specification; Mailgun Messages API; Mailgun Events API; Mailgun Logs API; plus 7 more.
Microsoft Outlook¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-email-outlook |
| Manifest import | @cognidesk/integration-email-outlook/manifest |
| Runtime import | @cognidesk/integration-email-outlook/runtime |
| Workspace | integrations/email/outlook |
| Manifest ID | email.outlook |
| Scope | provider-api-subset |
| Adapter coverage | standard |
| Implementation | official-sdk |
| Documentation | https://www.npmjs.com/package/@microsoft/microsoft-graph-client |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, draft, send, read-provider-object, update-provider-object |
| Provider setup | required microsoft-graph-oauth-access-token; optional microsoft-graph-mailbox-user, microsoft-graph-webhook-client-state |
Coverage: Coverage includes SDK-backed Microsoft Graph Outlook mailbox support workflows: messages, mailFolders, attachments, sendMail, subscriptions, mailbox user readiness, and change notifications.
Boundary: Available operations depend on Microsoft Graph permissions, OAuth grant type, tenant admin consent, conditional access, mailbox licensing, Exchange Online policy, and delegated or application user selection.
Evidence: Microsoft Graph JavaScript client; Microsoft Graph create message; Microsoft Graph sendMail; Microsoft Graph message delta; plus 3 more.
Postmark¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-email-postmark |
| Manifest import | @cognidesk/integration-email-postmark/manifest |
| Runtime import | @cognidesk/integration-email-postmark/runtime |
| Workspace | integrations/email/postmark |
| Manifest ID | email.postmark |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://postmarkapp.com/developer |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, thread, attach, read-provider-object, search-provider-object, update-provider-object |
| Provider setup | required postmark-server-token, postmark-account-token; optional postmark-message-stream, postmark-webhook-auth |
Coverage: Coverage includes generated per-operation functions for every operation in Postmark's official server and account Swagger files.
Boundary: The SDK user chooses streams, sender signatures, templates, inbound domains, webhook protection, retention, redaction, and outbound approval policy.
Evidence: Postmark Server API Swagger; Postmark Account API Swagger; Postmark API Explorer; Postmark Email API; plus 5 more.
Forms¶
Cognidesk Forms¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-form-cognidesk |
| Manifest import | @cognidesk/integration-form-cognidesk/manifest |
| Runtime import | @cognidesk/integration-form-cognidesk/runtime |
| Workspace | integrations/form/cognidesk |
| Manifest ID | form.cognidesk |
| Scope | local-protocol |
| Adapter coverage | partial |
| Implementation | local-protocol |
| Documentation | website/guides/provider-integrations-catalog.md#form-cognidesk |
| Directions | receive-only, inbound-only |
| Capabilities | receive, read-provider-object, form.webhook-signature |
| Provider setup | required form-registry; optional form-webhook-secret |
Coverage: Coverage is limited to SDK-user-defined Cognidesk form definitions, structural submission validation, intake normalization, and Cognidesk HMAC webhook parsing.
Boundary: Field definitions, required fields, accepted options, intake routing, retention, and automation policy are owned by SDK user configuration.
Evidence: No provider evidence listed in the manifest.
Help Center¶
Cognidesk Help Center¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-help-center-cognidesk |
| Manifest import | @cognidesk/integration-help-center-cognidesk/manifest |
| Runtime import | @cognidesk/integration-help-center-cognidesk/runtime |
| Workspace | integrations/help-center/cognidesk |
| Manifest ID | helpcenter.cognidesk |
| Scope | local-protocol |
| Adapter coverage | partial |
| Implementation | local-protocol |
| Documentation | website/guides/provider-integrations-catalog.md#helpcenter-cognidesk |
| Directions | receive-only, inbound-only |
| Capabilities | read-provider-object, search-provider-object, receive, helpCenter.webhook-signature |
| Provider setup | required helpcenter-source; optional helpcenter-webhook-secret |
Coverage: Coverage is limited to Cognidesk local or generic HTTP help-center source search/fetch/readiness plus Cognidesk HMAC webhook normalization.
Boundary: Source selection, article visibility, indexing cadence, ranking, retention, locale fallback, and answer policy are owned by SDK user configuration.
Evidence: No provider evidence listed in the manifest.
Marketplace¶
Amazon Marketplace¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-marketplace-amazon |
| Manifest import | @cognidesk/integration-marketplace-amazon/manifest |
| Runtime import | @cognidesk/integration-marketplace-amazon/runtime |
| Workspace | integrations/marketplace/amazon |
| Manifest ID | marketplace.amazon |
| Scope | full-provider-api |
| Adapter coverage | full |
| Implementation | generated-full-provider-api |
| Documentation | https://developer-docs.amazon.com/sp-api |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, read-provider-object, search-provider-object, create-provider-object, send, marketplace.notification-signature, marketplace.sigv4 |
| Provider setup | required amazon-lwa-client, amazon-lwa-token, amazon-marketplace-id, amazon-notification-destination, amazon-notification-signature; optional amazon-aws-role-region |
Coverage: Coverage includes generated per-operation functions for every operation in Amazon's official Selling Partner API model repository.
Boundary: The SDK user chooses marketplaces, roles, restricted-data-token policy, notification topics, outbound solicitation rules, operator visibility, retention, consent, and redaction.
Evidence: Amazon official SP-API model repository; Amazon SP-API Orders v0 reference; Amazon SP-API Orders v2026-01-01 reference; Amazon SP-API Orders migration guide; plus 6 more.
eBay Marketplace¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-marketplace-ebay |
| Manifest import | @cognidesk/integration-marketplace-ebay/manifest |
| Runtime import | @cognidesk/integration-marketplace-ebay/runtime |
| Workspace | integrations/marketplace/ebay |
| Manifest ID | marketplace.ebay |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developer.ebay.com/api-docs |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, read-provider-object, search-provider-object, update-provider-object, create-provider-object, send, marketplace.notification-signature, marketplace.digital-signature, marketplace.notification-challenge |
| Provider setup | required ebay-oauth-access-token, ebay-application-access-token, ebay-client-id, ebay-client-secret, ebay-marketplace-id, ebay-notification-verification-token; optional ebay-digital-signature-key |
Coverage: Coverage is limited to selected eBay marketplace support primitives: Sell Fulfillment order, shipping fulfillment, refund, and payment-dispute operations; Sell Commerce Message conversations; Commerce Notification destination/subscription/config/public-key operations; notification challenges; and signed notification parsing.
Boundary: The SDK user chooses marketplaces, OAuth flows, scopes, notification topics, subscription filters, operator visibility, outbound messaging policy, refund/dispute rules, retention, consent, and redaction.
Evidence: eBay Sell Fulfillment API; eBay Digital Signatures for APIs; eBay Key Management API; eBay Commerce Notification API resources; plus 10 more.
Messaging¶
Discord Messaging Support¶
| Field | Value |
|---|---|
| Integration | Discord Integration |
| Package | @cognidesk/integration-messaging-discord |
| Manifest import | @cognidesk/integration-messaging-discord/manifest |
| Runtime import | @cognidesk/integration-messaging-discord/runtime |
| Workspace | integrations/messaging/discord |
| Manifest ID | messaging.discord |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://www.npmjs.com/package/discord.js |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, thread, read-provider-object, notify, discord.interaction-signature |
| Provider setup | required discord-bot-token, discord-application-id, discord-public-key; optional discord-guild-id, discord-channel-id, discord-webhook-url |
Coverage: Coverage is a Cognidesk support workflow adapter backed by discord.js, selected discord.js REST helpers, and an optional discord.js Gateway service for live support-thread handoff.
Boundary: Available Discord operations depend on the SDK user's Discord application, bot installation, OAuth scopes, role permissions, channel permissions, forum settings, and rate limits.
Evidence: discord.js package; Discord API reference; Discord message resource; Discord channel/thread endpoints; plus 6 more.
Google RCS for Business¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-messaging-rcs |
| Manifest import | @cognidesk/integration-messaging-rcs/manifest |
| Runtime import | @cognidesk/integration-messaging-rcs/runtime |
| Workspace | integrations/messaging/rcs |
| Manifest ID | messaging.rcs |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developers.google.com/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, media, read-provider-object, rcs.agent-events, rcs.webhook-signature |
| Provider setup | required rcs-agent, rcs-access-token, rcs-webhook-client-token |
Coverage: Coverage is typed for selected RCS for Business support workflows: agentMessages text/media/card sends, agent events, phone capability checks, agent readiness, file create/upload helpers, webhook challenge handling, and X-Goog-Signature validation.
Boundary: RCS for Business access, agent creation, brand verification, carrier launch, tester setup, webhook configuration, and production throughput require the SDK user's Google RBM partner or provider approval.
Evidence: RCS agentMessages create; RCS agentEvents create; RCS webhooks; RCS files create; plus 2 more.
WhatsApp Business Platform¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-messaging-whatsapp |
| Manifest import | @cognidesk/integration-messaging-whatsapp/manifest |
| Runtime import | @cognidesk/integration-messaging-whatsapp/runtime |
| Workspace | integrations/messaging/whatsapp |
| Manifest ID | messaging.whatsapp |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developers.facebook.com/documentation/business-messaging/whatsapp/get-started |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, media, attach, read-provider-object, update-provider-object, whatsapp.webhook-signature |
| Provider setup | required whatsapp-access-token, whatsapp-phone-number-id, whatsapp-app-secret; optional whatsapp-webhook-verify-token, whatsapp-waba-webhook-subscription |
Coverage: Coverage is typed for selected WhatsApp Business Platform support workflows: Cloud API message sends, template payload construction, media upload/get/download helpers, phone-number readiness, business profile get/update, webhook challenge handling, and X-Hub-Signature-256 validation.
Boundary: Available operations depend on the SDK user's Meta app, WhatsApp Business Account, phone number registration, WABA messages webhook subscription, access token scopes, business verification, templates, quality limits, and messaging windows.
Evidence: WhatsApp Cloud API get started; WhatsApp template fundamentals; WhatsApp media; WhatsApp business profiles; plus 3 more.
Reviews¶
App Store Reviews¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-review-appstore |
| Manifest import | @cognidesk/integration-review-appstore/manifest |
| Runtime import | @cognidesk/integration-review-appstore/runtime |
| Workspace | integrations/review/appstore |
| Manifest ID | review.appstore |
| Scope | full-provider-api |
| Adapter coverage | full |
| Implementation | generated-full-provider-api |
| Documentation | https://developer.apple.com/documentation/appstoreconnectapi/customer-reviews |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, draft, send, read-provider-object, search-provider-object, update-provider-object |
| Provider setup | required appstore-api-key, appstore-app-id; optional appstore-review-response-policy |
Coverage: Coverage includes generated per-operation functions for every operation in Apple's official App Store Connect OpenAPI specification.
Boundary: The SDK user decides review triage, sentiment classification, public-response approval, localization, escalation, and retention policy.
Evidence: App Store Connect OpenAPI specification; App Store Connect API overview; List customer reviews for an app; Customer review responses; plus 2 more.
Google Play Reviews¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-review-googleplay |
| Manifest import | @cognidesk/integration-review-googleplay/manifest |
| Runtime import | @cognidesk/integration-review-googleplay/runtime |
| Workspace | integrations/review/googleplay |
| Manifest ID | review.googleplay |
| Scope | full-provider-api |
| Adapter coverage | full |
| Implementation | generated-full-provider-api |
| Documentation | https://developers.google.com/android-publisher/api-ref/rest/v3/reviews |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | read-provider-object, search-provider-object, send, draft |
| Provider setup | required googleplay-access-token, googleplay-package-name; optional googleplay-service-account |
Coverage: Coverage includes generated per-method functions for every method in the official Google Play Android Publisher v3 Discovery document.
Boundary: The Google Play Reply to Reviews API exposes production app reviews with comments; rating-only feedback and non-production feedback are not exposed through this API.
Evidence: Google Play Android Publisher Discovery document; Google Play Android Publisher reviews resource; Google Play Reply to Reviews guide; Google service account OAuth 2.0 guide; plus 1 more.
SMS¶
Twilio Programmable Messaging¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-sms-twilio |
| Manifest import | @cognidesk/integration-sms-twilio/manifest |
| Runtime import | @cognidesk/integration-sms-twilio/runtime |
| Workspace | integrations/sms/twilio |
| Manifest ID | sms.twilio |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://www.twilio.com/docs/messaging/api |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, schedule, read-provider-object, search-provider-object, update-provider-object, twilio.webhook-signature |
| Provider setup | required twilio-account, twilio-sms-sender |
Coverage: Coverage includes generated per-operation functions for Twilio's official Messaging-domain OpenAPI surfaces: core Message/Media/Feedback/ShortCode resources, Messaging Services v1-v3, Conversations v1-v2, Content v1-v2, Verify v2-v3, and Studio v1-v2.
Boundary: Live SMS readiness depends on the SDK user's Twilio account, SMS-capable sender, Messaging Service configuration, phone-number capabilities, regions, carrier registration, webhooks, and account permissions.
Evidence: Twilio Messaging API overview; Twilio Message resource; Twilio Message Scheduling; Twilio Link Shortening; plus 2 more.
Social¶
Facebook Messenger¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-social-messenger |
| Manifest import | @cognidesk/integration-social-messenger/manifest |
| Runtime import | @cognidesk/integration-social-messenger/runtime |
| Workspace | integrations/social/messenger |
| Manifest ID | social.messenger |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developers.facebook.com/docs/messenger-platform |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, thread, read-provider-object, search-provider-object, media, social.webhook-signature |
| Provider setup | required messenger-page-access-token, messenger-page-id, messenger-app-secret; optional messenger-webhook-verify-token, messenger-page-webhook-subscription |
Coverage: Coverage is typed for selected Messenger Platform support workflows: Page messages send, text payloads, sender actions, attachment payload/upload helpers, conversation/message reads, Page readiness, webhook challenge handling, and X-Hub-Signature-256 validation.
Boundary: Available operations depend on the SDK user's Meta app mode, Page connection, permissions, Page access token, webhook subscriptions, and messaging window rules.
Evidence: Messenger webhooks; Page subscribed apps; Messenger Send API; Messenger sender actions; plus 2 more.
Instagram Direct Messages¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-social-instagram |
| Manifest import | @cognidesk/integration-social-instagram/manifest |
| Runtime import | @cognidesk/integration-social-instagram/runtime |
| Workspace | integrations/social/instagram |
| Manifest ID | social.instagram |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developers.facebook.com/documentation/business-messaging/instagram-messaging/features/send-message |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, draft, thread, read-provider-object, search-provider-object, social.webhook-signature |
| Provider setup | required instagram-page-access-token, instagram-page-id, instagram-business-account-id, instagram-app-secret, instagram-permissions; optional instagram-webhook-verify-token, instagram-page-webhook-subscription |
Coverage: Coverage is limited to Instagram Messaging send payloads, conversations/messages reads, account/page reads, webhook challenge handling, and X-Hub-Signature-256 validation for SDK-user-owned support messaging.
Boundary: Available operations depend on the SDK user's Meta app review, Page ownership, Instagram professional account link, granted permissions, webhook field subscriptions, messaging windows, HUMAN_AGENT review, rate limits, and regional policy.
Evidence: Instagram Messaging overview; Instagram Messaging send message; Instagram Messaging webhooks; Instagram Messaging app review.
TikTok Social¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-social-tiktok |
| Manifest import | @cognidesk/integration-social-tiktok/manifest |
| Runtime import | @cognidesk/integration-social-tiktok/runtime |
| Workspace | integrations/social/tiktok |
| Manifest ID | social.tiktok |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developers.tiktok.com/doc/tiktok-api-v2-get-user-info |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, draft, thread, read-provider-object, search-provider-object, social.comment-reply, social.webhook-signature |
| Provider setup | required tiktok-client-key, tiktok-client-secret, tiktok-access-token, tiktok-account-id, tiktok-webhook-signature, tiktok-webhook-callback, tiktok-scopes |
Coverage: Coverage is limited to selected TikTok Display API user/video reads, Research API comment reads, Business API comment operations, posting-status reads, and webhook signature parsing for SDK-user-owned support/review workflows.
Boundary: TikTok's public developer APIs do not expose a general customer-service direct-message inbox; this package intentionally does not provide a generic DM send/read client.
Evidence: TikTok Display API get started; TikTok user info API; TikTok video list API; TikTok Research video comments API; plus 3 more.
Ticketing¶
Freshdesk Ticketing¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-freshdesk |
| Manifest import | @cognidesk/integration-ticketing-freshdesk/manifest |
| Runtime import | @cognidesk/integration-ticketing-freshdesk/runtime |
| Workspace | integrations/ticketing/freshdesk |
| Manifest ID | ticketing.freshdesk |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://developers.freshdesk.com/api/ |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff, freshdesk.webhook-shared-secret |
| Provider setup | required freshdesk-domain, freshdesk-api-key; optional freshdesk-webhook-secret |
Coverage: Coverage is limited to Freshdesk v2 support primitives for tickets, contacts, ticket conversations, replies, notes, selected handoff updates, agent/group reads, current-agent readiness, and SDK-user shared-secret webhook validation.
Boundary: Ticket forms, required fields, statuses, priorities, products, groups, SLAs, automations, and agent permissions are owned by the SDK user's Freshdesk account.
Evidence: Freshdesk API v2 reference; Freshdesk v2 checked endpoint inventory.
Front¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-front |
| Manifest import | @cognidesk/integration-ticketing-front/manifest |
| Runtime import | @cognidesk/integration-ticketing-front/runtime |
| Workspace | integrations/ticketing/front |
| Manifest ID | ticketing.front |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://github.com/frontapp/front-api-specs |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required front-api-access |
Coverage: Coverage includes generated per-operation functions for every operation in Front's official Core and Channel API OpenAPI files.
Boundary: Inbox IDs, channel IDs, teammate assignment, tags, and message visibility are SDK-user configuration.
Evidence: Front official OpenAPI specs; Front Core API OpenAPI JSON; Front Channel API OpenAPI JSON; Front Create message; plus 9 more.
Gorgias¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-gorgias |
| Manifest import | @cognidesk/integration-ticketing-gorgias/manifest |
| Runtime import | @cognidesk/integration-ticketing-gorgias/runtime |
| Workspace | integrations/ticketing/gorgias |
| Manifest ID | ticketing.gorgias |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://developers.gorgias.com/llms.txt |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required gorgias-api-base, gorgias-api-access |
Coverage: Coverage includes generated per-operation functions for every operation found in Gorgias' official endpoint markdown pages with embedded OpenAPI blocks.
Boundary: Domain URL, ticket channels, message channels, macros, Shopify context, automations, and visibility are SDK-user configuration.
Evidence: Gorgias developer llms.txt; Gorgias Create ticket; Gorgias Retrieve ticket; Gorgias Update ticket; plus 5 more.
Help Scout¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-help-scout |
| Manifest import | @cognidesk/integration-ticketing-help-scout/manifest |
| Runtime import | @cognidesk/integration-ticketing-help-scout/runtime |
| Workspace | integrations/ticketing/help-scout |
| Manifest ID | ticketing.help-scout |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://developer.helpscout.com/llms.txt |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required help-scout-api-access |
Coverage: Coverage is limited to Help Scout conversation create/read/list, raw conversation JSONPatch update, thread list, reply/note thread creation, and mailbox-list readiness for Cognidesk support workflows.
Boundary: Mailbox IDs, thread types, assignment, workflow rules, and customer visibility are SDK-user configuration.
Evidence: Help Scout developer llms.txt; Help Scout OAuth authentication; Help Scout Create Conversation; Help Scout Get Conversation; plus 7 more.
HubSpot Service Hub¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-hubspot |
| Manifest import | @cognidesk/integration-ticketing-hubspot/manifest |
| Runtime import | @cognidesk/integration-ticketing-hubspot/runtime |
| Workspace | integrations/ticketing/hubspot |
| Manifest ID | ticketing.hubspot |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://api.hubapi.com/public/api/spec/v1/specs |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff, hubspot.request-signature-v3 |
| Provider setup | required hubspot-private-app-token, hubspot-portal; optional hubspot-app, hubspot-webhook-secret |
Coverage: Coverage includes generated per-operation functions for every selected current API entry in HubSpot's official public spec index.
Boundary: Ticket pipelines, pipeline stages, priorities, owners, custom properties, association labels, webhook subscriptions, private app scopes, and Service Hub entitlements are owned by the SDK user's HubSpot portal.
Evidence: HubSpot public OpenAPI spec index; HubSpot CRM Tickets API guide; HubSpot CRM Notes API guide; HubSpot CRM search guide; plus 5 more.
Intercom¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-intercom |
| Manifest import | @cognidesk/integration-ticketing-intercom/manifest |
| Runtime import | @cognidesk/integration-ticketing-intercom/runtime |
| Workspace | integrations/ticketing/intercom |
| Manifest ID | ticketing.intercom |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://github.com/intercom/Intercom-OpenAPI |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff, intercom.request-signature |
| Provider setup | required intercom-access-token; optional intercom-webhook-secret |
Coverage: Coverage includes generated per-operation functions for every operation in Intercom's official stable REST API 2.15 OpenAPI file.
Boundary: Ticket types, ticket attributes, ticket states, conversation search fields, Inbox assignment targets, teammate availability, and API scopes are owned by the SDK user's Intercom workspace.
Evidence: Intercom official OpenAPI specs; Intercom REST API 2.15 OpenAPI YAML; Intercom REST API reference; Intercom Conversations API; plus 3 more.
Kustomer¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-kustomer |
| Manifest import | @cognidesk/integration-ticketing-kustomer/manifest |
| Runtime import | @cognidesk/integration-ticketing-kustomer/runtime |
| Workspace | integrations/ticketing/kustomer |
| Manifest ID | ticketing.kustomer |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://developer.kustomer.com/kustomer-api-docs/reference |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required kustomer-api-access |
Coverage: Coverage includes generated per-operation functions for every operation found in Kustomer's official ReadMe API registry OpenAPI documents.
Boundary: Conversation model, queues, teams, custom objects, and message visibility are SDK-user configuration.
Evidence: Kustomer REST APIs portal; Kustomer ReadMe API registry - Core Resources; Kustomer API introduction; Kustomer API keys; plus 6 more.
Microsoft Dynamics 365 Customer Service¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-dynamics365 |
| Manifest import | @cognidesk/integration-ticketing-dynamics365/manifest |
| Runtime import | @cognidesk/integration-ticketing-dynamics365/runtime |
| Workspace | integrations/ticketing/dynamics365 |
| Manifest ID | ticketing.dynamics365 |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/overview |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required dynamics365-instance, dynamics365-api-access |
Coverage: Coverage is limited to Dataverse incident CRUD/search, selected metadata/readiness helpers, incident notes via annotations, queue AddToQueue, and queue/activity reads used by Cognidesk support workflows.
Boundary: Dataverse table customizations, required fields, queues, owners, security roles, and routing rules are SDK-user configuration.
Evidence: Microsoft Dataverse Web API overview; Dynamics 365 Customer Service incident table reference; Dataverse EntityDefinitions metadata queries; Dataverse WhoAmI Function; plus 7 more.
Oracle Service¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-oracle-service |
| Manifest import | @cognidesk/integration-ticketing-oracle-service/manifest |
| Runtime import | @cognidesk/integration-ticketing-oracle-service/runtime |
| Workspace | integrations/ticketing/oracle-service |
| Manifest ID | ticketing.oracle-service |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://docs.oracle.com/en/cloud/saas/sales/faaps/api-internal-service-requests.html |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required oracle-service-instance, oracle-service-api-access |
Coverage: Coverage is typed for Oracle Fusion Service serviceRequests create, read by SrNumber, patch, collection search, child message creation, and readiness checks used by Cognidesk support workflows.
Boundary: Oracle Service categories, required fields, queues, assignment rules, milestones, extensions, and privileges are owned by the SDK user's Fusion Service environment.
Evidence: Oracle Fusion Service serviceRequests overview; Oracle Fusion Service create service request; Oracle Fusion Service get all service requests; Oracle Fusion Service get service request; plus 2 more.
Pega Customer Service¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-pega-customer-service |
| Manifest import | @cognidesk/integration-ticketing-pega-customer-service/manifest |
| Runtime import | @cognidesk/integration-ticketing-pega-customer-service/runtime |
| Workspace | integrations/ticketing/pega-customer-service |
| Manifest ID | ticketing.pega-customer-service |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://docs.pega.com/bundle/dx-api/page/platform/dx-api/dx-api-overview.html |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required pega-customer-service-instance, pega-customer-service-api-access |
Coverage: Coverage is typed for Pega DX API case creation, case read/update, case search/listing, case-type listing, assignment action submission, and readiness checks used by Cognidesk support workflows.
Boundary: Case types, starting processes, field requirements, assignment routing, security rules, data pages, and stage transitions are owned by the SDK user's Pega application.
Evidence: Pega DX API overview; Pega DX API cases endpoints; Pega DX API POST /cases; Pega DX API GET /cases; plus 4 more.
Salesforce Service Cloud¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-salesforce |
| Manifest import | @cognidesk/integration-ticketing-salesforce/manifest |
| Runtime import | @cognidesk/integration-ticketing-salesforce/runtime |
| Workspace | integrations/ticketing/salesforce |
| Manifest ID | ticketing.salesforce |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/resources_list.htm |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff, salesforce.webhook-verifier |
| Provider setup | required salesforce-instance, salesforce-oauth-access; optional salesforce-webhook-secret |
Coverage: Coverage is limited to selected Salesforce REST API and Service Cloud support primitives: Case create/read/update/search, sObject describe, assignment-rule header opt-in, CaseComment, FeedItem, Contact/Account SOQL search, user/org readiness, and SDK-user inbound event relay parsing.
Boundary: Salesforce Case record types, required fields, queues, owners, entitlements, assignment rules, triggers, Flow automation, field-level security, and Service Cloud licenses are owned by the SDK user's org.
Evidence: Salesforce REST API resources; Salesforce sObject Describe; Salesforce Assignment Rule header; Salesforce Case object reference; plus 9 more.
SAP Service Cloud¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-sap-service-cloud |
| Manifest import | @cognidesk/integration-ticketing-sap-service-cloud/manifest |
| Runtime import | @cognidesk/integration-ticketing-sap-service-cloud/runtime |
| Workspace | integrations/ticketing/sap-service-cloud |
| Manifest ID | ticketing.sap-service-cloud |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://help.sap.com/docs/sap-cloud-for-customer/odata-services/sap-cloud-for-customer-odata-api |
| Directions | bidirectional |
| Capabilities | handoff, create-provider-object, read-provider-object, update-provider-object, search-provider-object |
| Provider setup | required sap-service-cloud-tenant, sap-service-cloud-api-access |
Coverage: Coverage is typed for SAP Cloud for Customer OData ServiceRequestCollection create, read by ObjectID, patch, collection query, CSRF token preflight, and readiness checks used by Cognidesk support workflows.
Boundary: SAP tenant OData exposure, communication arrangements, required fields, statuses, code lists, workflow rules, and extensions are SDK-user configuration.
Evidence: SAP Cloud for Customer OData API; SAP Cloud for Customer OData API overview; SAP Cloud for Customer OData API v2 Reference; SAP Cloud for Customer OData Services PDF.
ServiceNow Ticketing¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-servicenow |
| Manifest import | @cognidesk/integration-ticketing-servicenow/manifest |
| Runtime import | @cognidesk/integration-ticketing-servicenow/runtime |
| Workspace | integrations/ticketing/servicenow |
| Manifest ID | ticketing.servicenow |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://www.servicenow.com/docs/r/washingtondc/api-reference/rest-apis/c_TableAPI.html |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required servicenow-instance, servicenow-api-access |
Coverage: Coverage is limited to ServiceNow Table API record create/read/update/search, incident creation, Attachment API upload/list, Import Set insert/read, and readiness checks used by Cognidesk support workflows.
Boundary: Available tables, fields, ACLs, business rules, and mandatory fields are owned by the SDK user's ServiceNow instance.
Evidence: ServiceNow Table API; ServiceNow Attachment API; ServiceNow Import Set API; ServiceNow Virtual Agent API; plus 2 more.
Zendesk Support¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-zendesk |
| Manifest import | @cognidesk/integration-ticketing-zendesk/manifest |
| Runtime import | @cognidesk/integration-ticketing-zendesk/runtime |
| Workspace | integrations/ticketing/zendesk |
| Manifest ID | ticketing.zendesk |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://developer.zendesk.com/zendesk/oas.yaml |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required zendesk-instance, zendesk-api-access |
Coverage: Coverage includes generated per-operation functions for every operation in Zendesk's official Support API OpenAPI file.
Boundary: Available fields, brands, forms, triggers, automations, macros, and permissions are owned by the SDK user's Zendesk account.
Evidence: Zendesk Support API OpenAPI; Zendesk Support Tickets API; Zendesk Ticket Comments API; Zendesk Ticket Attachments API; plus 3 more.
Zoho Desk¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-ticketing-zoho-desk |
| Manifest import | @cognidesk/integration-ticketing-zoho-desk/manifest |
| Runtime import | @cognidesk/integration-ticketing-zoho-desk/runtime |
| Workspace | integrations/ticketing/zoho-desk |
| Manifest ID | ticketing.zoho-desk |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://desk.zoho.com/DeskAPIDocument |
| Directions | bidirectional |
| Capabilities | create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff |
| Provider setup | required zoho-desk-org, zoho-desk-api-access |
Coverage: Coverage is typed for Zoho Desk ticket create, read, patch, ticket listing/search query passthrough, ticket comments, ticket threads, send-reply, organization readiness, and credential status used by Cognidesk support workflows.
Boundary: Departments, layouts, mandatory fields, assignment rules, blueprints, and visibility are SDK-user configuration.
Evidence: Zoho Desk API documentation; Zoho Desk create ticket; Zoho Desk list all tickets; Zoho Desk update ticket; plus 5 more.
Video¶
Whereby Embedded¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-video-whereby |
| Manifest import | @cognidesk/integration-video-whereby/manifest |
| Runtime import | @cognidesk/integration-video-whereby/runtime |
| Workspace | integrations/video/whereby |
| Manifest ID | video.whereby |
| Scope | full-provider-api |
| Adapter coverage | full |
| Implementation | generated-full-provider-api |
| Documentation | https://docs.whereby.com/reference/whereby-rest-api-reference/meetings |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | schedule, create-provider-object, read-provider-object, delete-provider-object, update-provider-object, receive, whereby.request-signature |
| Provider setup | required whereby-api-key; optional whereby-organization, whereby-room-template, whereby-webhook-signing-secret |
Coverage: Coverage includes generated per-operation functions for every operation in Whereby's official public REST OpenAPI spec.
Boundary: Whereby meetings are transient rooms controlled by the SDK user's Embedded account, API key, plan, dashboard configuration, and current Whereby feature availability.
Evidence: Whereby REST OpenAPI spec; Whereby REST meetings API; Whereby REST recordings API; Whereby REST transcriptions API; plus 2 more.
Zoom Meetings¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-video-zoom |
| Manifest import | @cognidesk/integration-video-zoom/manifest |
| Runtime import | @cognidesk/integration-video-zoom/runtime |
| Workspace | integrations/video/zoom |
| Manifest ID | video.zoom |
| Scope | provider-api-subset |
| Adapter coverage | standard |
| Implementation | provider-api-subset |
| Documentation | https://developers.zoom.us/api-hub/meetings/methods/endpoints.json |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | schedule, create-provider-object, read-provider-object, delete-provider-object, update-provider-object, receive, zoom.request-signature |
| Provider setup | required zoom-oauth-access-token; optional zoom-webhook-secret-token |
Coverage: Coverage includes generated per-operation functions for every operation in Zoom's official Meetings API Hub OpenAPI spec.
Boundary: Available meeting operations depend on the SDK user's Zoom OAuth scopes, account plan, account-level settings, admin policy, and delegated host permissions.
Evidence: Zoom Meetings API Hub OpenAPI; Zoom Meetings API reference; Zoom webhooks reference; Zoom webhook validation.
Voice Provider APIs¶
AWS Speech¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-aws-speech |
| Manifest import | @cognidesk/integration-voice-aws-speech/manifest |
| Runtime import | @cognidesk/integration-voice-aws-speech/runtime |
| Workspace | integrations/voice/aws-speech |
| Manifest ID | voice.aws-speech |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://docs.aws.amazon.com/transcribe/latest/APIReference/API_streaming_StartStreamTranscription.html |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, media |
| Provider setup | required aws-access-key-id, aws-secret-access-key, aws-region; optional aws-session-token |
Coverage: Implements Amazon Transcribe Streaming speech-to-text and Amazon Polly SynthesizeSpeech text-to-speech for Cognidesk STT/TTS voice pipelines.
Boundary: This package implements AWS STT/TTS for Cognidesk speech pipelines through injected AWS SDK clients; it does not own AWS credential resolution, IAM roles, VPC endpoints, or account policy.
Evidence: Amazon Transcribe StartStreamTranscription API; Amazon Transcribe streaming setup; AWS SDK for JavaScript Transcribe Streaming client; Amazon Polly SynthesizeSpeech API; plus 2 more.
Azure AI Speech¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-azure-speech |
| Manifest import | @cognidesk/integration-voice-azure-speech/manifest |
| Runtime import | @cognidesk/integration-voice-azure-speech/runtime |
| Workspace | integrations/voice/azure-speech |
| Manifest ID | voice.azure-speech |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://learn.microsoft.com/azure/ai-services/speech-service/rest-speech-to-text-short |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, media |
| Provider setup | required azure-speech-key, azure-speech-region |
Coverage: Implements Azure AI Speech speech-to-text and text-to-speech for Cognidesk STT/TTS voice pipelines.
Boundary: This package implements short-audio REST STT and REST TTS for Cognidesk speech pipelines, not full streaming Azure Speech SDK sessions.
Evidence: Azure AI Speech to text REST API; Azure AI Text to speech REST API; Azure Speech audio output formats.
Deepgram Speech¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-deepgram |
| Manifest import | @cognidesk/integration-voice-deepgram/manifest |
| Runtime import | @cognidesk/integration-voice-deepgram/runtime |
| Workspace | integrations/voice/deepgram |
| Manifest ID | voice.deepgram |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://developers.deepgram.com/docs/pre-recorded-audio |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, media |
| Provider setup | required deepgram-api-key |
Coverage: Implements Deepgram prerecorded speech-to-text and Aura text-to-speech REST requests for Cognidesk STT/TTS voice pipelines.
Boundary: This package implements REST STT/TTS for Cognidesk speech pipelines, not Deepgram Voice Agent or full streaming websocket sessions.
Evidence: Deepgram prerecorded audio STT; Deepgram Text-to-Speech REST; Deepgram TTS media output settings.
ElevenLabs Voice¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-elevenlabs |
| Manifest import | @cognidesk/integration-voice-elevenlabs/manifest |
| Runtime import | @cognidesk/integration-voice-elevenlabs/runtime |
| Workspace | integrations/voice/elevenlabs |
| Manifest ID | voice.elevenlabs |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://api.elevenlabs.io/openapi.json |
| Directions | send-only, receive-only, bidirectional |
| Capabilities | send, receive, media, elevenlabs.conversation-signed-url, elevenlabs.speech-to-text |
| Provider setup | required elevenlabs-api-key |
Coverage: Coverage includes generated per-operation functions for every operation in ElevenLabs' official public REST OpenAPI 3.1 specification.
Boundary: The generated full-provider claim is limited to ElevenLabs REST OpenAPI operations verified on 2026-06-18; realtime WebSocket transport behavior remains a separate protocol surface.
Evidence: ElevenLabs REST OpenAPI specification; ElevenLabs API reference; ElevenLabs API authentication; ElevenLabs Text to Speech create speech; plus 14 more.
Generic SIP Voice Connection¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-sip |
| Manifest import | @cognidesk/integration-voice-sip/manifest |
| Runtime import | @cognidesk/integration-voice-sip/runtime |
| Workspace | integrations/voice/sip |
| Manifest ID | voice.sip |
| Scope | local-protocol |
| Adapter coverage | partial |
| Implementation | local-protocol |
| Documentation | website/guides/provider-integrations-catalog.md#voice-sip |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | receive, send, media, transfer, recording, transcription, sip.webhook-signature |
| Provider setup | required sip-registrar, sip-domain, sip-auth, sip-tls, sip-srtp, sip-webhook-callback; optional sip-proxy |
Coverage: Defines a Cognidesk SIP stack gateway contract and callback normalizer for SDK-user-owned SIP/SBC/BYOC infrastructure.
Boundary: A full SIP transaction/dialog stack is intentionally out of scope for this package.
Evidence: No provider evidence listed in the manifest.
Google Cloud Speech¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-google-speech |
| Manifest import | @cognidesk/integration-voice-google-speech/manifest |
| Runtime import | @cognidesk/integration-voice-google-speech/runtime |
| Workspace | integrations/voice/google-speech |
| Manifest ID | voice.google-speech |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://docs.cloud.google.com/speech-to-text/docs/reference/rest/v1/speech/recognize |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, media |
| Provider setup | required google-cloud-access-token |
Coverage: Implements Google Cloud Speech-to-Text synchronous recognize and Cloud Text-to-Speech synchronous synthesize for Cognidesk STT/TTS voice pipelines.
Boundary: This package implements synchronous REST STT and REST TTS for Cognidesk speech pipelines, not full streaming Google Cloud Speech SDK sessions.
Evidence: Google Cloud Speech-to-Text speech.recognize REST API; Google Cloud Speech-to-Text RecognitionConfig; Google Cloud Text-to-Speech text.synthesize REST API; Google Cloud Text-to-Speech audio encodings; plus 1 more.
OpenAI Realtime Voice¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-openai |
| Manifest import | @cognidesk/integration-voice-openai/manifest |
| Runtime import | @cognidesk/integration-voice-openai/runtime |
| Workspace | integrations/voice/openai |
| Manifest ID | voice.openai |
| Scope | provider-api-subset |
| Adapter coverage | partial |
| Implementation | provider-api-subset |
| Documentation | https://developers.openai.com/api/docs/guides/realtime |
| Directions | bidirectional |
| Capabilities | receive, send, media, handoff |
| Provider setup | required openai-api-key |
Coverage: Implements a server-side OpenAI Realtime voice adapter for Cognidesk browser voice sessions, including session updates, audio events, speech responses, and function-tool outputs.
Boundary: This package currently supports only gpt-realtime-2.
Evidence: OpenAI Realtime and audio guide; OpenAI Realtime conversations guide; OpenAI Realtime client events reference; OpenAI realtime models prompting guide.
Twilio Programmable Voice¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-twilio |
| Manifest import | @cognidesk/integration-voice-twilio/manifest |
| Runtime import | @cognidesk/integration-voice-twilio/runtime |
| Workspace | integrations/voice/twilio |
| Manifest ID | voice.twilio |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://www.twilio.com/docs/voice/api |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | receive, send, media, transfer, twilio.webhook-signature |
| Provider setup | required twilio-account, twilio-rest-api-credentials; optional twilio-webhook-auth-token, twilio-voice-number |
Coverage: Coverage includes generated per-operation functions for Twilio's official Voice-domain OpenAPI surfaces: core Voice call/conference/queue/recording/transcription/stream/SIP resources, Voice v1/v3, Trunking v1, and Insights v1-v3.
Boundary: Live call readiness depends on the SDK user's Twilio account, voice-capable numbers, regions, webhooks, and account permissions.
Evidence: Twilio Programmable Voice API overview; Twilio Call resource; Twilio Stream TwiML; Twilio request signature validation; plus 3 more.
Vonage Voice API¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-voice-vonage |
| Manifest import | @cognidesk/integration-voice-vonage/manifest |
| Runtime import | @cognidesk/integration-voice-vonage/runtime |
| Workspace | integrations/voice/vonage |
| Manifest ID | voice.vonage |
| Scope | full-provider-api |
| Adapter coverage | partial |
| Implementation | generated-full-provider-api |
| Documentation | https://developer.vonage.com/en/voice/voice-api |
| Directions | inbound-only, outbound-only, bidirectional |
| Capabilities | receive, send, media, transfer, voice.webhook-signature |
| Provider setup | required vonage-application, vonage-voice-application-webhooks; optional vonage-api-key-secret, vonage-voice-number, vonage-webhook-signature-secret, vonage-fallback-answer-url, vonage-signed-callbacks |
Coverage: Coverage includes generated per-operation functions for every operation in the official Vonage Voice v1, Voice v2, Application v2, Conversation v1, and Numbers OpenAPI specs used by this voice package.
Boundary: The SDK user configures application answer/event/fallback webhooks, signed callbacks, phone numbers, regions, recording consent, outbound eligibility, and handoff policy.
Evidence: Vonage Voice API v1 OpenAPI; Vonage Voice API v2 OpenAPI; Vonage Application API v2 OpenAPI; Vonage Conversation API v1 OpenAPI; plus 11 more.
Workplace¶
Microsoft Teams¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-workplace-teams |
| Manifest import | @cognidesk/integration-workplace-teams/manifest |
| Runtime import | @cognidesk/integration-workplace-teams/runtime |
| Workspace | integrations/workplace/teams |
| Manifest ID | workplace.teams |
| Scope | provider-api-subset |
| Adapter coverage | standard |
| Implementation | official-sdk |
| Documentation | https://www.npmjs.com/package/@microsoft/microsoft-graph-client |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, notify, thread, read-provider-object, create-provider-object, update-provider-object |
| Provider setup | required microsoft-graph-oauth-access-token, microsoft-graph-tenant, microsoft-graph-app-registration; optional microsoft-graph-change-notification-client-state |
Coverage: Coverage includes SDK-backed Microsoft Graph Teams support workflows: channel and chat messages, channel replies, message updates, subscriptions, current-user readiness, and change notifications.
Boundary: Available operations depend on the SDK user's Microsoft Entra tenant, Teams licensing, Graph OAuth scopes, delegated versus application permission mode, resource-specific consent, tenant/admin consent, channel membership, and Teams policy.
Evidence: Microsoft Graph JavaScript client; Microsoft Graph send channel message; Microsoft Graph send chat message; Microsoft Graph send channel reply; plus 6 more.
Slack¶
| Field | Value |
|---|---|
| Package | @cognidesk/integration-workplace-slack |
| Manifest import | @cognidesk/integration-workplace-slack/manifest |
| Runtime import | @cognidesk/integration-workplace-slack/runtime |
| Workspace | integrations/workplace/slack |
| Manifest ID | workplace.slack |
| Scope | support-workflow-subset |
| Adapter coverage | partial |
| Implementation | support-workflow-adapter |
| Documentation | https://www.npmjs.com/package/@slack/web-api |
| Directions | receive-only, send-only, bidirectional |
| Capabilities | receive, send, notify, thread, media, read-provider-object, update-provider-object, slack.request-signature |
| Provider setup | required slack-bot-token, slack-signing-secret |
Coverage: Coverage is a Cognidesk support workflow adapter backed by Slack's official @slack/web-api package.
Boundary: Available Slack operations depend on the SDK user's app scopes, workspace policy, channel membership, Enterprise Grid policy, and user targets for ephemeral messages.
Evidence: Slack Web API package; Slack Web API methods; Slack chat.postMessage; Slack chat.update; plus 6 more.