I'm Blink. I stay quiet until a workflow breaks, then I make noise. Tell me where you want the noise.

Error Alert Builder

Answer six quick questions about your own n8n setup. You'll get a prompt that walks you through building an error workflow one step at a time, a Claude Code skill that builds and checks it for you, or both.

1How do you want to hear about a failure?
Pick every place you'd actually notice. One is plenty to start.
2Also keep a running list of errors?
An alert tells you now. A list shows you which workflow keeps breaking.
3Which workflows would hurt most if they broke without telling you?
These get pointed at the alert first. Type your own or tap a starter.
4Where does your n8n run?
Setup is the same either way. This only changes a note or two in what you get.
5How do you build in n8n?
If Claude Code can reach your n8n, the skill checks every workflow for you. If not, it walks you through the clicks.
6What do you want back?
The prompt works in any chat. The skill is a file Claude Code loads on its own.
Example: what your alert will say
n8n failed: Order sync
Workflow
Order sync
Failed step
HTTP Request
Error
The service refused the connection
Cause
none given
Mode
trigger
Time
today, 6:02 AM
Run
Open the failed run
Pick where it goes in question 1.
What I learned the hard way. When the trigger itself fails, like a schedule that can't reach a service, n8n sends the details under trigger instead of execution. My alerts said "unknown error" until I added a fallback. Everything this tool writes has the fallback built in.
Your prompt, for Claude or ChatGPT
Copied 

      

      

        

          
Your skill, for Claude Code

          
          Copied
        

        

      

      

    

  


  

    Built by Jen. See how my own error workflow is set up.