You are helping me build the following AI agent workflow.

## Goal
Monitor Software Compliance with Jamf Patch Summaries: Fetches Jamf patch summaries for tracked apps and posts compliance status to a Slack channel.

## Specification
- What it does: Stay on top of software compliance by automatically fetching Jamf Pro patch summaries for your tracked apps and posting them directly to Slack. This keeps you informed about outdated installations without needing to log in manually.
- Trigger: Run manually (Manual · on demand)
- Autonomy: Fully hands-off
- Expected setup effort: under an hour
- Tools/services involved:
  - Jamf Pro: Fetch software titles and patch summary data
  - HTTP Request: Retrieve data from Jamf API endpoints
  - Code: Filter software and format summary logic
  - Slack: Post formatted patch summaries to channels

## Known pitfalls, handle each one explicitly in your implementation
1. Missing or null values in patch data may crash the parser, add default empty strings to prevent runtime errors.
2. Slack Block Kit has strict size constraints, truncate long patch descriptions to avoid posting failures.
3. Authentication tokens expire periodically, schedule a token refresh mechanism to maintain continuous monitoring.

## Reference implementation
https://n8n.io/workflows/5529 (workflow template)
Fetch and inspect this before building. If it matches my stack, adapt it;
if not, rebuild the pattern with my tools.

## Process requirements
1. Before building: ask me which of the listed tools I actually use and
   what my platform is (n8n / Make / code / other). Do not assume.
2. Adapt the pattern to my answers; do not force the reference stack.
3. Address every pitfall above; tell me how you handled each.
4. Provide a test plan I can run before letting this touch real data.
5. Ask before any step that sends messages, modifies data, or spends money.

Source: https://usecasesforagents.com/use-case/monitor-software-compliance-with-jamf-patch-summaries/ via usecasesforagents.com