Setup 8 of 14
Create a Contentful CMA token and connect your space
If your site is built with Contentful, Get1pct can write the edits you choose with “Use this edit” to an entry’s title, description and heading fields, and then publish the entry. To connect, you create a CMA token (a personal access token). The token can do everything the user who created it can do, so create it while signed in as a user with limited access.
- Required?
- Optional (Contentful only)
- Where you do it
- Contentful Settings
Before you start
- You need a Contentful user who can edit and publish entries in the space. The next section explains how to set one up.
- Connecting is optional. Without it, you copy the wording of each edit and paste it into Contentful yourself.
- Get1pct stores the token encrypted and uses it only to apply and undo the edits you choose. It deletes the token when you disconnect or cancel.
- Each site can have one connection. If WordPress is connected to the same site, connecting Contentful replaces it.
- The Contentful screenshots were taken in a test space in November 2026, with the end of the token hidden. They show only how to create and authorize the token. The other steps follow Contentful’s official documentation.
Limiting access
You can’t set permissions on a CMA token itself. The token has exactly the access of the user who created it, in every space that user belongs to. So set up the user first:
- Set up a user just for Get1pct and invite it to only the space you connect.
- Give it the Editor role, which can edit and publish entries. The Author role can’t publish, so edits would fail. The Admin role isn’t needed.
- If your plan has custom roles, you can narrow the access further: reading, editing and publishing entries of the content types you connect.
Get1pct only reads locales, content types and entries, changes the fields you list (with PATCH) and publishes that entry. It never deletes or archives entries, and never changes your content model.
To learn how to store the token and what to do if it may have leaked, see Keep API keys and CMS tokens safe.
Steps
Step 1Create a CMA token
- Log in to Contentful as the user described above and open the space.
- In the top menu, open Settings → CMA tokens and click Create personal access token.
- Enter a name such as get1pct, choose an expiration date and click Generate.
- Copy the token. Contentful shows it only on this screen.
- Click Done. If the token’s row in the list shows Authorize access, click it, then click Authorize next to your organization. If your organization manages token access, the token doesn’t work until you do this, and Get1pct says “We could not connect.”

- Enter a name you will recognize, such as get1pct, in “Token name”.
- Choose when the token should stop working in “Expiration date”. When it expires, create a new token and connect again.
- Click “Generate”. The token is shown only on this screen, so copy it right away.

- You create tokens with “Create personal access token” at the top right (it opens the screen in the previous screenshot).
- If the row of your new token shows “Authorize access”, click it. If it doesn’t, you can skip this.
- In the panel on the right, click “Authorize” next to your organization. The token doesn’t work until you do this (connecting says “We couldn’t connect”).
When the token expires, edits fail to apply. Create a new token and connect again.
Step 2Note the space ID, environment and locale
- Space ID: shown under Settings → General settings, which only space admins can open. If you’re signed in as an Editor, take it from your browser’s address bar instead. It’s the part right after
/spaces/(app.contentful.com/spaces/xxxx/…). - Environment ID: shown under Settings → Environments. It’s usually
master. - Locale: the code of the language to change, such as en-US, shown under Settings → Locales. A field that isn’t localized keeps its value only in the default locale, so for that field Get1pct changes the default locale’s value.
- Data region: choose EU if you sign in at app.eu.contentful.com. Otherwise, keep the default (US).
Step 3Note the content type ID and field IDs
- Content type ID: open the content type in Content model. The ID is shown near its name (for example, blogPost).
- Field IDs: the Field ID in each field’s settings (for example, title or seoDescription). Get1pct can change Short text and Long text fields.
- Field to match {slug}: the ID of the field your page URLs are made from, such as slug. It must be a Short text field. If you leave it blank, Get1pct treats that part of the URL as the entry ID.
Step 4Enter them in the dashboard and click Connect
Open Connections in your dashboard. Under “How your site is updated”, choose “Shopify, Webflow, Contentful, microCMS or another service”. The dashboard in the screenshot is in Japanese, so each step below it gives the English label in brackets.

