Skip to main content
Glama

delete_workflow

Remove a workflow from the Automatisch automation platform by specifying its ID to manage and organize your automated processes.

Instructions

Delete a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesWorkflow ID to delete

Implementation Reference

  • src/handlers.ts:91-104 (registration)
    Registration of the 'delete_workflow' tool in the list of tools, including its name, description, and input schema requiring a workflowId.
    {
      name: "delete_workflow",
      description: "Delete a workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "Workflow ID to delete"
          }
        },
        required: ["workflowId"]
      }
    },
  • MCP tool handler dispatch for 'delete_workflow': calls main.api.deleteWorkflow with workflowId argument and returns JSON response.
    case "delete_workflow":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.deleteWorkflow(args?.workflowId), null, 2)
          }
        ]
      };
  • Core API handler function for deleteWorkflow (currently a placeholder stub referencing logic from index.ts).
    deleteWorkflow: async function(workflowId: any) {
      // ... copy deleteWorkflow logic from index.ts ...
    },
  • apiHelpers factory function that provides the api object used by handlers, including deleteWorkflow method.
    export function apiHelpers(main: any) {
      return {
        apiRequest: async function(endpoint: any, options: any = {}) {
          // ... copy apiRequest logic from index.ts ...
        },
        listWorkflows: async function(args: any = {}) {
          // ... copy listWorkflows logic from index.ts ...
        },
        getWorkflow: async function(workflowId: any) {
          // ... copy getWorkflow logic from index.ts ...
        },
        createWorkflow: async function(data: any) {
          // ... copy createWorkflow logic from index.ts ...
        },
        updateWorkflow: async function(workflowId: any, data: any) {
          // ... copy updateWorkflow logic from index.ts ...
        },
        deleteWorkflow: async function(workflowId: any) {
          // ... copy deleteWorkflow logic from index.ts ...
        },
        listConnections: async function(args: any = {}) {
          // ... copy listConnections logic from index.ts ...
        },
        createConnection: async function(data: any) {
          // ... copy createConnection logic from index.ts ...
        },
        listExecutions: async function(args: any = {}) {
          // ... copy listExecutions logic from index.ts ...
        },
        getAvailableApps: async function(args: any = {}) {
          // ... copy getAvailableApps logic from index.ts ...
        },
        testWorkflow: async function(workflowId: any, testData: any = {}) {
          // ... copy testWorkflow logic from index.ts ...
        },
        getWorkflowsOverview: async function() {
          // ... copy getWorkflowsOverview logic from index.ts ...
        },
        getConnectionsOverview: async function() {
          // ... copy getConnectionsOverview logic from index.ts ...
        },
        getRecentExecutions: async function() {
          // ... copy getRecentExecutions logic from index.ts ...
        }
      };
  • Initialization of the 'api' property on the server instance using apiHelpers, making it available to handlers as main.api.
    public api = apiHelpers(this);

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/milisp/automatisch-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server