Copy AI

Actions3

Workflow Run Actions

Overview

The Copy AI node for n8n, specifically the "Workflow Run" resource with the "Get Many" operation, retrieves multiple workflow run records from the Copy AI platform. This is useful for monitoring, auditing, or analyzing the execution history of a specific workflow. For example, you might use this node to fetch all recent runs of a content generation workflow, review their statuses, or trigger follow-up actions based on their results.

Properties

Name	Meaning
Workflow ID	ID of the workflow whose runs you want to retrieve.
Return All	Whether to return all available workflow runs (`true`), or limit the number of results (`false`).
Limit	Maximum number of workflow runs to return (only shown if "Return All" is `false`).

Output

The output is an array of JSON objects, each representing a workflow run.
Each object contains data fields as returned by the Copy AI API for a workflow run. Typical fields may include run identifiers, status, timestamps, and any associated metadata.

Example output:

[
  {
    "id": "run_123",
    "status": "completed",
    "createdAt": "2024-06-01T12:00:00Z",
    "metadata": { /* ... */ }
    // ...other fields as provided by the API
  },
  {
    "id": "run_124",
    "status": "failed",
    "createdAt": "2024-06-02T09:30:00Z"
    // ...
  }
]

Dependencies

External Service: Requires access to the Copy AI API.
API Credentials: You must configure the copyAiApi credential in n8n with your Copy AI API key.

Troubleshooting

Invalid Workflow ID: If the provided Workflow ID does not exist or is incorrect, the node will throw an error indicating that the workflow could not be found.
API Key Issues: If the API key is missing or invalid, authentication errors will occur. Ensure your credentials are correctly set up in n8n.
Limit Exceeded: If you request more items than allowed by the API, the node will attempt to fetch all items if "Return All" is true, or slice the results if "Limit" is set.
JSON Parse Errors: Supplying malformed JSON in any advanced fields (not used in "Get Many") can cause parsing errors.