Copy.ai Workflows API

Name: Copy.ai Workflows API API
Brand: Copy.ai Workflows API
Availability: InStock

★ 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.

Quickstart

Get started with Copy.ai Workflows API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"trigger a Copy.ai workflow run"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Copy.ai Workflows API 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

GET STARTED

Start building with Copy.ai Workflows API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Copy.ai Workflows API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Copy.ai Workflows API 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

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

GET

/webhook

List webhooks

Why though 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.

Alternative

OpenAI API

General-purpose LLM API for direct prompt-based copy generation

Choose OpenAI when the agent needs raw model access without the workflow guardrails Copy.ai imposes.

Complementary

n8n API

Workflow automation tool that can orchestrate Copy.ai runs across multiple data sources

Pair n8n with Copy.ai when teams want a visual flow that triggers Copy.ai workflows from external events.

Complementary

Zapier API

Automation platform that can fan Copy.ai outputs into hundreds of downstream apps

Use Zapier when the generated copy needs to land in CRM, CMS or messaging tools that Zapier already connects to.

Complementary

HubSpot Marketing Emails API

Send the generated copy as marketing emails through HubSpot

Pick HubSpot when the workflow output is destined for an email campaign managed inside HubSpot.

FAQs

Specific to using Copy.ai Workflows API 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.