Skip to main content
TextMine integrations fall into several shapes: OAuth-connected providers, Vault-level native integrations, workflow integrations, Zapier automations, the TextMine MCP server, agent self-service signup, and Workbench MCP/provider imports. Availability depends on organisation configuration, enabled features, user connection status, and provider capability support.

Integration directions

DirectionWhat it means
Import into WorkbenchBring an external file into the current Workbench chat as temporary context.
Import into VaultSave a file into the durable Vault pipeline for processing, extraction, review, workflows, and possible publication to Legislate.
Submit out of TextMineSend outputs, documents, reports, or files to an external system.
Expose TextMine to agentsLet external agents call TextMine tools through the hosted TextMine MCP server or Public API V3.
Discover API docsLet agents use the developer hub and ReadMe MCP surface for exact schemas and API operation discovery.
Automate with ZapierLet Zapier triggers, searches, and actions call TextMine through Public API V3.
Provision third-party agentsCreate a multitenant, non-enterprise agent organization, service-account API key, and billing account through agent self-service signup.

Agent and automation entry points

Entry pointUse it for
TextMine MCP serverMCP-compatible agent clients that need TextMine-hosted tools backed by Public API V3.
Agent self-service signupExternal agents that need a TextMine organization, service-account API key, billing account, Public API V3 access, and MCP access.
API and developer docsPublic API V3 reference, exact operation IDs, ReadMe MCP, and client setup guides.
For agentsRouting rules for agents deciding between Mintlify, Public API V3, TextMine MCP, ReadMe MCP, Workbench, and the web app.
ZapierNo-code automations that call TextMine document, record, task, report, workflow, and agent actions through Public API V3.
/.well-known/textmine-agent.jsonMachine-readable agent onboarding metadata for signup, billing, Public API V3, and MCP.

User-connected providers

These providers are connected by users or organisations and expose explicit capabilities.
ProviderConnection shapeCurrent capabilities
Google DriveOAuthCreate documents, list folders, list files in folders, download files, and import files into Workbench or Vault.
SharePointOAuth/native integrationList folders, list files in folders, download files, import files, and submit workflow outputs where enabled.
NotionOAuthCreate pages in a connected Notion workspace.

Vault native integrations

Vault native integrations are configured against a Vault and can participate in upload/import or workflow processes.
IntegrationWhat it supports
ServiceNowConfigure a Vault-level ServiceNow connection, test access, list configured table records, list record attachments, and import selected attachments into Vault.
DocuSignConfigure, test, enable/disable, and import agreement/envelope material where enabled.
SharePointConfigure, test, browse, import, and submit outputs where enabled.
OpenCorporatesUse company data as a source for enrichment or import flows.
SEC/EDGARSearch EDGAR filing text, fetch SEC filings, and use SEC company/adviser sources in upload or workflow flows.
Box, Ariba, Finastra, Companies HouseNative or legacy import/source surfaces visible in document import flows where configured.
Vault emailRoute inbound email and attachments into Vault or workflow-triggered document processing.

ServiceNow details

The ServiceNow integration can be configured per Vault. Supported behavior includes:
  • Basic authentication or OAuth client credentials, depending on configuration.
  • Instance URL, table name, encoded query, and display-value settings.
  • Default table support such as ast_contract where configured.
  • Optional field mappings for number, name, supplier, and status display.
  • Connection testing before saving.
  • Record browsing with search, limit, offset, and optional table override.
  • Attachment browsing for selected records.
  • Importing selected attachments, selected records, or matching records into Vault.
  • Import modes: UPSERT, NEW_RECORDS_ONLY, and UPDATE_EXISTING_ONLY.
Workflow block import_from_integration currently supports ServiceNow for pulling records and linked attachments into the workflow Vault. It can use a saved table/query configuration or override the table/query for a run.

Workflow integration blocks

Workflows can use integration blocks without requiring a human to operate the UI each time.
BlockIntegration behavior
api_requestRuns a structured REST request for API integrations, callbacks, and webhooks.
webhookCalls an outbound webhook URL or HTTP callback.
import_from_integrationPulls records and linked attachments from an external system into the workflow Vault. Currently supports ServiceNow.
submit_to_integrationPushes workflow outputs to an external system. Current implementation supports SharePoint output.
search_edgar_filingsSearches SEC EDGAR filing text and saves matching filings for later steps.
fetch_sec_filingsImports recent SEC filings for companies in scope.
send_emailSends email notifications with optional output/report/document attachments.
See Workflow blocks for the full workflow catalog.

Workbench MCP/provider scan and import

Workbench can scan connected providers in a controlled sequence:
  1. List enabled providers for the current Workbench session.
  2. List folders when the provider supports folder browsing.
  3. List or search files in a selected folder.
  4. Import selected files into the current Workbench chat.
  5. Save imported files into Vault only when the user explicitly asks and approves.
The key capabilities are:
Workbench capabilityWhat it does
list_mcp_providersShows connected providers and capabilities.
list_mcp_foldersBrowses provider folders.
list_mcp_filesLists or searches provider files.
import_mcp_documentsImports selected files as Workbench context.
import_uploaded_documentsSaves uploaded or imported Workbench files into Vault after approval.
Workbench imports selected files rather than scanning an entire external repository. Agents should name the provider, folder, file, or query whenever possible.

Official MCP/provider catalog

The current provider catalog includes official MCP or source integrations that can be connected manually where enabled. Capabilities are declared per provider.
ProviderProvider IDDeclared capabilities
BoxboxSearch documents, list folders, list files, download files.
DropboxdropboxSearch documents, list folders, list files, download files.
Amazon S3amazon-s3Search documents, list folders, list files, download files.
DocuSigndocusignSearch documents, download files.
iManageimanageSearch documents, list folders, list files, download files.
NetDocumentsnetdocumentsSearch documents.
HighQthomson-reuters-highqSearch documents.
IroncladironcladSearch documents.
CourtListenercourtlistenerSearch documents.
CoCounsel Legalthomson-reuters-cocounselSearch documents.
GovInfogovinfoSearch documents, download files.
Federal Registerfederal-registerSearch documents, download files.
Regulations.govregulations-govSearch documents.
Congress.govcongress-govSearch documents.
Open Statesopen-statesSearch documents.
AtlassianatlassianSearch documents.
SalesforcesalesforceSearch documents.
AWSawsSearch documents.
AzureazureSearch documents.
Google Cloudgoogle-cloudSearch documents.
FactSetfactsetSearch documents.
LSEGlsegSearch documents.
StripestripeSearch documents.
XeroxeroSearch documents.
SnowflakesnowflakeSearch documents.
DatabricksdatabricksSearch documents.
Manual provider connections store an endpoint URL and optional credential metadata. Secret-like metadata is sanitized and credentials are stored separately. A provider must be connected and Workbench-enabled before Workbench can use it for browsing or import.

Zapier

Use Zapier when a Zap should automate TextMine work through Public API V3. Zapier uses a TextMine service-account API key from agent self-service signup or TextMine provisioning, plus the matching Public API base URL. Open TextMine on Zapier to browse supported pairings and templates.

TextMine MCP and developer hub

The TextMine MCP server exposes TextMine tools to external agents. The developer hub provides Public API V3 reference, examples, client setup, and ReadMe MCP discovery. Use API and developer docs when a developer or agent needs exact operation IDs or setup instructions.