Workflows

list_workflows

List the team's workflows, with an optional status filter (Active, Inactive or archived) and name search. Use it to see existing workflows or to check for duplicate names before creating one.

Parameters

Name	Type	Required	Default	Description
`status`	`string`	No	—	Restricts results to workflows in one state: "active", "inactive" or "archived". Omit to return every workflow for the user's current team. Use "active" when the user asks what automations are able to run — Active means allowed to run, not running; whether one runs on its own also depends on its schedule (see get_workflow).
`search`	`string`	No	—	Case-insensitive substring match against the workflow name only — it does not look at descriptions, steps or tags. Use it before creating a workflow to check the team does not already have one with a similar name.
`page`	`integer`	No	—	1-based page number through the list, which is ordered newest first. Defaults to 1; only needed when the team has more workflows than a single page holds.
`per_page`	`integer`	No	—	How many workflows to return per page. Defaults to 20 when omitted or when the value is not a positive number.

Input Schema

{
  "type": "object",
  "properties": {
    "page": {
      "type": "integer",
      "description": "1-based page number through the list, which is ordered newest first. Defaults to 1; only needed when the team has more workflows than a single page holds."
    },
    "search": {
      "type": "string",
      "description": "Case-insensitive substring match against the workflow name only — it does not look at descriptions, steps or tags. Use it before creating a workflow to check the team does not already have one with a similar name."
    },
    "status": {
      "type": "string",
      "description": "Restricts results to workflows in one state: \"active\", \"inactive\" or \"archived\". Omit to return every workflow for the user's current team. Use \"active\" when the user asks what automations are able to run — Active means allowed to run, not running; whether one runs on its own also depends on its schedule (see get_workflow)."
    },
    "per_page": {
      "type": "integer",
      "description": "How many workflows to return per page. Defaults to 20 when omitted or when the value is not a positive number."
    }
  }
}

Output Schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string",
            "format": "uuid"
          },
          "name": {
            "type": "string"
          },
          "status": {
            "type": "string"
          },
          "link_url": {
            "type": "string",
            "format": "uri",
            "description": "Direct URL to view this workflow in Marcora."
          }
        }
      }
    },
    "curPage": {
      "type": "integer"
    },
    "nextPage": {
      "type": [
        "integer",
        "null"
      ]
    },
    "prevPage": {
      "type": [
        "integer",
        "null"
      ]
    },
    "itemsTotal": {
      "type": "integer"
    }
  }
}

Instructions

List workflows for the user's current team. Supports optional status filter and substring search.

Input roles:

status: "active" | "inactive" | "archived". Omit to return all.
search: substring to match against workflow name.
page / per_page: pagination. Default page=1, per_page=20, max per_page=100.

Usage patterns:

Before create_workflow: call list_workflows with search: to check for duplicate-name workflows.
When the user asks "what workflows do I have": call with no filters.
When the user asks "what's my automation doing?": filter by status="active" — but Active only means a workflow is allowed to run. Whether it runs on its own depends on its schedule (On or Paused), which the list does not show; call get_workflow and follow its run_state before saying any workflow is running. A workflow is Active/Inactive, a schedule is On/Paused — never mix the two.
Each item's id is a UUID string. Use it as workflow_id in get_workflow / update_workflow / run_workflow / get_workflow_runs.

Links: present link_url to the user exactly as returned — copy it character for character. Never retype, shorten, or rebuild a link or the IDs inside it.