Skip to content
NEWError doctor and Watchtower: failed n8n runs explained in plain words, and emailed to you. See what is new

Product / Run and fix

Run and fix

Push it to n8n. Know when it breaks, and why.

The part after the build is where automations usually stall. trig8n connects the logins, publishes the workflow and watches it for you.

01

Push to n8n

Connect n8n Cloud or your own server once with an API key. Every workflow then goes in with one click, published.

  • Works with n8n Cloud and self-hosted n8n
  • Logins n8n does not know yet are kept as open slots
  • Published again when you link a login later

02

Set up logins

trig8n reads which logins each workflow needs, finds the ones already in your n8n and tells you where to get the rest, field by field.

  • Your passwords stay in your n8n. trig8n only remembers the name of each login.
Your passwords stay in your n8ntrig8n passes a login straight to your n8n and only remembers its name, so it can link it to a workflow. It never keeps the password or key.

03

Error doctor

Claude explains each failed run in plain words: what went wrong, why, and how to fix it. Where the workflow is the cause, you get a fixed copy.

  • Private values are masked before anything goes to Claude
  • The login of the failed step is never sent

04

Watchtower

Checks your n8n every hour and emails you when an automation fails, and when your n8n cannot be reached.

  • At most one email every 3 hours
  • One email if n8n is unreachable three checks in a row
Every hourChecks the newest failed runs.
Calm inboxAt most one email every 3 hours.
Down alertOne email if n8n is unreachable three times in a row.

More from Product

Start with a free account.

No card needed. Every tool can be tried a few times.

Start freeSee pricing