Skip to content

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
Email 7 @cognidesk/integration-email-ses
@cognidesk/integration-email-gmail
@cognidesk/integration-email-imap
@cognidesk/integration-email-mailgun
@cognidesk/integration-email-outlook
@cognidesk/integration-email-postmark
@cognidesk/integration-email-smtp
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/integrations/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 provider-rest-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 a built-in Discourse-compatible REST adapter for forum topic/post/search/current-user workflows, optional provider client overrides, 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 contact-center.8x8
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://raw.githubusercontent.com/8x8Cloud/public-developer-docs/master/docs_oas/actions-events/contact_center_call_api.json
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, send, update-provider-object
Provider setup required 8x8-contact-center-api-base, 8x8-contact-center-api-access; optional 8x8-contact-center-routing

Coverage: No suitable official server-side JavaScript Contact Center SDK was verified.

Boundary: The official @8x8/pui-partner-comm package is a partner iframe communication SDK, not a backend Contact Center API client.

Evidence: 8x8 Contact Center Call API OpenAPI; 8x8 Contact Center Agent Status OpenAPI; 8x8 Partner SDK.

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 contact-center.aircall
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://developer.aircall.io/api-references/
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff
Provider setup required aircall-api-access; optional aircall-api-base, aircall-routing

Coverage: aircall-everywhere is a maintained Workspace iframe SDK, not a server-side Public API client.

Boundary: Runtime calls use Aircall Public API REST for documented call transfer and ping endpoints, with AircallRawClient available as the host-client override.

Evidence: Aircall API References; Aircall Everywhere SDK; aircall-everywhere npm package.

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 contact-center.amazon-connect
Scope support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/aws/aws-sdk-js-v3
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, send, transfer, read-provider-object
Provider setup required amazon-connect-instance, amazon-connect-api-access

Coverage: Runtime uses AWS SDK v3 clients for normalized Amazon Connect support workflows.

Boundary: Contact flows, queue/quick-connect routing, outbound consent, IAM policy, participant token custody, and WebSocket subscription behavior remain application/AWS configuration.

Evidence: AWS SDK for JavaScript v3; Amazon Connect API Reference; Amazon Connect Participant Service.

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 contact-center.five9
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-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: No suitable official backend JavaScript/TypeScript SDK was verified.

Boundary: Runtime calls use a built-in REST adapter only when baseUrl/API credentials and host-configured operation paths are supplied, with Five9ProviderClient available as a typed host-client override.

Evidence: Five9 Contact Center APIs and SDKs; Five9 CRM SDK JSDoc; npm five9 package.

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 contact-center.genesys-cloud
Scope support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/MyPureCloud/platform-client-sdk-javascript
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, contact-center.open-messaging-ingress, schedule, read-provider-object
Provider setup required genesys-cloud-region, genesys-cloud-api-access; optional genesys-cloud-open-messaging, genesys-cloud-routing

Coverage: Runtime uses the official purecloud-platform-client-v2 SDK for normalized Genesys Cloud support workflows.

Boundary: Genesys regions, OAuth permissions, Architect flows, queues, callbacks, digital integrations, and outbound policy remain SDK-user configuration.

Evidence: Genesys Cloud JavaScript SDK; Genesys Cloud Developer Center; Genesys Cloud Open Messaging.

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 contact-center.genesys-engage
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://docs.genesys.com/Documentation/GMS/latest/API/CallbackServicesAPI
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, schedule, send, read-provider-object
Provider setup required genesys-engage-gms-base-url; optional genesys-engage-auth, genesys-engage-routing

Coverage: Runtime callback scheduling uses the official PureEngage engagement-client-js generated SDK through CallbacksApi.bookCallbackExternal.

Boundary: No matching maintained backend/runtime SDK was verified for GMS Chat API v2, so chat operations use the reviewed REST adapter.

Evidence: Genesys GMS Callback Services API; Genesys GMS Chat API v2; PureEngage engagement-client-js; Genesys Cloud Platform SDK for JavaScript; plus 1 more.

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 contact-center.genesys-pureconnect
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://help.genesys.com/developer/cic/docs/icws/webhelp/icws/connection/index.htm
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, create-provider-object, read-provider-object
Provider setup required genesys-pureconnect-icws-base-url; optional genesys-pureconnect-session, genesys-pureconnect-routing

Coverage: No maintained Genesys PureConnect ICWS npm runtime SDK was verified.

