Skip to main content
Use these examples as starting points for repeatable TextMine automations. They are deliberately written as patterns rather than rigid templates, because most workflows need to be scoped to a Vault, document type, approval policy, and integration setup. For the full block catalog, see Workflow blocks.

​
Financial services

Financial services workflows usually prioritize intake control, source evidence, exception handling, and audit-ready outputs.
WorkflowTriggerCore blocksOutput
Credit agreement covenant reviewDocument imported or manual runWait for processing, extract tables, run playbook, calculate values, request approval, send reportCovenant exceptions, source-linked review, approval record
SEC filing monitorScheduledFetch SEC filings, search filings, extract text, run general action, create alert, send emailFiling summary and exceptions for monitored issuers
Fund document risk scanDocument processedDefault tags, aggregation tags, entity checks, AI review, report templateRisk summary by fund, party, obligation, and date
KYC or onboarding evidence reviewIntake formUpload to Vault, wait for processing, extract entities, reconcile data, create or update recordReviewed customer/vendor record with evidence links
Regulatory change impact checkScheduled or manualEnrich values, search filings or sources, run agent, create alertsImpact summary and affected document list

​
Example: covenant exception workflow

  1. Start when a credit agreement or amendment is imported into a lending Vault.
  2. Wait for processing and table extraction.
  3. Run default tags for borrower, facility amount, dates, governing law, and key covenants.
  4. Apply a covenant playbook.
  5. Use calculate_values to compare extracted thresholds against policy limits.
  6. Use reconcile_data to flag breaks between agreement text, tables, and accepted policy outputs.
  7. Request approval from legal or credit risk for exceptions.
  8. Send a report with source passages, table references, and reviewer decisions.
Use this pattern when the answer must be defensible to risk, compliance, or audit teams. Legal workflows usually focus on review consistency, negotiation guidance, clause risk, publication, and reusable work product.
WorkflowTriggerCore blocksOutput
NDA review and escalationDocument importedWait for processing, apply playbook, condition on red flags, request approval, send emailApproved NDA review or escalation packet
Contract playbook applicationManual or document processedApply playbook, AI review, fill template, send reportClause-by-clause review memo
MSA deviation trackerDocument processedDefault tags, chained tags, compare to accepted output, create recordDeviation register with evidence
Signature and execution checkDocument importedEmbedded image detection, image tags, entity tags, AI reviewSignature/completion checklist
Publish validated contractsApproval completedSend to Legislate, create alert, update recordPublished archive document and audit trail
  1. Start manually from Vault or after document processing.
  2. Confirm the document type and processing status.
  3. Apply the correct playbook for the agreement type.
  4. Extract parties, dates, governing law, assignment, termination, liability, confidentiality, and data protection fields.
  5. Use chained tags to connect extracted parties to obligations and rights.
  6. Route red flags to a reviewer.
  7. Generate a report or Word artifact for the matter file.
  8. Publish to Legislate after validation if the document should become part of the archive.
Use this pattern when a legal team wants consistent review outputs without turning every review into a bespoke Workbench conversation.

​
Risk advisory

Risk advisory workflows usually combine document review, sampling, evidence, and exception reporting.
WorkflowTriggerCore blocksOutput
Control evidence sampleScheduled or manualSample population, wait for processing, extract tags, AI review, reportSample register and exceptions
Third-party risk reviewIntake form or provider importUpload to Vault, extract entities, enrich values, apply playbook, create recordRisk profile with evidence and recommended action
Policy compliance sweepScheduledSelect documents, run aggregation tags, decision matrix, create alertsCompliance exception queue
Internal audit document testManualExtract tables, compare to accepted output, reconcile data, send reportTest result with supporting documents
Regulatory impact assessmentScheduledEnrich values, run agent, lookup records, create alertsImpacted controls, vendors, contracts, or teams

​
Example: third-party risk workflow

  1. Start from an intake form or provider import.
  2. Upload questionnaires, contracts, security reports, or policies to Vault.
  3. Wait for processing and run default tags.
  4. Extract entities such as supplier, parent company, locations, systems, and services.
  5. Enrich supplier context where configured.
  6. Apply a risk playbook or decision policy matrix.
  7. Create or update a supplier risk record.
  8. Request approval for high-risk findings.
  9. Send a final report and retain source evidence.
Use this pattern when the workflow must produce a structured risk outcome rather than a one-off summary.

​
Procurement

Procurement workflows usually prioritize supplier intake, obligation extraction, renewal visibility, approval routing, and integration with source systems.
WorkflowTriggerCore blocksOutput
Supplier contract intakeIntake form or email receivedUpload to Vault, wait for processing, default tags, entity tags, create recordSupplier/contract record with extracted terms
Renewal and notice monitoringScheduledLookup records, check dates, create alert, send emailRenewal queue with owners and dates
ServiceNow contract importScheduled or manualImport from integration, wait for processing, extract tags, create/update recordUpdated contract inventory from ServiceNow
Spend and fee table extractionDocument processedExtract tables, chained tags, calculate values, reportPricing and fee summary
Procurement approval packetManualApply playbook, request approval, fill template, send emailApproved procurement memo and supporting evidence

​
Example: renewal monitoring workflow

  1. Run on a schedule against a procurement Vault or contract record schema.
  2. Look up contracts with renewal, expiry, or notice dates within the review window.
  3. Confirm dates against validated Vault tags or record evidence.
  4. Create alerts for owners.
  5. Send a report to procurement and legal stakeholders.
  6. Update records when decisions are made.
Use this pattern when procurement needs durable operational follow-up rather than another spreadsheet reminder.

​
Design guidance

Before building any workflow, define:
  • The business event that should trigger it.
  • The Vault, provider, document type, or record scope.
  • The human decisions that require approval.
  • The extracted tags, tables, entities, or records that downstream steps depend on.
  • The expected output: alert, report, record, email, Legislate publication, external submission, or all of these.
  • The run history details needed for audit and debugging.
Agents should present workflows as a proposed sequence first when the workflow will send messages, create records, change assignments, call integrations, or publish documents.