Workato · Arazzo Workflow

Workato Stop and Delete a Recipe

Version 1.0.0

Safely decommission a recipe by stopping it before deletion.

1 workflow 1 source API 1 provider
View Spec View on GitHub AgenticAPI ManagementAutomationB2BEmbedded iPaaSEnterpriseIntegrationiPaaSOrchestrationWorkflowsArazzoWorkflows

Provider

workato

Workflows

stop-and-delete-recipe
Stop a running recipe if needed, then permanently delete it.
Reads a recipe, stops it only when it is currently running, verifies it has stopped, and deletes it from the workspace.
4 steps inputs: recipeId outputs: deleted, recipeName
1
getRecipe
Read the recipe to confirm it exists and determine whether it is currently running before deletion.
2
stopRecipe
Deactivate the recipe so it no longer processes trigger events.
3
confirmStopped
Re-read the recipe and confirm the running flag is now false.
4
deleteRecipe
Permanently delete the stopped recipe from the workspace.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Workato Stop and Delete a Recipe
  summary: Safely decommission a recipe by stopping it before deletion.
  description: >-
    The Workato API requires a recipe to be stopped before it can be deleted.
    This workflow reads the recipe, branches on its running state to stop it
    only when needed, confirms it is no longer running, and then permanently
    deletes it. Every step spells out its request inline so the flow can be
    read and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: recipesApi
  url: ../openapi/workato-recipes-api-openapi.yml
  type: openapi
workflows:
- workflowId: stop-and-delete-recipe
  summary: Stop a running recipe if needed, then permanently delete it.
  description: >-
    Reads a recipe, stops it only when it is currently running, verifies it has
    stopped, and deletes it from the workspace.
  inputs:
    type: object
    required:
    - recipeId
    properties:
      recipeId:
        type: integer
        description: The unique identifier of the recipe to decommission.
  steps:
  - stepId: getRecipe
    description: >-
      Read the recipe to confirm it exists and determine whether it is
      currently running before deletion.
    operationId: getRecipe
    parameters:
    - name: id
      in: path
      value: $inputs.recipeId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      recipeName: $response.body#/name
      running: $response.body#/running
    onSuccess:
    - name: stopFirst
      type: goto
      stepId: stopRecipe
      criteria:
      - context: $response.body
        condition: $.running == true
        type: jsonpath
    - name: alreadyStopped
      type: goto
      stepId: deleteRecipe
      criteria:
      - context: $response.body
        condition: $.running == false
        type: jsonpath
  - stepId: stopRecipe
    description: Deactivate the recipe so it no longer processes trigger events.
    operationId: stopRecipe
    parameters:
    - name: id
      in: path
      value: $inputs.recipeId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      stopped: $response.body#/success
  - stepId: confirmStopped
    description: Re-read the recipe and confirm the running flag is now false.
    operationId: getRecipe
    parameters:
    - name: id
      in: path
      value: $inputs.recipeId
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.running == false
      type: jsonpath
    outputs:
      running: $response.body#/running
  - stepId: deleteRecipe
    description: Permanently delete the stopped recipe from the workspace.
    operationId: deleteRecipe
    parameters:
    - name: id
      in: path
      value: $inputs.recipeId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      deleted: $response.body#/success
  outputs:
    recipeName: $steps.getRecipe.outputs.recipeName
    deleted: $steps.deleteRecipe.outputs.deleted

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/workato-stop-and-delete-recipe-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.