Jamf Software Compliance Reporting to Slack - n8n Workflow

IT Administrators and DevOps teams using Jamf Pro for macOS fleet management.
Organizations needing automated, real-time reporting on software patch compliance.
Users looking for advanced examples of HTTP Request and Code n8n node usage.
Anyone seeking efficient n8n templates for internal monitoring.

This essential monitoring n8n workflow provides immediate visibility into software patching health across your organization's devices managed by Jamf Pro. Instead of manually checking patch dashboards, this automation proactively pulls compliance data (like which software is up-to-date versus out-of-date). The data is then perfectly formatted using a custom n8n node (Code node) into a Slack Block Kit message, delivering a clear, actionable summary directly to your IT team's Slack channel. This powerful n8n solution ensures security teams are immediately aware of compliance drifts, making this one of the most useful n8n templates for infrastructure management. The n8n workflow starts with a manual n8n trigger but can easily be converted to a time-based n8n trigger for scheduled daily reports.

1. The n8n workflow is initiated by a Manual n8n trigger (which should ideally be replaced by a Schedule n8n trigger for daily runs).


2. The Jamf Server n8n node sets the base URL for API communication.


3. The Get Software Title/ID HTTP Request n8n node queries the Jamf API to retrieve a complete list of all managed software titles.


4. The ID List Filter n8n node filters this list, keeping only the specific software IDs defined by the user for monitoring (e.g., specific browsers or applications).


5. The Get Patch Summary:ID HTTP Request n8n node iterates through the filtered IDs to fetch the detailed patch summary for each selected item.


6. The Manual Field Mapping Set n8n node cleans the raw data and creates a direct link back to the relevant Jamf application page.


7. The Block Formatting Code n8n node customizes the output, converting the summary statistics (up-to-date, out-of-date counts) into a visually rich Slack Block Kit structure.


8. Finally, the Slack Channel n8n node posts the beautifully formatted compliance report, completing the n8n workflow execution.

1. Import: Copy the provided n8n workflow JSON and import it into your n8n instance using the "New" button and selecting "Import from JSON."


2. Jamf Configuration (Set Node): Locate the Jamf Server n8n node. Change the value of the server key from yourServer to your actual Jamf Cloud server domain (e.g., acme-corp).


3. Credentials: This n8n workflow uses OAuth2 API authentication for the Jamf HTTP Request n8n nodes. You must set up a Generic Credential Type named oAuth2Api with the appropriate Jamf tokens, or link existing Jamf credentials to the two HTTP Request n8n nodes.


4. Filter Customization: Go to the ID List Filter n8n node and update the placeholders with the actual numerical IDs of the software titles you wish to track. If you need to monitor more items, add additional equals conditions in this n8n node.


5. Slack Setup: Connect the Slack Channel n8n node using your Slack API credentials and select the target channel ID where the reports should be posted.


6. Activation: Once configured, set the n8n trigger to "Active" (or convert the Manual n8n trigger to a Schedule n8n trigger).

Click (Manual Trigger n8n trigger): Initiates the entire n8n workflow run. Typically used for testing or quick, on-demand execution.
Jamf Server (Set n8n node): Stores the base URL for the Jamf Cloud instance, allowing other n8n nodes to reference it dynamically. Key Configuration: Sets the variable server.
Get Software Title/ID (HTTP Request n8n node): Connects to the Jamf API (/api/v2/patch-software-title-configurations) to retrieve all available patch data. Requires OAuth2 API authentication.
ID List (Filter n8n node): Selectively processes items. Function: Ensures only the pre-defined software titles are carried forward to the summary retrieval steps, significantly optimizing the n8n workflow efficiency. This is a critical configuration point.
Get Patch Summary:ID (HTTP Request n8n node): Fetches detailed compliance statistics (patch-summary) for each filtered software title ID. Uses an expression referencing the server from the Jamf Server n8n node.
Manual Field Mapping (Set n8n node): Restructures and renames complex API fields into simple variables (Title, Latest version, up To Date, etc.) and calculates the direct Jamf application URL using data from previous n8n nodes.
Block Formatting (Code n8n node): Custom scripting to transform the clean data structure into an array of Slack Block Kit objects, ensuring the final message is aesthetically pleasing and easy to read. This is a powerful application of the n8n node scripting capability.
Slack Channel (Slack n8n node): Final action. Function: Sends the compiled Block Kit message to the specified Slack channel, completing the automation flow. This is the final step in this useful n8n templates example.