> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/mutations/deleteworkflow.md).

# Delete Workflow

deleteWorkflow Mutation

Deletes a Workflow definition from the system.

## Arguments

| Name | Type  | Description                                     |
| ---- | ----- | ----------------------------------------------- |
| `id` | `ID!` | The unique identifier of the workflow to delete |

## Return Type

`WorkflowDeletePayload!` - Contains information about the deleted workflow.

## Return Fields

`WorkflowDeletePayload`:

| Field       | Type | Description                    |
| ----------- | ---- | ------------------------------ |
| `deletedID` | `ID` | The ID of the deleted workflow |

## Usage Example

```graphql
mutation {
  deleteWorkflow(id: "workflow_123") {
    deletedID
  }
}
```

## JavaScript Example

```javascript
const DELETE_WORKFLOW = gql`
  mutation DeleteWorkflow($id: ID!) {
    deleteWorkflow(id: $id) {
      deletedID
    }
  }
`;

const { data } = await client.mutate({
  mutation: DELETE_WORKFLOW,
  variables: {
    id: "workflow_123"
  }
});

console.log(`Deleted workflow: ${data.deleteWorkflow.deletedID}`);
```

## Important Notes

* Deleting a workflow definition will prevent new instances from being started
* Existing running workflow instances may continue to execute until completion
* This operation permanently removes the workflow definition and cannot be undone
* Ensure proper authorization before performing this operation
* Consider deactivating the workflow first to stop new instances before deletion
* Associated workflow signals will be disassociated but not deleted
* Review dependencies on this workflow before deletion to avoid breaking other processes


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/mutations/deleteworkflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.