Boundary: Official PureConnect ICWS SDK documentation describes a REST API and API documentation rather than a maintained npm runtime client.

Evidence: PureConnect ICWS connection; PureConnect ICWS interactions; PureConnect ICWS SDK; NPM ICWS candidate machinepack-ic.

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 contact-center.nextiva
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://www.nextiva.com/resources/learn/rest-apis
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, read-provider-object
Provider setup required nextiva-contact-center-api-base, nextiva-contact-center-api-access; optional nextiva-contact-center-routing

Coverage: No suitable public server-side Nextiva JavaScript SDK was verified for this provider runtime.

Boundary: Runtime calls use a strict typed REST adapter when baseUrl/API credentials are supplied, with NextivaProviderClient available as a host-client override.

Evidence: Nextiva Contact Center REST APIs; Nextiva WorkItem Service; Nextiva Frontend SDKs; Nextiva SDK Installation; 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 contact-center.nice-cxone
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://developer.niceincontact.com/API
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, schedule, send, update-provider-object, read-provider-object
Provider setup required nice-cxone-api-base, nice-cxone-api-access; optional nice-cxone-routing

Coverage: Maintained NICE @nice-devone SDK packages exist, but the closest ACD runtime package is UNLICENSED and documented for CXone Agent/app-bundler use.

Boundary: Runtime calls use a fail-closed built-in REST adapter when baseUrl/API credentials are supplied, with NiceCxoneProviderClient available as a typed host override.

Evidence: NICE CXone REST APIs; NICE CXone ACD SDK package; NICE CXone Agent SDK repository.

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 contact-center.ringcentral
Scope support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/ringcentral/ringcentral-js
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, read-provider-object
Provider setup required ringcentral-api-base, ringcentral-api-access; optional ringcentral-ringcx-routing

Coverage: Runtime uses @ringcentral/sdk for authentication and SDK.platform()-dispatched contact-center operations.

Boundary: RingCX API product, regional endpoint, queue/campaign IDs, and outbound eligibility are SDK-user configuration.

Evidence: RingCentral JavaScript SDK; RingCX Voice APIs; RingCX Digital APIs.

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 contact-center.talkdesk
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://api-docs.talkdeskapp.com/public-api
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, schedule, create-provider-object
Provider setup required talkdesk-api-root, talkdesk-api-access; optional talkdesk-routing

Coverage: No suitable official npm REST SDK was verified.

Boundary: Runtime calls use a built-in REST adapter when baseUrl/API credentials are supplied, with TalkdeskProviderClient available as an override.

Evidence: Talkdesk public OpenAPI bundle; Talkdesk Callback API.

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 contact-center.zoom
Scope support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://developers.zoom.us/api-hub/contact-center/methods/endpoints.json
Directions inbound-only, outbound-only, bidirectional
Capabilities handoff, send, read-provider-object
Provider setup required zoom-contact-center-api-base, zoom-contact-center-api-access; optional zoom-contact-center-routing

Coverage: No maintained official server-side JavaScript SDK was verified for Zoom Contact Center management APIs.

Boundary: @zoom/appssdk is an embedded Zoom Apps SDK, @zoom/rtms is media-streaming, and the Contact Center SDK is a browser/client integration surface.

Evidence: Zoom Contact Center REST OpenAPI; Zoom Contact Center Webhooks OpenAPI; Zoom Contact Center SDK for web; Zoom Apps SDK; 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 official-sdk
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: Coverage is limited to selected Shopify Admin GraphQL support operations backed by the official Shopify Admin API client.

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 API client; Shopify webhook HMAC validation.

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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
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-connect-mode

Coverage: Coverage is limited to Cognidesk-normalized Stripe commerce support operations backed by the official Stripe SDK.

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 Node SDK; Stripe webhook signature verification.

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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/aws/aws-sdk-js-v3/tree/main/clients/client-sesv2
Directions receive-only, send-only, bidirectional
Capabilities receive, send, read-provider-object, update-provider-object
Provider setup required aws-credentials, aws-region; optional ses-sns-verification

Coverage: Coverage is the Cognidesk normalized support-email adapter surface backed by AWS SDK v3 SES clients.

Boundary: SES is not a mailbox product and does not expose mailbox-style message history.

