Woo Revenue Incident Graph

What is Woo Revenue Incident Graph?

Diagnose why a connected WooCommerce checkout or payment path changed by joining privacy-safe store signals with public release and issue evidence.

This Actor exposes a small, allowlisted set of read-only MCP tools through a normal Apify input form and API. It is intended for woocommerce store owners, agencies, and incident responders investigating checkout and revenue failures. The Actor sends only the selected tool name and the JSON arguments you provide to the public UtilityHouse MCP endpoint, then writes one structured result to the run's default dataset.

What can it do?

Operation	Purpose
get_checkout_health_snapshot	Check checkout health first
diagnose_revenue_incident	Diagnose a revenue incident
check_checkout_change_risk	Check checkout-change risk
verify_revenue_recovery	Verify that a fix held

The Actor uses limited Apify permissions. It cannot alter the upstream product, your website, an order, a payment, a grant application, or a WordPress installation. An upstream HTTP error, MCP error, invalid response, or tool-level error fails closed and produces no successful-result event.

How to use it

1. Choose an operation from the Operation field.
2. Paste the matching MCP arguments into Tool arguments as a JSON object.
3. Run the Actor and open Results in the default dataset.
4. Treat cited evidence and explicit unknowns as part of the answer; do not remove caveats when passing the result to another system.

Quick-start input:

{
  "tool": "check_checkout_change_risk",
  "arguments": {
    "component": "plugin:woocommerce-gateway-stripe",
    "to_version": "9.0.0"
  }
}

The same input can be used from Apify Console, the Apify API, schedules, webhooks, and supported integrations. Product details and current limitations are available at https://revenue-graph.utilityhouse.xyz/.

Output

Every successful run writes exactly one dataset item:

{
  "product": "woo-revenue-incident-graph",
  "tool": "check_checkout_change_risk",
  "eventCharged": false,
  "result": { "...": "The structured MCP result" }
}

The shape inside result follows the selected MCP tool. The Actor does not invent a success record when the upstream service refuses, abstains at protocol level, times out, or returns malformed data.

Pricing and successful-result events

This public free beta does not charge a successful_tool_result event. Billing is disabled in the release configuration and also fails closed in code. A future paid release would require both an owner-controlled billing switch and an explicit structuredContent.billable: true result; a missing or false marker, an abstention, and every failed call emit no successful-result event. The dataset's eventCharged field records the actual decision. Apify platform compute and storage usage may still apply according to the user's plan.

Privacy and limitations

• Store-specific health, diagnosis, and recovery require a connected store.

• Real-store diagnostic accuracy remains unmeasured.

• An unknown or abstained answer is intentional when evidence is stale or too thin.

• Do not send customer details, order identifiers, payment data, credentials, or other personal information in the arguments object.

• Results are stored in the caller's Apify dataset and follow that account's retention settings.

• This is decision support, not legal, security, financial, or award advice.

Support

Start with the product documentation at https://revenue-graph.utilityhouse.xyz/. Include the Actor name, selected operation, and a privacy-safe error code when reporting a problem. Never include API keys, customer data, wallet details, payment identifiers, or raw store records.