OutcomeOS

Frequently looked up

Q1How do you verify an outcome was actually achieved?

With events from the system where the result lives, not from the workflow itself. A lead outcome needs an inbound reply event. A payment outcome needs a signed payment-succeeded event for the same customer and invoice. Each metric links back to the event and source that verified it.

Q2What happens when an integration fails?

Safe steps retry automatically with exponential backoff. Steps marked as idempotent retry automatically. Sending a message or taking a payment is never blindly retried—it uses an idempotency key, and if the result is unknown the run goes to the attention queue with the reason. You can replay failed runs once the cause is fixed.

Q3Can I host OutcomeOS myself?

Yes. Self-hosting is available on request—tell the team about your setup and they will share the guide and access. The hosted plans are the managed service where they run, patch and maintain it. Self-hosted installs bring their own provider credentials.

Q4How is this different from Zapier, Make or n8n?

Those tools are great at running steps; OutcomeOS also tracks whether the business result happened. You define an outcome with success criteria, like “the lead replied”. Workflows send events toward it, and the outcome is only marked achieved when a verifying event arrives. Run status and outcome status are shown separately.

Q5What happens when I hit my plan limit?

Your data stays readable, but new executions stop until the next cycle or an upgrade. Dashboards, logs and outcomes keep working. Triggers that arrive over the limit are rejected with a clear error rather than silently dropped, so the sender can retry later.