Build and Manage Wix Automations

Use this guide to discover installed automation capabilities and inspect whether an automation is active. These are read-only workflows. Creation, configuration edits, activation and test execution are outside what this skill covers. Do not perform a write when the user asks only to inspect.

For a capability check, resolve the site's catalogs, retain the returned app/key identities, and inspect the selected schemas. A remembered action key is a search hint, not evidence that the action is installed. State missing prerequisites without offering an unverified substitute. If a requested action isn't found, report it exactly as the "Bounded fallback" section of Automations API Catalog says (scan evidence, "not found" vs "not installed", closest related actions). Resolve the trigger once and scan the action catalog once; answer from those results instead of repeating either call.

For current status, find the exact automation, Get its returned ID, and report the status from that response. Every status answer names the automation and its returned ID. Current ACTIVE/INACTIVE status is separate from historical run results.

Status questions need only Query and Get Automation: don't call the trigger or action catalogs for them. Query by the exact name with one bounded page before paging further.

Keep the requested site context fixed. Do not expose tokens or credentials. Tie every claim to the returned data, and distinguish a missing record from proof of nonexistence.