Copy.ai
Connect Copy.ai to run your GTM workflows and get their output, review past runs and the credits they used, and manage webhooks.
You paste one value into PopMCP: a Copy.ai API key, from Configuration, then View API Keys, in your workspace.
Paid plan required before this connector works
No one reviews you, but Copy.ai's pricing page lists API access on its Enterprise plan and on no other.
- Typical wait
- None if your workspace already has API access. Otherwise it depends on Copy.ai's sales team, because Enterprise starts with a demo.
- Cost
- Copy.ai quotes Enterprise individually, from copy.ai/prices. Every workflow run also spends workflow credits from your plan. PopMCP adds nothing to this.
- Blocked until approved
- Everything, if your workspace has no API access: without a working key there is nothing to connect.
- Works meanwhile
- Read Copy.ai's API guide, and connect your other tools in PopMCP. There is no sandbox.
Where to apply: Check whether your workspace shows Configuration, then View API Keys. If it does not, ask your Copy.ai contact about API access, or request a demo at copy.ai/prices. Copy.ai is now part of Fullcast, and its support address is on fullcast.com.
- Copy.ai does not say what a key does on a plan without API access, so PopMCP can only report what Copy.ai answers.
- Running a workflow counts as a write in PopMCP, so a new read-only connection cannot run one until an owner or admin allows write actions.
- A key can be set to expire after 12 months. When it does, make a new one and reconnect.
- Setup time
- 2 min
- Auth
- API credentials
- API base URL
- https://api.copy.ai/api
- Rate limits
- Copy.ai does not publish a rate limit for this API. Runs are asynchronous: starting one returns an id, and the output follows when the status reaches COMPLETE. The run tools check every few seconds, and each call stops after a fixed number of requests.
Before you begin
- A Copy.ai workspace with API access. Copy.ai's pricing page lists API access on its Enterprise plan
- At least one workflow built in Copy.ai, because the API runs workflows and cannot create them
- The id of each workflow you want to run: open the workflow, then its API tab. The API cannot list workflows, so your AI will ask you for it
- Enough workflow credits for what you plan to run. Each run spends credits, and the amount depends on the workflow's steps
Get your credentials
Sign in to Copy.ai and open Configuration
Sign in at app.copy.ai and click Configuration in the left sidebar. A key reaches one workspace, so if you have more than one, open the right one first. You can connect another later with its own key.
Open API Keys and click Create
Click View API Keys, then Create at the top right of the page. If you do not see API Keys, your workspace may not have API access: ask your Copy.ai contact.
API Keys
Keys that let other tools run this workspace's workflows.
This view is a simplified sketch: the labels on your page may differ slightly. Expiry Date offers Never or 12 Months. A key made to expire stops working after that, and you would then make a new one.
Copy the key straight away
Name the key something you will recognise, like PopMCP, choose a user and an expiry, then click Create. Copy the key now and keep it somewhere safe: Copy.ai does not show it again.
Paste the key into PopMCP
In PopMCP, paste the key into API key and connect. PopMCP checks it by reading the workspace's webhooks, which spends no credits. New connections start read-only, so your AI can read runs and webhooks but cannot run a workflow or spend credits until an owner or admin allows write actions.
Give your AI a workflow id
Copy.ai's API cannot list workflows, so tell your AI which one to use. Open the workflow in Copy.ai, click its API tab, and copy the link in API ENDPOINT. The id is the part at the end, starting with letters like WCFG-. Pasting the whole link works too.
Connect in PopMCP
Open your workspace, choose Copy.ai in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | In Copy.ai click Configuration, then View API Keys, then Create. The key is shown only once. Stored encrypted and used only on our servers.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Copy.ai immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP marks the Copy.ai connection Verified and labels it Copy.ai workspace, since Copy.ai's API does not report a workspace name. Giving the AI a workflow id and asking for the inputs its earlier runs used returns those names, and a wrong id comes back as not found.
Troubleshooting
"Copy.ai did not accept this API key..."
Why: The key was copied incompletely, has expired or was deleted. Copy.ai shows a key only once, so it cannot be copied again.
Fix: In Copy.ai click **Configuration**, then **View API Keys**, make a new key and paste it into PopMCP.
"That is a workflow or run id..."
Why: A workflow id or run id was pasted in place of the key. These start with letters like WCFG- or WRUN-.
Fix: Paste the key from **View API Keys**. Give workflow ids to your AI in the chat instead.
There is no API Keys option under Configuration
Why: Copy.ai's pricing page lists API access on its Enterprise plan, so the workspace may not have it.
Fix: Ask your Copy.ai contact about API access for the workspace.
The AI says a workflow was not found
Why: The id is mistyped or belongs to another workspace. A key only reaches its own workspace.
Fix: Copy the id again from the workflow's **API** tab, or connect that workspace with its own key.
The AI says the credit limit has been reached
Why: Copy.ai answered WORKFLOW_CREDIT_LIMIT_REACHED, so no run was started.
Fix: Add credits in Copy.ai or wait for your plan's credits to renew. Trying again will not help until then.
The output looks wrong or empty
Why: An input name may not match the workflow. Copy.ai's API does not describe a workflow's inputs, so PopMCP can only compare them with earlier runs.
Fix: Look at input_check in the AI's result, and at the workflow's inputs in Copy.ai, then run it with the right names. Another run spends credits, so check first.
A run says done is false
Why: The workflow is still running. Runs can outlast the wait of up to 45 seconds.
Fix: Ask the AI to keep waiting, which uses wait_for_workflow_run and spends nothing. Do not start the workflow again, because that would spend credits twice.