Skip to content

Available-on-Request Integrations

Some integrations need a conversation before they go live. The capture mechanism exists - we just haven’t templated the self-serve onboarding because the customer set asking for it has been small or because the platform’s enterprise terms vary by tenant. The fastest path is to tell us what you need, and we’ll wire it up.

The following pills on the platform integrations page carry the Available on request badge. We can capture them today; setup is concierge.

Trader pings, analyst commentary, file shares across the Bloomberg Terminal’s chat system. We archive in native format, preserving the audit trail your supervisors and examiners expect. Bloomberg integrations require firm-side enterprise enablement; tell us about your Bloomberg tenant and we’ll scope.

Phone calls, SMS, MMS, and any platform built on Twilio. Comma can ingest the call/message logs and recordings directly from your Twilio account. Authentication is a Twilio API key pair scoped to the archive surfaces you want.

Inbound and outbound voice calls of business contacts, including caller ID, timestamps, duration, and the recording itself. Source paths vary by tenant (carrier recording, soft-phone integration, BYOD), so this is a setup-side conversation rather than a single OAuth flow.

Video, transcripts, in-meeting chat, and full metadata for every Webex meeting. Comma uses Webex’s compliance/archive APIs to capture meetings already covered by your Cisco enterprise plan. We need your tenant info and an admin to grant the scopes.

Direct and channel text exchanges, files, GIFs, whiteboards, reactions, edits and deletes, read receipts. Same Webex enterprise plan as Meetings; same concierge setup.

Sales Cloud, Marketing Cloud, Pardot, and Chatter content - messages, attachments, comments, polls, posts - captured in native format. Salesforce’s per-tenant variation (objects, custom fields, org-specific permission models) means we scope each install.

Project descriptions, comments, attachments, full issue history. Jira capture pairs naturally with Confluence, which is self-serve. We can wire Jira alongside it for engineering-led firms.

Anything not on the platform integrations page is also fair game. We’ve onboarded customer-specific platforms before via:

  • Vendor compliance/archive APIs - most enterprise SaaS exposes one even if it isn’t documented publicly
  • Inbound Webhooks - the developer API for pushing messages from anything HTTP-capable
  • Custom connectors - for high-volume or unusual sources, we build a dedicated connector
  1. From the platform integrations page, click the Available on request pill for the platform you need
  2. You’ll land on Get in Touch
  3. Tell us the platform, your tenant size, and any specific surfaces you need archived
  4. We’ll come back with a scope, timeline, and the credentials/permissions we’ll need