Monitor software compliance with Jamf patch summaries in Slack
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 workflow has 8 nodes and runs manually, when you click “Execute workflow”. Along the way it connects Slack.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Jamf Server (Edit Fields (Set)): sets 1 field: server
- Get Software Title/ID (HTTP Request): calls an HTTP API
- ID List (Filter): keeps only the items that match a condition
- Get Patch Summary:ID (HTTP Request): calls an HTTP API
- Manual Field Mapping (Edit Fields (Set)): sets 5 fields: Title, Latest version, up To Date…
- Block Formatting (Code): runs custom JavaScript code
- 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.
Nodes used (6)
- HTTP Request
n8n-nodes-base.httpRequest - Filter
n8n-nodes-base.filter - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Manual Trigger
n8n-nodes-base.manualTrigger - Slack
n8n-nodes-base.slack
From the author
🧩 Jamf Patch Summary to Slack Stay on top of software patch compliance by automatically posting Jamf patch summaries to Slack. This helps IT and security teams quickly identify outdated installs and take action—without logging into Jamf. ✅ Prerequisites • A…