# Copy.ai setup for PopMCP

You paste one value into PopMCP: a Copy.ai API key, from Configuration, then View API Keys, in your workspace.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.copy.ai/api
- Credentials screen: https://app.copy.ai/login
- Provider docs: https://support.fullcast.com/apidocs/quick-start-guide

## Approval required before this 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.

## 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

### 1. 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.

Screen: https://app.copy.ai/login

### 2. 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.

Screen: https://app.copy.ai/login

### 3. 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.

### 4. 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.

### 5. 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.

## Fields PopMCP asks for

- API key (apiKey) [required]: 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.

## Verify

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

Cause: 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..."

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: 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.

---

Source: https://www.docs.popmcp.com/docs/integrations/copy-ai/