Copy.ai Workflows API
★ Only Publicly Available OpenAPI DocumentAI/MLLanguage ModelsapiKey7 EndpointsREST
For Agents
Trigger pre-built Copy.ai workflows from an agent and stream completion via webhook to inject generated marketing copy into downstream systems.
Use for: Trigger a Copy.ai workflow that generates a product description, Get the output of a Copy.ai workflow run by run ID, List the last ten runs of my marketing-email workflow, Register a webhook so I'm notified when a workflow finishes
Not supported: Does not handle prompt design, model selection, or content publishing — use for triggering and retrieving Copy.ai workflow runs only.
Jentic publishes the only available OpenAPI specification for Copy.ai Workflows API, keeping it validated and agent-ready. The Copy.ai Workflows API lets external systems trigger pre-built Copy.ai workflows by ID, retrieve the run output, and subscribe to webhooks when runs complete. The seven endpoints cover starting a workflow run, listing recent runs, fetching a specific run, and full webhook lifecycle management. Authentication is via an API key passed in a custom header, and workflow inputs and outputs are passed as JSON payloads matching whatever variables the underlying Copy.ai workflow expects.
Install Jentic One Beta
Connect the Copy.ai Workflows API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Copy.ai Workflows API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Copy.ai Workflows API.
Start a Copy.ai workflow run with input variables defined by the workflow
Fetch the result of a specific workflow run including the generated output
List the recent run history for a workflow to inspect failures or throughput
Register a webhook to be notified when a workflow run completes
List or remove existing webhook subscriptions on the account
Use Cases
Patterns agents use Copy.ai Workflows API for, with concrete tasks.
★ Bulk Product Description Generation
E-commerce teams with a Copy.ai workflow that turns product attributes into a description can trigger one workflow run per product from their catalogue ingestion pipeline. POST /workflow/{workflow_id}/run starts each run, and a webhook fires on completion so the catalogue can be updated without polling. The API supports any input shape the workflow defines.
POST /workflow/{workflow_id}/run with the product SKU, attributes and target tone, then store the returned run_id for the catalogue update.
Sales Email Drafting From CRM Triggers
Sales operations can wire CRM stage changes to Copy.ai workflows that draft outreach emails referencing the deal context. The webhook payload returns the generated copy, which a downstream automation can attach as a draft activity in the CRM for the rep to review and send.
Trigger the 'sales-email-draft' workflow with the deal name, prospect role and company size; on webhook completion attach the output to the CRM record.
Content Operations Dashboard
Content teams running multiple Copy.ai workflows for different channels can build a dashboard listing recent runs and their outputs by calling GET /workflow/{workflow_id}/run for each tracked workflow. This surfaces failed runs and throughput without logging into the Copy.ai UI.
GET /workflow/{workflow_id}/run for each of the team's three production workflows and summarise success rate over the last 50 runs.
Agent-Driven Copy Generation
An AI agent that needs branded marketing copy can call Copy.ai workflows through Jentic instead of generating from scratch, ensuring outputs match the workflow's pre-tuned voice, prompts and guardrails. Jentic handles the API key and the agent simply provides workflow inputs and consumes the run result.
Use Jentic to start a Copy.ai workflow run for a launch announcement and poll GET /workflow/{workflow_id}/run/{run_id} until status is complete.
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for copy.
METHOD
PATH
DESCRIPTION
POST
/workflow/{workflow_id}/run
Start a workflow run
GET
/workflow/{workflow_id}/run
List runs for a workflow
GET
/workflow/{workflow_id}/run/{run_id}
Get a specific workflow run
POST
/webhook
Register a webhook
GET
/webhook
List webhooks
GET
/webhook/{webhook_id}
Get a specific webhook
DELETE
/webhook/{webhook_id}
Remove a webhook
POST
/workflow/{workflow_id}/run
Start a workflow run
GET
/workflow/{workflow_id}/run
List runs for a workflow
GET
/workflow/{workflow_id}/run/{run_id}
Get a specific workflow run
POST
/webhook
Register a webhook
GET
/webhook
List webhooks
GET
/webhook/{webhook_id}
Get a specific webhook
DELETE
/webhook/{webhook_id}
Remove a webhook
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Copy.ai API key sits in the Jentic credential vault. Agents triggering workflow runs through Jentic never hold the key directly; Jentic injects it as the apiKeyHeader on every request to /workflow/{workflow_id}/run.
Intent-based discovery
Agents search Jentic with intents like 'trigger Copy.ai workflow' or 'fetch Copy.ai run result' and Jentic returns the matching workflow or webhook operation, with the run input schema so the agent supplies the right variables.
Time to first call
Direct integration: half a day to wire up workflow triggers, run polling and webhook receivers. Through Jentic: 15-30 minutes from signup to a first triggered run.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Copy.ai Workflows API through Jentic.
Why is there no official OpenAPI spec for Copy.ai Workflows API?
Copy.ai does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Copy.ai Workflows API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Copy.ai Workflows API use?
The API uses an API key passed as a custom header (apiKeyHeader scheme in the spec). Through Jentic the API key is held in the credential vault and attached to the request at execution time, so the raw key never enters agent context.
Can I trigger a Copy.ai workflow run from an external system?
Yes. POST /workflow/{workflow_id}/run starts the run with whatever JSON inputs the workflow expects, and returns a run ID. Either poll GET /workflow/{workflow_id}/run/{run_id} or register a webhook on POST /webhook to be notified when the run finishes.
How does the Copy.ai webhook flow work?
Register the webhook URL with POST /webhook and Copy.ai will POST the run output to that URL when each run completes. List existing subscriptions with GET /webhook and remove stale ones with DELETE /webhook/{webhook_id} to keep only the receivers you trust.
What rate limits apply to the Copy.ai Workflows API?
The OpenAPI spec does not declare formal rate limits. Treat workflow runs as quota-consuming and respect plan limits documented in the Copy.ai dashboard, with retry-with-backoff on HTTP 429.
How do I run a Copy.ai workflow through Jentic?
Run pip install jentic, search Jentic with 'trigger Copy.ai workflow', load the operation schema for POST /workflow/{workflow_id}/run and execute it with the workflow ID and the input payload that the workflow expects.
GET STARTED