Triage museum microclimate excursions with OpenAI, Jira, Slack, and Google Drive
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 16 nodes and runs on a schedule (every day). Along the way it connects Postgres, OpenAI Chat Model, Jira Software and Google Drive and 1 more.
How it runs
Trigger: On a schedule (every day).
- Normalise Museum Scope (Edit Fields (Set)): sets or maps fields
- Fetch Current Sensor Readings (HTTP Request): calls an HTTP API
- Read Prior Sensor State (Postgres): uses Postgres
- Detect Material Deltas (Code): runs custom JavaScript code
- Check For Meaningful Change (If): checks a condition and branches into true / false
- Split Changed Sensor Items (Split Out): splits a list into separate items
- Merge: merges the data from its input branches
- Extract Conservation Risk (Information Extractor): extracts structured fields from text with AI, with model: Choose Conservation Model
- Write New Sensor State (Postgres): uses Postgres
- Score Conservation Severity (Code): runs custom JavaScript code
…plus 4 more steps. See the full node list below.
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.
Nodes used (14)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Postgres
n8n-nodes-base.postgres - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - Split Out
n8n-nodes-base.splitOut - Information Extractor
@n8n/n8n-nodes-langchain.informationExtractor - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - Switch
n8n-nodes-base.switch - Jira Software
n8n-nodes-base.jira - Google Drive
n8n-nodes-base.googleDrive - Merge
n8n-nodes-base.merge - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs every 30 minutes to pull museum microclimate sensor readings, compare them with prior state stored in Postgres, and, for meaningful excursions, uses OpenAI to extract conservation risk before creating a Jira task, posting a…