Evidence: AWS SDK for JavaScript v3 SESv2 client; AWS SDK for JavaScript v3 SES classic client; Amazon SES API v2; Amazon SES event publishing; plus 1 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 local-protocol
Adapter coverage partial
Implementation local-protocol
Documentation https://datatracker.ietf.org/doc/html/rfc9051
Directions inbound-only
Capabilities read-provider-object, search-provider-object
Provider setup required imap-server, imap-mailbox-credentials

Coverage: Coverage is a focused Cognidesk IMAP protocol adapter backed by ImapFlow.

Boundary: This package does not implement full mailbox synchronization, storage, retention, MIME parsing policy, attachment handling policy, deletion policy, or outbound SMTP.

Evidence: RFC 9051 IMAP4rev2; ImapFlow.

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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/mailgun/mailgun.js
Directions receive-only, send-only, bidirectional
Capabilities receive, send, read-provider-object, search-provider-object
Provider setup required mailgun-api-key, mailgun-domain; optional mailgun-webhook-signing-key

Coverage: Coverage is the Cognidesk normalized support-email adapter surface backed by the official Mailgun SDK.

Boundary: The SDK user owns domain selection, route policy, retention, redaction, replay-cache storage, outbound approval, and rate limiting.

Evidence: mailgun.js package; Mailgun Messages API; Mailgun Events API; Mailgun Webhooks.

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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/ActiveCampaign/postmark.js
Directions receive-only, send-only, bidirectional
Capabilities receive, send, read-provider-object, update-provider-object
Provider setup required postmark-server-token; optional postmark-account-token

Coverage: Coverage is the Cognidesk normalized support-email adapter surface backed by the official Postmark Node client.

Boundary: The SDK user owns message stream selection, webhook auth policy, retention, redaction, outbound approval, and rate limiting.

Evidence: Postmark Node.js library; Postmark Email API; Postmark Messages API; Postmark inbound webhooks.

SMTP Email

Field Value
Package @cognidesk/integration-email-smtp
Manifest import @cognidesk/integration-email-smtp/manifest
Runtime import @cognidesk/integration-email-smtp/runtime
Workspace integrations/email/smtp
Manifest ID email.smtp
Scope local-protocol
Adapter coverage partial
Implementation local-protocol
Documentation https://datatracker.ietf.org/doc/html/rfc5321
Directions send-only
Capabilities send, read-provider-object
Provider setup required smtp-server, smtp-account-credentials; optional smtp-sender-address

Coverage: Coverage is a focused Cognidesk SMTP outbound adapter backed by Nodemailer.

Boundary: SMTP is outbound-only; mailbox synchronization, inbound parsing, reply polling, retention, and deletion are intentionally outside this package.

Evidence: RFC 5321 SMTP; Nodemailer.

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#cognidesk-forms
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 help-center.cognidesk
Scope local-protocol
Adapter coverage partial
Implementation local-protocol
Documentation website/guides/provider-integrations-catalog.md#cognidesk-help-center
Directions receive-only, inbound-only
Capabilities read-provider-object, search-provider-object, receive, help-center.webhook-signature
Provider setup required help-center-source; optional help-center-webhook-secret

Coverage: Coverage is limited to Cognidesk local help-center source search/fetch/readiness, built-in HTTP source adapters, remote HelpCenterClient overrides, and Cognidesk HMAC webhook normalization.

Boundary: Remote provider transport, 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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk-plus-support-slice
Documentation https://github.com/amzn/selling-partner-api-sdk
Directions receive-only, send-only, bidirectional
Capabilities receive, read-provider-object, search-provider-object, create-provider-object, delete-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 is limited to Cognidesk marketplace support primitives, not full Amazon SP-API ownership.

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 JavaScript SDK; Amazon prebuilt JavaScript SDK tutorial; Amazon SP-API Orders v0 reference; Amazon SP-API Orders v2026-01-01 reference; plus 2 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, delete-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-provider-client, 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 official-sdk
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 REST, discord.js Routes 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-provider-client, rcs-webhook-client-token

Coverage: Runtime coverage uses the official @google/rcsbusinessmessaging SDK for selected RCS for Business support workflows: agentMessages text/media/card sends, agent events, phone capability checks, and file create/upload helpers.

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 provider-rest-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: provider REST adapter message sends, template payload construction, media upload/get/download, 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 support-workflow-subset
Adapter coverage partial
Implementation support-workflow-adapter
Documentation https://developer.apple.com/documentation/appstoreconnectapi
Directions receive-only, send-only, bidirectional
Capabilities receive, draft, send, read-provider-object, search-provider-object, delete-provider-object
Provider setup required appstore-api-key, appstore-app-id; optional appstore-review-response-policy

