Integrations

Every environment your customers already work in. Labelled honestly.

A destination is not a checkbox. It is an OAuth model, a consent screen somebody reads, an approver with a calendar, a permission system, a credential that expires and a set of failures with names. Each page below explains what a forward deployed engineer actually deals with there, and what Meetext owns of it.

AtlassianGoogle WorkspaceHubSpotMicrosoft 365SalesforceServiceNowSlack

Destinations

Where your product gets installed. Each one is a real installation into somebody else's company, and a shallow one is worse than none. 7 install today and every one is in preview: the adapters are complete and none has yet run against a real provider account.

Preview

Atlassian

Jira and Confluence, cloud and data center, which are different products.

Jira and Confluence Cloud ship. Data Center is declared by the adapter and refused at deploy time: it is the customer's own infrastructure on their own upgrade schedule, which is a different adapter rather than a setting.

Preview

Google Workspace

A Google Chat app in the customer's own Workspace domain. Chat ships; other surfaces do not.

Google Chat ships. The Docs and Gmail add-on, Drive and Gemini surfaces are declared by the adapter and refused at deploy time rather than failing later.

Preview

HubSpot

A public app installed per portal, with scope changes that force reinstalls.

Preview

Microsoft 365

The same shape against Microsoft Entra, where admin consent is a distinct step.

Preview

Salesforce

Where enterprise implementation actually lives, and the hardest destination to do honestly.

Preview

ServiceNow

Instances, update sets and scoped applications, where configuration drift is the default.

Preview

Slack

A bot in the customer's own workspace, installed by someone who works there.

What these words mean

Available: A complete adapter, and every part of the deployment lifecycle proven against the real provider. Not merely written: run.
Preview: The adapter is real and something is incomplete, either a part of the destination or real-provider proof for part of the lifecycle. The gap is stated on the page rather than discovered during an evaluation.
Planned: Meetext models the destination and no adapter exists yet. Nothing to install, and nothing to sign up for.
Bring your own: Not a destination. Something you bring yourself, reached through a source rather than shipped to through an adapter.

These labels are generated from a proof registry in the deployment code, not written here. Available requires every part of the deployment lifecycle to have actually run against the real provider, and a test refuses the claim without dated evidence. Nothing has earned it yet.

Sources

Where your capabilities come from. Many, because you should not have to build anything new to start. Whichever you connect normalises into the same internal format, so every destination behaves identically.

The asymmetry is the product. Sources are open ended. Destinations are few and deep.

MCP server

Available

Streamable HTTP, protocol versions negotiated per client.

OpenAPI document

Available

OpenAPI 3, JSON or YAML, by URL or upload.

Repository

Available

FastAPI, Flask, Django, Next.js and Express route discovery.

Bring your own

Internal APIs Reached as an OpenAPI document or a repository scan.
Databases Through your own service. Meetext never holds a database credential.
Snowflake Through an MCP server or API you already run in front of it.
Custom enterprise systems Anything you can describe as capabilities becomes deployable.

If your customers live somewhere that is not listed, tell us which and how many. That is how the next destination gets picked.

2 environments free

Stop assigning an engineer to every customer.

Connect a source, publish, and send one link. Your next enterprise customer installs itself.

Start free Talk to us

2 customer environments free, forever. No card required.