Contact and support
Support is deliberately layered: the fastest answers are the ones you do not have to wait for. Work down the list and most questions are answered before you reach us.
How to get help, in order
Contextual help where you are
Every finding in the dashboard explains the signal, the evidence behind it and what to check first. Start there — it is the answer written for that exact case.
The documentation
Connecting an instance, what each detection means, writing an Outcome Contract, and how alerts deduplicate are all covered in the docs.
The FAQ
The n8n monitoring guide and the pricing page answer the questions that come up most often, including the ones about plan limits and read-only access.
Automated diagnostics
When an integration is unhealthy, run the built-in connection check in the dashboard. It tests reachability, the API key and permissions, and usually names the problem outright.
Open a ticket by email
If none of the above settled it, email us with your workspace name, the workflow involved, what you expected and what you saw. Include the finding identifier if there is one.
OutcomeGuard is operated by ProofWorks. Support is handled by email at support at our domain. The address is published here as text once the domain is live; we would rather leave this blank than print an address that does not work.
support at our domain
Write from the address on the account so we can find the right workspace. Never send us an API key or a password — we never need either to help you.
What to expect
- We answer support email on business days, oldest first, with security reports jumping the queue.
- Refund requests are answered within five business days.
- Incidents affecting the service are published on the status page while they are happening, not afterwards.