Coverage: Cognidesk adapter coverage is scoped to App Store Connect customer review list/read/response workflows.

Boundary: The SDK user decides review triage, sentiment classification, public-response approval, localization, escalation, and retention policy.

Evidence: App Store Connect API overview; App Store Connect OpenAPI specification (openapi.oas.json sha256:352ccca83f6460761bc513b87ed667974afb1347649d49b7cd98cd9041236bec); App Store Connect JWT tokens; Apple App Store Server Node.js Library; plus 1 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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://developers.google.com/android-publisher/api-ref/rest
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: Cognidesk adapter coverage is scoped to Google Play review list/read/reply workflows.

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 API; Google Play Android Publisher reviews resource; Google APIs Node.js client; @googleapis/androidpublisher package.

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 provider-api-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://www.npmjs.com/package/twilio
Directions receive-only, send-only, bidirectional
Capabilities receive, send, schedule, read-provider-object, search-provider-object, twilio.webhook-signature
Provider setup required twilio-account, twilio-sms-sender

Coverage: Implements normalized SMS/MMS send, read, list, cancel, readiness, webhook, and Twilio SDK client access with the official Twilio Node helper library.

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 Node helper library; Twilio Messaging API overview; Twilio Message resource; Twilio webhook security.

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-provider-client, 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 3 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; plus 1 more.

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 provider-rest-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
Provider setup required freshdesk-domain, freshdesk-api-key; optional freshdesk-webhook-secret

Coverage: Implementation uses the official @freshworks/freshdesk JavaScript SDK by default when domain and apiKey are configured.

Boundary: Ticket forms, required fields, statuses, products, groups, SLAs, automations, and agent permissions are SDK-user configuration.

Evidence: Freshdesk API v2 reference; Freshworks Freshdesk SDK; Freshworks API SDK; Freshworks API SDK repository; plus 1 more.

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 support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://dev.frontapp.com/docs/core-api-overview
Directions bidirectional
Capabilities create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff
Provider setup required front-api-access; optional front-base-url

Coverage: Runtime calls use the built-in Front REST adapter by default because no viable maintained backend Core/Channel API JavaScript client was verified.

Boundary: Inbox IDs, channel IDs, teammate assignment, tags, message visibility, credentials, retries, pagination, and API base URL selection are SDK-user configuration. Multipart attachments are rejected by JSON operation helpers and require SDK-user direct multipart handling.

Evidence: Front Core API overview; Front API overview; Front Create message; Front Create conversation reply.

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 support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://developers.gorgias.com/
Directions bidirectional
Capabilities create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff
Provider setup required gorgias-base-url, gorgias-api-access

Coverage: Runtime coverage is provided through the built-in Gorgias REST adapter when baseUrl and accessToken/apiKey are configured.

Boundary: Domain URL, ticket channels, message channels, macros, Shopify context, automations, and visibility are SDK-user configuration.

Evidence: Gorgias developer docs; Gorgias REST API credentials; Gorgias Create ticket; Gorgias Create ticket message; plus 2 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 provider-rest-adapter
Documentation https://developer.helpscout.com/mailbox-api/
Directions bidirectional
Capabilities create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff
Provider setup required help-scout-api-access; optional help-scout-base-url

Coverage: No official maintained backend JavaScript Inbox API client was verified; Help Scout's official Inbox SDK is PHP, and the official JavaScript SDK is for Apps UI context.

Boundary: Mailbox IDs, thread types, assignment, workflow rules, and customer visibility are SDK-user configuration.

Evidence: Help Scout Inbox API; Help Scout JavaScript SDK; Help Scout open-source clients.

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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/HubSpot/hubspot-api-nodejs
Directions receive-only, send-only, bidirectional
Capabilities read-provider-object, send, create-provider-object, update-provider-object, search-provider-object, draft, link-provider-object
Provider setup required hubspot-private-app-token

Coverage: Coverage is scoped to normalized ticketing support operations implemented by typed handlers.

Boundary: Ticket pipelines, stages, owners, custom properties, association labels, scopes, and portal-specific workflow policy are SDK-user configuration.

