How to Integrate Copy.ai with Your Headless CMS

What is Copy.ai?

Copy.ai is a go-to-market AI platform used by marketing, sales, and revenue teams to run repeatable AI workflows. Teams use it to generate and adapt content such as outbound emails, product descriptions, SEO briefs, competitive summaries, and campaign copy from structured inputs. Its workflow model is useful when you want the same AI process to run again and again with consistent variables, review steps, and outputs.

Why integrate Copy.ai with a headless CMS?

Copy.ai works best when it gets clean inputs: product names, audience segments, feature lists, URLs, tone rules, regions, and campaign dates. If those inputs live in a headless CMS as structured fields, you can send them directly into a Copy.ai workflow instead of asking a marketer to paste content from a page preview, spreadsheet, or ticket.,The disconnected version gets messy fast. A product marketer publishes a new product page, then copies the description into Copy.ai, waits for campaign variants, pastes approved copy back into an editor, and asks a developer to update another channel. That works for 5 pages. It breaks at 500 product pages, 12 locales, and 4 campaign teams.,With Sanity, content in the Content Lake is typed JSON, so Copy.ai can receive exactly the fields a workflow needs. GROQ selects those fields, webhooks trigger on publish events, and Functions can run the server-side call to Copy.ai without a separate worker or scheduled batch job. You still need to design the workflow and review process carefully, but the data handoff becomes repeatable instead of manual.

Architecture overview

A typical flow starts when an editor publishes a document in Sanity Studio, such as a product, landing page, campaign brief, or knowledge base article. A Sanity webhook fires on the publish mutation and sends the document ID to your webhook handler, or a Sanity Function runs directly on the content event. The handler uses @sanity/client and a GROQ query to fetch only the fields Copy.ai needs, including joined references such as product category, target audience, region, and brand voice rules. Your server then calls the Copy.ai Workflow API with those values as workflow start variables. Copy.ai runs the configured workflow, for example generating ad variants, sales email drafts, or SEO metadata. The output can be sent back to Sanity as draft fields for editorial review, pushed to a task system, or delivered to the end user through your website, app, email tool, or sales workflow.

Common use cases

Step-by-step integration

1. 1

   Set up Copy.ai access

   Create or use a Copy.ai workspace, create a workflow with named start variables, such as productName, audience, sourceUrl, and valueProps, then create an API key from your Copy.ai workspace settings. Copy the workflow ID from the API or workflow details screen.

2. 2

   Model the source content in Sanity Studio

   Define schema fields that map cleanly to Copy.ai variables. For a product launch workflow, use fields such as title, slug, shortDescription, valueProps, audience, category reference, sourceUrl, and launchDate. Keep long rich text and short prompt inputs separate.

3. 3

   Create the trigger

   Use a Sanity webhook for published documents, or use a Sanity Function if you want the sync logic to run inside Sanity's event system. Filter the trigger by document type and publish transition so drafts don't start Copy.ai runs by accident.

4. 4

   Fetch the exact fields with GROQ

   In your handler, use @sanity/client to fetch the document by ID. Use GROQ projections to include references Copy.ai needs, such as category title, audience name, and canonical URL, instead of sending the full document.

5. 5

   Call the Copy.ai Workflow API

   Send the GROQ result as workflow start variables to Copy.ai's workflow run endpoint. Keep this call on the server so your Copy.ai API key never ships to the browser.

6. 6

   Test the editorial loop

   Publish one test document, confirm the Copy.ai run starts, review the generated output, and decide where it should go next. Common choices are draft fields in Sanity, a Slack review message, a task, or a downstream campaign tool.

How Sanity + Copy.ai works

CMS approaches to Copy.ai

Keep building

Explore related integrations to complete your content stack.