- Choose “Contentful” in “お使いの CMS” (Your CMS).
- Enter “スペース ID” (Space ID) and “環境 ID” (Environment ID, usually master).
- Enter “ロケール” (Locale), such as en-US. If you use the EU data center, set “データの保管場所” (Data region) to EU.
- Paste the token into “CMA トークン” (CMA token).
- Enter the page path pattern, such as /blog/{slug}, in “ページのパス” (Page path), and the content type ID in “コンテンツタイプ ID” (Content type ID).
- Enter the ID of the field that matches {slug}, such as slug. If left blank, we look up the entry ID.
- Enter the IDs of the fields we may change (the heading field below works the same way).
For a page that comes from one fixed entry, such as the home page, leave {slug} out of the path and enter the entry ID instead. Then click “Connect” at the bottom. Get1pct checks that the locale, content types and fields exist before it connects.
How this connection behaves
Get1pct follows these rules every time it applies an edit through this connection.
- We only change the title tag, meta description and heading (h1), and only in the fields you listed when connecting. We never change body text.
- We change a field only when its current value is exactly the same as the edit’s “before” text (the text on the live page). If it differs at all, it’s a different entry or your site adds words (such as “| Site name”), so we leave it for you to copy.
- We don’t write an edit whose new text is the same as before, longer than 2,000 characters, or contains < > [ ] or control characters (a CMS may read them as tags or shortcodes).
- Before writing we record which field changes from what to what, and after writing we read it back. If the saved value differs, we put the old value back and report a failure.
- If a write is interrupted, we read the current value next time: if it was written we’re done, if it’s unchanged we continue, otherwise we report a failure. We never write the same change twice.
- Undo puts the old value back only while the field still holds the value Get1pct wrote. If someone has edited it since, we leave it.
- We only call the CMS’s official API host. We don’t follow redirects, give up after 15 seconds and don’t read responses over 2 MB.
- Get1pct writes only to entries that are published, not archived and have no unpublished changes. After changing a field it publishes the entry. If publishing fails, it puts the old value back.
To compare Shopify, Webflow, Contentful and microCMS side by side, see what each CMS connection can do.
Check the connection
Once connected, use “Check the connection” under the CMS in Connections. Enter the URL of one live article or item page.
- Read test: we find the CMS entry and show, for the title, description and heading, whether the CMS value is exactly the text on the live page. Only those fields are updated automatically; for the others the table shows why. Nothing is changed.
- Write test: we write the current value of one field that can be updated back into it as is, and read it back. The live page doesn’t change. If the token can’t write, or your CMS changes the text when saving, the result says so.
Run the read test first, then the write test. If the write test says the next edit can’t be applied, publish the site (or entry) in your CMS and let us know.
After connecting
- Get1pct writes an edit you choose only when the field’s current value exactly matches the text on the live page. It then publishes the entry. If publishing fails, it puts the old value back. To reverse an applied edit, click “Undo the change” on that edit in the dashboard.
- Get1pct leaves entries with unpublished changes alone, so it never publishes someone else’s work in progress. You copy those edits and apply them yourself.
- If your site is statically generated, the change appears on the live page after the build that runs when the entry is published.
Troubleshooting
- “We could not connect.”
- First, look at the list under Settings → CMA tokens. If the token’s row shows Authorize access, click it and authorize your organization. Then check the space ID, environment ID, locale and data region, and that the user who created the token belongs to the space. Check the spelling of the content type and field IDs, including upper and lower case, and that the fields are Short text or Long text.
- Applying an edit fails
- Get1pct can’t check write and publish access when you connect, so the first edit is where a problem shows up. Check that the user who created the token can publish the entry (the Author role can’t) and that the token hasn’t expired. If publishing is refused, Connections says the access isn’t enough. If the token expired or was revoked, it says “Reconnect needed”.
- An edit isn’t applied automatically
- To be safe, Get1pct leaves an entry alone when it has unpublished changes or its value differs from the live page. The edit screen shows how each edit will be applied.
To stop
Click “Disconnect” under Connections in your dashboard. Get1pct deletes the token it stored. The token still exists in Contentful, so also revoke it in the list under Settings → CMA tokens. Removing the Get1pct user from the space also stops the token from reading or changing that space.
If the steps don’t match what you see, contact us with your site URL and the screen where you got stuck. Please don’t send passwords.