Overview
The Copy AI Trigger node for n8n starts workflows in response to specific events from the Copy AI platform. It is designed as a trigger node, meaning it listens for incoming webhook events from Copy AI and initiates an n8n workflow when one of the selected events occurs.
Common scenarios:
- Automate follow-up actions when a Copy AI workflow starts, completes, or fails.
- Monitor your workspace's credit usage and trigger alerts or notifications when the credit limit is reached.
- Integrate Copy AI activity with other tools (e.g., send Slack messages, update databases) based on workflow events.
Practical examples:
- Send a notification to a team chat when a Copy AI workflow run fails.
- Log all completed Copy AI workflows into a spreadsheet.
- Alert administrators when the Copy AI workspace reaches its credit limit.
Properties
| Name | Meaning |
|---|---|
| Event Type | The event which will trigger the workflow. Options: - Workflow Started - Workflow Completed - Workflow Failed - Credit Limit Reached |
Output
The node outputs the JSON payload received from Copy AI via the webhook. The structure of this output depends on the event type sent by Copy AI, but generally, it will mirror the data sent in the webhook request body.
Example output:
{
// All fields as provided by Copy AI in the webhook event
}
- The output is always in JSON format.
- No binary data is produced by this node.
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. - Webhook URL: The node registers a webhook with Copy AI; your n8n instance must be accessible from the internet (not running on localhost unless using n8n's tunnel feature).
Troubleshooting
Webhook not working on localhost:
Error:The Webhook can not work on "localhost". Please, either setup n8n on a custom domain or start with "--tunnel"!
Solution: Use n8n's tunnel mode (n8n start --tunnel) or deploy n8n on a publicly accessible domain.Webhook creation failed:
Error:CopyAI webhook creation response did not contain the expected data.
Solution: Ensure your Copy AI API credentials are correct and that your n8n webhook URL is reachable by Copy AI.404 errors during webhook check/delete:
If the webhook was deleted manually or expired on Copy AI, the node will attempt to clean up its internal state automatically.