Access and safety
- Does OutcomeGuard need write access?
- No. It reads the n8n public REST API and never writes. It does not create, edit, activate or deactivate workflows, and it does not read or change credentials.
- Can it break my workflows?
- It cannot change them. The only load it adds is read requests to the API, which are rate-limited and backed off when the instance pushes back.
- Where does my API key live?
- Encrypted at rest with AES-256-GCM, with keys held only in the runtime environment. Never in code, git or logs. A key used for a free scan is discarded when the scan ends.
- Do you store my data?
- Execution summaries only: status, timestamps, duration, item counts, last node, definition hash, redacted error text. Never execution payloads.
Coverage
- Does it work with n8n Cloud?
- Yes, and with self-hosted instances. Both expose the public REST API. A self-hosted instance needs to be reachable over HTTPS from the internet.
- What about Make, Zapier or GitHub Actions?
- On the roadmap, without dates. Version 1 is n8n only, on purpose.
- Does it monitor sub-workflows?
- A workflow called by another workflow is monitored like any other workflow, judged against its own history. Its trigger kind is “called” rather than a schedule, so cadence is learned from observation instead of from a cron expression.
Behaviour you might not expect
- Why does a workflow say insufficient data?
- It has not run enough times for a statistical judgement. Hard failures are still reported; the detections that need a baseline wait. This is reported openly rather than hidden behind a green tick.
- Why is a workflow UNKNOWN?
- The instance could not be reached. OutcomeGuard will not claim a workflow is healthy on the basis of no evidence, and it will not claim it is broken either.
- Why did I not get an alert for every failed run?
- Findings are deduplicated into incidents with a cooldown. One outage is one email, a second if it is still broken later, and one when it recovers.
- A workflow legitimately returns zero items. Will it be flagged?
- Not once the baseline shows that zero is normal for it. The empty-output detection only fires when zero contradicts the workflow's own history.
Account and billing
- Is the Free plan time-limited?
- No. Three monitored workflows, core detection, seven days of history and email alerts, with no card and no trial clock.
- Can I cancel any time?
- Yes. Cancelling stops the next charge and you keep access until the end of the paid period. A first payment on a plan is refundable within 14 days.
- How do I delete everything?
- Disconnect the integration to remove its credential and execution summaries, or delete the account to remove the workspace and its data.