Overview
The "Copy AI" node for n8n allows you to programmatically start a workflow run on the Copy AI platform. The "Workflow Run" resource with the "Start" operation is used to trigger a new execution of a specified workflow, optionally passing in start variables and metadata. This is useful for automating content generation or other processes managed by Copy AI workflows directly from your n8n automation.
Common scenarios:
- Automatically triggering a Copy AI workflow when an event occurs in another system.
- Passing dynamic input data (start variables) to a Copy AI workflow from previous n8n nodes.
- Storing and retrieving custom metadata alongside workflow runs for tracking or auditing purposes.
Practical example:
You could use this node to start a Copy AI workflow that generates marketing copy whenever a new product is added to your e-commerce database, passing product details as start variables.
Properties
| Name | Meaning |
|---|---|
| Workflow ID | ID of the workflow to be started. Required. |
| Start Variables | A JSON object containing all start variables for your workflow. Required. Example: {"inputText": "Generate a blog post about AI."} |
| Additional Fields | Collection of optional fields: • Metadata: A JSON object containing metadata to store and return with the workflow run. Optional. |
Output
The output is a JSON object representing the newly started workflow run. The structure typically includes:
{
"id": "string", // Unique identifier of the workflow run
"workflowId": "string", // ID of the workflow that was started
"status": "string", // Status of the workflow run (e.g., "running", "completed")
"createdAt": "string", // Timestamp of when the run was created
"metadata": { ... }, // Any metadata provided at start
"startVariables": { ... }, // The start variables passed in
// ...other fields returned by the Copy AI API
}
If binary data is ever returned (not typical for this operation), it would represent file outputs or attachments generated by the workflow.
Dependencies
- External Service: Requires access to the Copy AI API.
- API Key: You must configure Copy AI API credentials in n8n under the name
copyAiApi. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid Workflow ID: If the provided Workflow ID does not exist, the node will throw an error indicating the workflow cannot be found.
- Malformed Start Variables or Metadata: If the JSON provided in "Start Variables" or "Metadata" is invalid, the node will fail with a parsing error.
- Authentication Errors: If the API key is missing or incorrect, you may receive authentication/authorization errors from the Copy AI API.
Error messages and resolutions:
"Unexpected token ... in JSON": Check that your "Start Variables" and "Metadata" fields contain valid JSON."Workflow not found": Verify the Workflow ID is correct and exists in your Copy AI account."401 Unauthorized": Ensure your Copy AI API credentials are correctly configured in n8n.