Extract and organize contract details from PDFs with Slack, GPT-4o, and Google Sheets
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 12 nodes and runs on Slack events. Along the way it connects OpenAI Chat Model, Slack and Google Sheets.
How it runs
Trigger: On Slack events.
- Check File Format (Switch): routes items into 3 branches
- Download PDF (HTTP Request): calls an HTTP API
- Convert Word to PDF (HTTP Request): calls an HTTP API
- Send Error Message (Slack): uses Slack
- Extract Text from PDF (Extract from File): extracts data from a file (pdf)
- Extract Text from PDF (Extract from File): extracts data from a file (pdf)
- Analyze Contract Content (AI Agent): runs an AI agent, with model: AI model; output parser: Structure Output
- Save to Google Sheets (Google Sheets): append
- Notify on Slack (Slack): uses Slack
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
- Still check Slack Trigger requires a signing secret on the Slack API credential (Receive Contract File).
Nodes used (9)
- Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Slack Trigger
n8n-nodes-base.slackTrigger - Switch
n8n-nodes-base.switch - HTTP Request
n8n-nodes-base.httpRequest - Extract from File
n8n-nodes-base.extractFromFile - Slack
n8n-nodes-base.slack - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Sheets
n8n-nodes-base.googleSheets
From the author
Managing contracts manually is time-consuming and prone to human error, especially when documents need to be shared, tracked, and stored across different tools. This workflow automates the entire process by capturing contract PDFs and Words uploaded to Slack,…