> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/mcp-and-ai-reference/use-cases-and-examples.md).

# Use cases and examples

Choose a supported execution walkthrough or a design recipe. The latter defines what to build and verify; it is not a claim that the full scenario has been executed in your environment.

## Existing-flow walkthroughs

* [Find and inspect an existing Hyperflow](https://docs.autommate.com/userguide/mcp-and-ai-reference/discovery-tool-contracts.md#worked-example-find-the-documented-request-intake-flow)
* [Inspect an action contract before mapping it](https://docs.autommate.com/userguide/mcp-and-ai-reference/inspection-tool-contracts.md#worked-example-inspect-the-string-assign-contract-before-mapping-it)
* [Run an existing API or webhook Hyperflow](https://docs.autommate.com/userguide/mcp-and-ai-reference/run-an-existing-autom-through-mcp.md)
* [Inspect an existing service execution record](https://docs.autommate.com/userguide/mcp-and-ai-reference/track-run-status-and-verify-results.md#worked-example-inspect-a-scheduled-service-execution)

## Design and acceptance recipes

* [Transfer a Jira issue to Xurrent](https://docs.autommate.com/userguide/mcp-and-ai-reference/use-cases-and-examples/jira-to-xurrent)
* [Design a reusable service for several tenants](https://docs.autommate.com/userguide/mcp-and-ai-reference/use-cases-and-examples/reusable-tenant-service)

Inspect the available integrations, permissions and authoring tools before implementing a recipe. Use controlled data and record the run and target-system evidence. A returned status alone is not the business result.

## Configurable employee offboarding

[Prepare an offboarding Service blueprint for multiple tenants](https://docs.autommate.com/userguide/mcp-and-ai-reference/use-cases-and-examples/configurable-employee-offboarding). Use native actions, trace inputs to Engage or verified outputs, check actual approval evidence and independently verify the result. The recipe includes a manual deployment handover and explicit acceptance tests; it is not a claim of an executed customer implementation.
