Automation library · Research and reporting

Contract extraction, risk analysis & compliance automation

Started by another system calling it, and works across Gmail, Postgres, Slack and in-memory vectors. It puts OpenAI behind a retrieval step, so answers are drawn from documents you supply rather than from the model alone. 23 steps, 1 branch: large, and worth reading before you trust it with anything live.

LargeCalls a model: OpenAIRetrieval

23 stepsLarge: read it before trusting it with anything live
1Branch: places the flow splits
0Loops or waits
4Services it connects to

The flow

Starts it 3Model 7Logic 5Service 8

The steps in the order they run, from what starts it.

  1. 1Schedule Contract ReviewSchedule triggerStarts it
  2. 2Webhook - Contract UploadWebhookStarts it
  3. 3Gmail - Contract EmailsGmail triggerStarts it
  4. 4Text Splitter - Clause ChunkingText Splitter Recursive Character Text SplitterModel
  5. 5OpenAI EmbeddingsEmbeddings Open AiModel
  6. 6OpenAI Chat Model - Compliance AnalysisLm Chat Open AiModel
  7. 7Structured Parser - Compliance ResultsOutput Parser StructuredModel
  8. 8Workflow ConfigurationSetLogic
  9. 9Merge All Contract SourcesMergeLogic
  10. 10Document Loader - Contract ProcessingDocument Default Data LoaderModel
  11. 11Vector Store - Contract ClausesVector Store In MemoryModel
  12. 12AI Agent - Compliance CheckerAgentModel
  13. 13Fetch Contracts from RepositoryHttp RequestService
  14. 14Extract Contract ContentExtract From FileService
  15. 15Calculate Risk ScoreCodeLogic
  16. 16Store Compliance ResultsPostgresService
  17. 17Route by Risk LevelSwitchLogic
  18. 18Alert - High Risk ContractsSlackService
  19. 19Send to Dashboard APIHttp RequestService
  20. 20Update CLM SystemHttp RequestService
  21. 21Update ERP SystemHttp RequestService
  22. 22Prepare Audit TrailSetLogic
  23. 23Store Audit TrailPostgresService

How it's built

Starts on
Another system calling it
Steps
23, with 1 branch
Size
Large: read it before trusting it with anything live
Connects to
Gmail, Postgres, Slack, in-memory vectors
Model
OpenAI
Retrieval
Answers are drawn from documents you supply, not from the model alone

Questions

What does it need to run?

An n8n account, plus your own Gmail, Postgres, Slack and in-memory vectors accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

Yes. It calls OpenAI. Its answers draw on documents you give it, not on the model alone. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Take your time. At 23 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 23 steps before you point it at anything that matters.