← Integration guides

Connect Webflow to GeoCopy

Recommended: Connect with Webflow OAuth

In GeoCopy → Integrations → Webflow, click Connect with Webflow. You will authorize GeoCopy in Webflow, then choose your site and CMS collection. This is the same flow used for the Webflow App Marketplace.

Advanced: Manual API token

GeoCopy publishes to a Webflow CMS collection using the Webflow Data API. You need a Site API token (not your Webflow login password), plus your Site ID and Collection ID. See Webflow's site token docs.

Before you start

• You must be a site administrator to create API tokens.
• Your blog collection should use field slugs GeoCopy expects (see Collection fields below).

Steps

1. Open Site settings

1. In the Webflow Dashboard, find your site.
2. Click the ⋯ menu on the site card and choose Settings.

2. Go to API access

1. In the left sidebar, select Apps & integrations.
2. Scroll to the API access section.

3. Create the token and set permissions

1. Click Generate API token, name it (e.g. GeoCopy).
2. Set these token permissions (Webflow cannot add scopes later — regenerate if you change them):

   Permission	Level	Why GeoCopy needs it
   CMS	Read and write	Create and update blog items in your collection (required)
   Assets	Read and write	Upload featured images when publishing (required if articles have images)
   SitesView and manage site data and publishing	Read and write	Recommended for Live posts and connecting with a .webflow.io slug
   Sites(same row)	Read-only	OK if you paste the hex Site ID from Site settings → General and only use Draft in GeoCopy

   You do not need Ecommerce, Forms, Users, or Workspace tokens — only a Site API token on the site you publish to.

3. Click Generate token and copy the token immediately. You cannot view it again.

4. Copy your Site ID

In the same Site settings screen, open the General tab (default). Webflow shows your Site ID there. It is a 24-character hex string (e.g. 680e63e98c9a982ac9b8b741).

Do not use the slug from your public URL (angels-stupendous-site-739303.webflow.io). That subdomain is not the API Site ID. If you only have the slug, GeoCopy can try to resolve it when you connect, as long as your API token can list sites.

5. Find your Collection ID

1. Open CMS and select your blog collection (e.g. Blog Posts).
2. Open Collection settings. The Collection ID is in the URL or settings panel (another 24-character hex string).

6. Connect in GeoCopy

1. Go to Portal → Integrations → Webflow and click Connect.
2. Paste:
   • Site URL — your public site (e.g. https://www.example.com)
   • API Token — from step 3
   • Site ID — from step 4
   • Collection ID — from step 5
3. Click Connect. GeoCopy verifies access before saving.

Collection fields

GeoCopy writes to these CMS field slugs. If your collection uses different names (e.g. post-body instead of content), rename fields or create a collection for GeoCopy with the slugs below.

Revoke access

In Site settings → Apps & integrations → API access, revoke or delete the GeoCopy token.

Troubleshooting

• 403 when publishing (featured image) — Token is missing Assets → Read and write. Revoke the token and create a new one with CMS and Assets both set to Read and write.
• 403 when connecting or saving collection — Missing CMS → Read and write and/or raise Sites to Read and write. Regenerate the token with the full permission table above.
• Connection failed / 401 — Wrong token, revoked token, or typo when pasting.
• Publishing fails / 422 — Collection field slugs do not match the table in Collection fields.
• No API access section — You need site administrator permissions on that Webflow site.
• Draft works in Webflow but GeoCopy "Live" does not — Add Sites → Read and write on the token, or keep GeoCopy on Draft and publish manually in Webflow.

Also connecting WordPress? See Connect WordPress.