# General Translation Integrations: Quickstart
URL: https://generaltranslation.com/en-GB/docs/integrations/storyblok/quickstart.mdx
---

title: Quickstart
description: Quickstart to connect a Storyblok space to General Translation and translate your first story from the Dashboard.
related:
  links:
    - /docs/integrations/storyblok/guides/translating-content
    - /docs/integrations/storyblok/guides/managing-translations
    - /docs/integrations/storyblok/guides/using-translated-content
    - /docs/integrations/storyblok/guides/configuring-storyblok

---

Use the Storyblok integration to translate stories from the Dashboard.

Storyblok is a Dashboard-managed content source integration: you connect a Storyblok space using credentials, then translate stories from the Dashboard — there is no npm package to install. Translations are written back to each story as field-level localised values (Storyblok's field-level translation), so you access them through Storyblok's own Content Delivery API.

## Before you start [#before-start]

You need:

* A [Project](/docs/platform/dashboard/get-started) on a plan that includes the `project_integrations` feature.
* `project:write` permission on that Project.
* A Storyblok space with your target languages configured under **Settings > Languages**.
* A Storyblok personal access token (a Management API token).

*Note: if the `project_integrations` feature is not included in your plan, the Dashboard shows an upgrade prompt in place of the integrations catalogue, so you cannot connect a space.*

## Quickstart [#quickstart]

### 1. Configure languages in Storyblok [#configure-languages]

In Storyblok, open your space and go to **Settings > Languages**. Add each language you want to translate into.

General Translation only offers a Storyblok language as a target locale when it is both configured on the space and maps to a supported General Translation locale. See [Locales](/docs/integrations/storyblok/reference/locales).

### 2. Create a personal access token [#create-token]

In Storyblok, go to **My account > Personal access tokens** and create a token. The integration uses it to call the Storyblok Management API on your behalf.

Make a note of your space's **Space ID** (a number shown in **Settings > General**) and its **Region** (EU, US, CA, AP, or CN).

### 3. Connect the space in the Dashboard [#connect-space]

In the General Translation Dashboard, go to **Project > Integrations > Catalogue** and find **Storyblok**. Click **Connect** and fill in:

* **Space ID** — your numeric space ID.
* **Region** — the region your space is hosted in.
* **Personal access token** — the token from the previous step.

Credentials are stored in an Organization connection for the Storyblok space. The Project integration links to that connection. If successful, you are taken to the integration's management page.

### 4. Select stories and locales, then sync [#sync-apply]

On the management page:

1. Choose one or more **Story** entries (the selector is searchable and supports select all/none).
2. Set the **Source locale** (defaults to your Project's default locale).
3. Confirm the **Target locales** (defaulted from the space's configured languages, excluding the source).
4. Optionally tick **Auto-enable supported fields** to mark supported fields as translatable in Storyblok before syncing.
5. Click **Sync and apply**.

General Translation reads each story's draft, extracts translatable fields, translates them, and writes the results back into the story as a draft. Nothing is published automatically.

See [Translating content](/docs/integrations/storyblok/guides/translating-content) for the full workflow and the results summary.

### 5. Review the draft in Storyblok [#review-draft]

Open the story in Storyblok and switch to a target language to review the translated draft. When you are satisfied, publish it in Storyblok.

To fetch translated content in your app, query Storyblok's Content Delivery API with the `language` parameter. See [Using translated content](/docs/integrations/storyblok/guides/using-translated-content).
## Next steps

- /docs/integrations/storyblok/guides/translating-content
- /docs/integrations/storyblok/guides/managing-translations
- /docs/integrations/storyblok/guides/using-translated-content
- /docs/integrations/storyblok/guides/configuring-storyblok