Page cover

List Available Workflows API

Description: Retrieves a list of available workflows.

Try it out: Swagger Reference

Request Syntax:

GET /workflows
Authentication: Bearer <Your API key>

Response Syntax:

[
  {
    "workflow_id": "",
    "user_id": "",
    "organization_id": "",
    "created_at": "",
    "created_by": "",
    "description": "",
    "file_metadata": {
        "bucket": "",
        "url": "",
        "key": ""
    },
    "graph": {
        "settings": {
            "support_multiple_edges": boolean
        },
        "input_data": {},
        "description": "",
        "nodes": { ... },
        "edges": [ ... ],
        "entry_point": "",
        "finish_point": "",
        "selectedOutput": "",
        "node_metadata": ""
    },
    "name": "",
    "status": "",
    "updated_at": "",
    "updated_by": "",
    "version": "",
    "public": boolean
    },
    { ...
    }
]
List Available Workflows Response Example

Each workflow returned in the API list will include the following information.

Response Syntax Variables

  • Workflow id: ID associated with the workflow

  • User id: ID of the user who created the workflow

  • Organization ID: ID of the organization where the workflow is stored

  • Created at: date-time the workflow was created

  • Created by: User id of the user who created the workflow

  • Description: Generated description of the workflow. This is what is passed to the routing model to determine when to call the workflow.

  • File Metadata: Information on where the file is stored

  • Graph: breakdown of the nodes and connections within the workflow

  • Name: name of the workflow

  • Status: status of the workflow

    • Can be active or inactive

  • Updated at: date-time for last time the workflow was updated

  • Updated by: the user ID of the last person to update the workflow

  • Version: Version of the workflow

  • Public: whether the the workflow is public or private. This determines who in the organization can see the workflow

Last updated