Evidence: HubSpot Node client; HubSpot CRM Tickets API guide; HubSpot CRM Notes API guide; HubSpot CRM search guide.

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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://github.com/intercom/intercom-node
Directions receive-only, send-only, bidirectional
Capabilities read-provider-object, send, create-provider-object, update-provider-object, search-provider-object, draft
Provider setup required intercom-access-token

Coverage: Coverage is scoped to normalized ticket and conversation operations implemented by typed handlers.

Boundary: Ticket types, attributes, states, assignment targets, teammate availability, scopes, and public/private reply policy are SDK-user configuration.

Evidence: Intercom Node client; Intercom Tickets API; Intercom Conversations API.

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 support-workflow-subset
Adapter coverage partial
Implementation provider-rest-adapter
Documentation https://developer.kustomer.com/
Directions bidirectional
Capabilities create-provider-object, read-provider-object, update-provider-object, search-provider-object, handoff
Provider setup required kustomer-api-access, kustomer-api-permissions; optional kustomer-base-url

Coverage: Kustomer's developer surface separates REST APIs for backend systems from Apps Platform and Chat SDK packages.

Boundary: SDK user configuration owns auth, tenancy, pagination, retries, rate limits, and provider response normalization policy.

Evidence: Kustomer developer portal; Kustomer REST APIs portal; @kustomer/apps-server npm package; @kustomer/apps-server-sdk npm package; plus 3 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 official-sdk
Documentation https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/overview
Directions bidirectional
Capabilities create-provider-object, draft, 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-web-api Dataverse helper; Dynamics 365 Customer Service incident table reference; Dataverse EntityDefinitions metadata queries; plus 8 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 provider-rest-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 optional oracle-service-provider-client, 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 provider-rest-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 optional pega-customer-service-provider-client, pega-customer-service-instance, pega-customer-service-api-access

Coverage: Runtime coverage uses the built-in Pega DX REST adapter when baseUrl plus access credentials are provided; a host-injected PegaCustomerServiceProviderClient remains available as an override.

Boundary: The built-in adapter covers selected Pega DX case and assignment-action operations only; hosts can still inject a PegaCustomerServiceProviderClient for custom authentication, retries, or endpoint policy.

Evidence: Pega DX API overview; Pega DX API cases endpoints; Pega DX API POST /cases; Pega DX API GET /cases; plus 7 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 maintained-library
Documentation https://github.com/jsforce/jsforce
Directions receive-only, send-only, bidirectional
Capabilities read-provider-object, send, create-provider-object, update-provider-object, search-provider-object, draft
Provider setup required salesforce-instance, salesforce-oauth-access

Coverage: Coverage is scoped to Service Cloud Case support workflows implemented by typed handlers.

Boundary: Record types, required fields, queues, owners, assignment rules, Flow automation, field-level security, and Service Cloud licenses are SDK-user configuration.

Evidence: JSforce; Salesforce REST API resources; Salesforce Case object reference; Salesforce CaseComment object reference; plus 1 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 optional sap-service-cloud-provider-client, sap-service-cloud-instance, sap-service-cloud-api-access

Coverage: Runtime coverage uses the built-in SAP Service Cloud OData adapter backed by the official SAP Cloud SDK HTTP client for selected ServiceRequestCollection create, read by ObjectID, update, search, and readiness workflows when baseUrl plus access credentials are provided.

Boundary: SAP tenant exposure, communication arrangements, required fields, statuses, code lists, workflow rules, and extensions are SDK-user host-client 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 official-sdk
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, send, draft, attach, handoff
Provider setup optional servicenow-instance, servicenow-api-access, servicenow-raw-client

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
Integration Zendesk Integration
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 support-workflow-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://www.npmjs.com/package/node-zendesk
Directions bidirectional
Capabilities create-provider-object, read-provider-object, update-provider-object, search-provider-object, send, draft, attach, handoff
Provider setup required zendesk-instance, zendesk-api-access

Coverage: Coverage is a Cognidesk support workflow adapter backed by the node-zendesk provider SDK.

Boundary: Tenant fields, triggers, automations, macros, routing, requester identity, and outbound policy remain SDK-user configuration.

Evidence: node-zendesk package; Zendesk Node.js API client docs; Zendesk Support API OpenAPI; Zendesk Support Tickets API; plus 2 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 provider-rest-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 REST-backed 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 provider-api-subset
Adapter coverage standard
Implementation provider-rest-adapter
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-provider-client, whereby-organization, whereby-room-template, whereby-webhook-signing-secret

