- Public Zapier page: TextMine on Zapier
- Developer API docs: developers.textmine.com
- Service-account provisioning: Third-party agent signup
Choose a setup path
Do not create or guess an API key outside the TextMine signup or provisioning flow.
Find TextMine in Zapier
Open TextMine on Zapier, then choose TextMine when building or editing a Zap. TextMine Settings also links to the TextMine Zapier app directory page when service-account access is enabled. Use that route when users need to discover supported triggers, searches, actions, and popular app pairings.Discover signup availability
Before asking a new third-party agent to connect Zapier, check whether self-service signup is available:
When signup is available, call
POST https://public-api.textmine.com/v3/third-party-agents/signup/self-service with credentialDeliveryPublicKey. The response returns encryptedApiKey; decrypt it only inside the trusted runtime or support-managed credential setup, then enter the decrypted service-account API key in Zapier. Do not expose the raw key to model-visible prompts, logs, or shared documentation.
Find values in TextMine Settings
For existing TextMine organizations, open Settings and find the Zapier section. The Zapier section shows:
If service-account access is not enabled for the existing organization, use Contact TextMine from the Zapier section.
Connect TextMine in Zapier
In Zapier, add or reconnect the TextMine app. Enter these fields:
For the UK multitenant deployment, enter
https://public-api.textmine.com as the Public API Base URL. Do not enter https://app.textmine.com or the internal API host.
Zapier tests the connection by calling the Public API health endpoint with the API key. If the key or base URL does not match the service account’s environment, authentication fails.
Available Zapier capabilities
The current Zapier integration is aligned to Public API V3 and includes visible triggers for:
Searches:
Actions:
Zapier does not create API keys from inside the Zap editor. Use third-party agent signup where available, or contact TextMine when a new existing-organization service-account key is required.
Tenant and permission behavior
The Public API base URL is an auth/config field so different TextMine deployments can connect to the correct Public API host. Users should use the URL shown in TextMine Settings or issued by TextMine for their service account. Do not prefill this field, and do not present a tenant picker or tenant-name list in Zapier; the service-account API key scopes the connection to its organization. The service account API key controls the organization, permissions, Vault access, available records, workflows, and other resources. Entering another customer’s Public API host does not grant access to that customer’s data. Keep API keys environment-specific. Do not use a staging key against production, or a production key against another deployment.Popular Zap patterns
Common TextMine automations include:- Send new processed document metadata to Google Sheets.
- Notify Slack when an agent task needs review or approval.
- Update HubSpot, Salesforce, or Pipedrive when TextMine extracts validated business records.
- Generate a TextMine AI report from newly imported documents.
- Import files from a connected storage app into Vault processing.
Troubleshooting
If signup is unavailable:- Check
https://public-api.textmine.com/v3/third-party-agents/signup/availabilityfor the availability message. - Confirm third-party access is enabled for the tenant.
- Confirm self-service signup is enabled for the deployment.
- Contact TextMine if the tenant or deployment is not configured.
- Confirm the API key was decrypted from the signup response or issued by TextMine for the correct organization.
- Confirm the Public API Base URL is the root URL only, without
/v3or another path. - Confirm the key and Public API URL belong to the same TextMine environment.
- Confirm the key has been decrypted and stored exactly.
- Contact TextMine if the Settings page says setup is required or if the key has expired.