Skip to content

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

  1. 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.

  2. The documentation

    Connecting an instance, what each detection means, writing an Outcome Contract, and how alerts deduplicate are all covered in the docs.

  3. 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.

  4. 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.

  5. Send us a message

    If none of the above settled it, use the form below with your workspace name, the workflow involved, what you expected and what you saw. Include the finding identifier if there is one.

Send us a message

OutcomeGuard is operated by ProofWorks. Support is handled through this form rather than a published address, which keeps the inbox free of scraped spam. We reply by email to the address you enter.

If you have an account, enter the address on the account so we can find the right workspace. Never send an API key or a password — we never need either to help you.

What to expect

  • We answer messages 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.