Coverage: Coverage includes generated per-operation types/functions for every operation in Whereby's official public REST OpenAPI spec; runtime calls default to a package-owned REST adapter when apiKey/baseUrl/fetch options are provided.

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/docs/rivet/javascript/
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-video-provider-client, zoom-webhook-secret-token

Coverage: Coverage includes generated per-operation functions for every operation in Zoom's official Meetings API Hub OpenAPI spec. Runtime uses Zoom's official @zoom/rivet Meetings SDK for mapped SDK operations when accessToken/getAccessToken/account OAuth credentials are provided.

Boundary: Runtime provider API calls use Zoom's official @zoom/rivet SDK when OAuth credentials are supplied, except for documented REST exceptions or explicit low-level REST transport options.

Evidence: Zoom Rivet for JavaScript; Zoom Rivet JavaScript repository; Zoom Meetings API Hub OpenAPI; Zoom Meetings API reference; plus 2 more.

Voice Provider APIs

AWS Speech

Field Value
Integration AWS Speech Integration
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 standard
Implementation official-sdk
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
Integration Azure AI Speech Integration
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 standard
Implementation official-sdk
Documentation https://github.com/microsoft/cognitive-services-speech-sdk-js
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 adapts buffered Cognidesk voice turns through the Speech SDK; it does not expose continuous recognizer sessions as Cognidesk operations.

Evidence: Azure Speech SDK for JavaScript; Azure AI Speech SDK documentation.

Deepgram Voice

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 official-sdk
Documentation https://www.npmjs.com/package/@deepgram/sdk
Directions receive-only, send-only, bidirectional
Capabilities receive, send, media
Provider setup required deepgram-api-key

Coverage: Implements normalized Cognidesk speech-to-text and text-to-speech operations with the official Deepgram SDK.

Boundary: This package implements SDK-backed STT/TTS for Cognidesk speech pipelines, not Deepgram Voice Agent or Flux websocket sessions.

Evidence: Deepgram SDK package; Deepgram prerecorded audio STT; Deepgram Text-to-Speech REST.

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 provider-api-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://www.npmjs.com/package/@elevenlabs/elevenlabs-js
Directions send-only, receive-only, bidirectional
Capabilities send, receive, media
Provider setup required elevenlabs-api-key

Coverage: Implements normalized Cognidesk speech, transcription, and conversational session helpers with the official ElevenLabs JavaScript SDK.

Boundary: Realtime WebSocket transport behavior, telephony setup, batch calling, call recording policy, consent, retention, and live agent routing remain SDK-user/provider configuration.

Evidence: ElevenLabs JavaScript SDK package; ElevenLabs API reference; ElevenLabs Speech to Text; ElevenLabs Text to Speech.

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 https://www.npmjs.com/package/drachtio-srf
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 platform, registrar, SBC, and RTP/SRTP media engine are intentionally out of scope for this package.

Evidence: drachtio-srf npm package; drachtio-srf repository.

Google Cloud Speech

Field Value
Integration Google Cloud Speech Integration
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 standard
Implementation official-sdk
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
Integration OpenAI Realtime Voice Integration
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 standard
Implementation official-sdk
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.

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 provider-api-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://www.npmjs.com/package/twilio
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

Coverage: Implements normalized call-control, TwiML media stream, webhook, readiness, and raw Twilio helper-client access with the official Twilio Node helper library.

Boundary: Live call readiness depends on the SDK user's Twilio account, voice-capable numbers, regions, webhooks, and account permissions.

Evidence: Twilio Node helper library; Twilio Programmable Voice API; Twilio Call Resource; Twilio webhook security.

Vonage Voice

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 provider-api-subset
Adapter coverage partial
Implementation official-sdk
Documentation https://www.npmjs.com/package/@vonage/server-sdk
Directions inbound-only, outbound-only, bidirectional
Capabilities receive, send, media, transfer, voice.webhook-signature
Provider setup required vonage-application; optional vonage-webhook-signature

Coverage: Implements normalized Vonage Voice call-control, NCCO, webhook, readiness, and raw SDK access with the official Vonage server SDK.

Boundary: Live call readiness depends on the SDK user's Vonage application, numbers, webhook URLs, regions, and account permissions.

Evidence: Vonage Server SDK package; Vonage Voice API reference; Vonage Voice webhooks; Vonage NCCO reference.

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 official-sdk-plus-support-slice
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.