# Hourly alert creation and resolution in SIGNL4 based on file state
This automation manages alerts in SIGNL4 using an external JSON file as state storage. Designed for teams needing reliable, lightweight alert handling without database dependency.
## Who it´s for
- DevOps teams using SIGNL4 for incident management
- System administrators automating alert cycles
- Engineers requiring simple state persistence between runs
## What the automation does
- Runs hourly via cron schedule
- Reads binary JSON file with alert data
- Checks ´Done´ flag: if false, creates new alert in SIGNL4; if true, resolves existing one using external ID
- Updates event status and writes back to file
- Prevents duplicate alerts by tracking processed events
## What´s included
- Ready-to-use n8n workflow
- Trigger and handler logic
- Integrations with SIGNL4 and file system (via Binary File I/O)
- Basic setup and adaptation guide
## Requirements for setup
- n8n instance with file system access
- SIGNL4 account with API key
- Read/write access to the JSON alert data file
## Benefits and outcomes
- Eliminates manual alert entry in SIGNL4
- Reliable tracking of processed events without complex infrastructure
- Avoids notification duplicates
- Simple deployment using file-based state storage
- Works in standalone environments without persistent database
## Important: template only
Important: you are purchasing a ready-made automation workflow template only. Rollout into your infrastructure, connecting specific accounts and services, 1:1 setup help, custom adjustments for non-standard stacks and any consulting support are provided as a separate paid service at an individual rate. To discuss custom work or 1:1 help, contact via chat
No feedback yet