# Webflow site tokens (/integrations/webflow-service-account)

Connect one Webflow site with a site API token. Choose its scopes in the site settings, then add the token to Sim.

## Prerequisites \[#prerequisites]

In Sim, you need workspace write access and permission to manage integrations.

Only **site administrators** can generate site tokens. Each site allows a maximum of **5 tokens** — if you're at the cap, revoke an unused one before creating a token for Sim.

## Setting up the site token \[#setting-up-the-site-token]

Open your site's **Site settings** and go to **Apps & integrations** → **API access**

Click **Generate API token** and give it a recognizable name (e.g. `sim-workflows`)

Select the scopes the token needs. The minimum set for Sim's Webflow blocks is:

```
Sites: Read-only
CMS: Read and write
```

The picker offers **no access**, **read-only**, or **read and write** per category. `Sites: Read-only` (`sites:read`) is required for Sim to verify the token when you connect it. `CMS: Read and write` (`cms:read` + `cms:write`) covers Sim's Webflow tools — listing, getting, creating, updating, and deleting CMS items. Add other scopes only if you need them

Copy the token when it's shown. Webflow only displays it once — if you close the dialog, you'll have to generate a new token.

Warning:

Site tokens expire after **365 consecutive days of inactivity**. An API call before expiry resets the clock, so a workflow that runs regularly resets the inactivity period — but a workflow that sits dormant for a year will start failing with authentication errors. If a workflow runs rarely, set a calendar reminder to run it (or any Webflow block) at least once a year, or check the credential periodically in Sim.

## Adding the site token to Sim \[#adding-the-site-token-to-sim]

Open **Integrations** from your workspace sidebar

Search for "Webflow" and open it, then click **Add to Sim** and choose **Add site token**

Paste the site API token and optionally set a display name and description

Click **Add site token**. Sim verifies the token by listing the sites it can access — if it fails, you'll see a specific error explaining what went wrong. A token created without the `sites:read` scope fails this check even if its CMS scopes are correct.

The token is encrypted before being stored, along with the site it grants access to.

## Using the credential in workflows \[#using-the-credential-in-workflows]

Add a Webflow block to your workflow. In the credential dropdown, select the saved Webflow site token. Choose the operation and configure its inputs.
The block calls Webflow's Data API (`api.webflow.com/v2/...`) using the token. It can only reach collections and items belonging to the token's site — pointing a block at a different site's collection fails with an access error.

## Verify access and rotate the token \[#verify-access-and-rotate-the-token]

Read an item from the token's site, then test any required CMS writes. A token cannot access another site's collections. Use separate site tokens for multiple sites, or use OAuth when appropriate.

Scopes are fixed when the token is created. If you need wider access, generate a replacement with the required scopes, update the saved credential in Sim, test the workflow, then revoke the old token. Keep the five-token limit in mind. A missing scope can produce an authorization error even when the token is valid.

See Webflow's [site-token guide](https://developers.webflow.com/data/reference/authentication/site-token) for scope selection, inactivity expiration, and revocation.