{"id":167,"date":"2026-10-23T10:58:40","date_gmt":"2026-10-23T10:58:40","guid":{"rendered":"https:\/\/docs.latw.ai\/uncategorized\/connecting-webflow\/"},"modified":"2026-10-23T10:58:40","modified_gmt":"2026-10-23T10:58:40","slug":"connecting-webflow","status":"publish","type":"post","link":"https:\/\/docs.latw.ai\/pl\/latw-cloud\/connecting-webflow\/","title":{"rendered":"Connecting Webflow"},"content":{"rendered":"

A Webflow site connects to LATW Cloud without a plugin and without a Webflow app: you generate a
\nsite token<\/strong> in Webflow and paste it in the panel. LATW Cloud then reads your content and writes
\nthe translations through the Webflow API, into the languages of Webflow Localization. The AI model,
\nthe prompt, the glossary, the budget and the target languages are set in the panel, and you order
\ntranslations there, in the site’s Content<\/strong> tab.<\/p>\n

A Webflow site is a site like any other in LATW Cloud: it works on every plan and takes one site
\nslot.<\/p>\n

What gets translated<\/h2>\n\n\n\n\n\n\n\n\n\n
In Webflow<\/th>\nWhat LATW Cloud translates<\/th>\n<\/tr>\n<\/thead>\n
Pages<\/strong><\/td>\nThe texts of the page, form placeholders, button labels, dropdown options, the texts you changed in a component on that page, and the page title, SEO title and description, Open Graph title and description<\/td>\n<\/tr>\n
Collection template pages<\/strong><\/td>\nThe texts of the template around the CMS fields \u2014 they are the same for every item of the collection<\/td>\n<\/tr>\n
CMS collections<\/strong><\/td>\nEach item’s name, plain text and rich text fields, and the alt text of its images<\/td>\n<\/tr>\n
Components<\/strong><\/td>\nThe texts of the component and the default values of its text properties. A change here shows wherever the component is used, unless a page changed that text for itself<\/td>\n<\/tr>\n
Products<\/strong> (Webflow E-commerce)<\/td>\nThe product’s name, description and your own text fields, like a CMS item<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The source is the site’s primary language. Each translation is written into its own language only:
\nthe primary language, images, prices, references and the other fields of an item are never
\nchanged.<\/p>\n

Slugs are not sent to AI. LATW Cloud makes them from the translated name (see Slugs<\/em> below).<\/p>\n

Not translated:<\/strong><\/p>\n

    \n
  • Images themselves, and the alt text of images placed on pages: the Webflow API does not localize
    \nthem. Change them in the Designer.<\/li>\n
  • Variant options of products (e.g. Size: Small<\/em>) and SKU names.<\/li>\n
  • Draft and archived pages, archived CMS items, and items that exist only in a secondary language.<\/li>\n
  • Components from a shared library, which can’t be changed in this site.<\/li>\n
  • Texts without a letter in them (numbers, prices, symbols).<\/li>\n
  • Content you excluded from translation in Webflow. If your site uses translation exclusions,
    \nLATW Cloud reads pages and components the way Webflow shows them for translation, without what
    \nyou excluded.<\/li>\n<\/ul>\n

    Before you start<\/h2>\n
      \n
    • Webflow Localization with at least one more language.<\/strong> Turn it on in the Designer and add the
      \nlanguages you want; how many you can add depends on your Webflow plan. A language that is turned
      \noff in Webflow is not chosen as a target, but you can add it in the site’s Settings<\/strong>.<\/li>\n
    • A site plan with CMS<\/strong> if you want to translate collections. Pages and components need no CMS.<\/li>\n
    • Admin access to the site in Webflow<\/strong>, to generate the token.<\/li>\n
    • A free site slot on your plan.<\/strong> See Plans<\/em>.<\/li>\n<\/ul>\n

      Generate a site token<\/h2>\n
        \n
      1. \n

        In Webflow, open the site’s Site settings \u2192 Apps & integrations \u2192 API access<\/strong> and press
        \nGenerate API token<\/strong>.<\/p>\n<\/li>\n

      2. \n

        Give it Read and write<\/strong> access to Pages<\/strong>, CMS<\/strong> and Components<\/strong>, and Read<\/strong> access
        \nto Sites<\/strong> (scopes sites:read<\/code>, pages:read<\/code>, pages:write<\/code>, cms:read<\/code>, cms:write<\/code>,
        \ncomponents:read<\/code>, components:write<\/code>).<\/p>\n

        Give Sites<\/strong> write access (sites:write<\/code>) only if LATW Cloud should publish the whole site after
        \neach job \u2014 see Publishing<\/em>.<\/p>\n<\/li>\n

      3. \n

        Copy the token. Webflow shows it only once.<\/p>\n<\/li>\n<\/ol>\n

        A token belongs to one site. Webflow allows five tokens per site and deletes a token that has not
        \nbeen used for a year.<\/p>\n

        Connect<\/h2>\n
          \n
        1. In the panel, open Sites \u2192 Add site<\/strong> and choose Webflow<\/strong> (or press Connect with a token<\/strong>
          \non the Webflow card under Integrations<\/strong>).<\/li>\n
        2. Paste the token into Site token<\/strong>. The first time you connect a site, tick I accept the
          \nData Processing Agreement<\/strong>.<\/li>\n
        3. Press Connect site<\/strong>.<\/li>\n<\/ol>\n

          LATW Cloud reads the site with the token before it saves anything: it checks that the token sees
          \none site, that Localization has a language to translate into, and that the token can read pages,
          \ncollections and components. If something is missing, the form says what. A token without write
          \naccess is only noticed by the first job, which then waits with Webflow’s reason.<\/p>\n

          When the site is connected, the panel opens its Overview<\/strong>. The site is named by its custom
          \ndomain, or by its webflow.io<\/code> address when it has none.<\/p>\n

          Connecting sends LATW Cloud the site’s name, its domains and its languages. The token is stored
          \nencrypted and is never shown again in the panel \u2014 only its last four characters.<\/p>\n

          Connecting the same Webflow site again, with a new token, does not create a second site: it keeps
          \nits settings and jobs.<\/p>\n

          How languages and statuses work<\/h2>\n

          LATW Cloud shows the languages by Webflow’s codes in lower case, e.g. de-de<\/code> for German
          \n(Germany). Choose the target languages in the site’s Settings<\/strong> tab.<\/p>\n

          Webflow does not record whether a text is translated or out of date, and LATW Cloud does not keep
          \ntrack of it for Webflow either. So on a Webflow site:<\/p>\n

            \n
          • Every item shows as Translated<\/strong> in every language, in the Content<\/strong> tab and on the
            \nOverview<\/strong>, whether it was translated or not. The status filter does not tell you what still
            \nneeds translating \u2014 choose the items yourself.<\/li>\n
          • A job always translates the whole items you selected<\/strong>, also the ones translated before. There
            \nis no Translate again<\/strong> option in New job<\/strong>: it is always on.<\/li>\n
          • A job overwrites the selected items’ texts in the target languages<\/strong>, including translations
            \nyou made or corrected in Webflow. Select only the items you want translated again.<\/li>\n<\/ul>\n

            Opening an item in the Content<\/strong> tab shows each text with its current translation in every
            \nlanguage.<\/p>\n

            Settings in the panel<\/h2>\n

            The site’s Settings<\/strong> tab has a Webflow<\/strong> card with two settings.<\/p>\n

            Publishing<\/strong> \u2014 what happens after a translation is written:<\/p>\n\n\n\n\n\n\n\n
            Option<\/th>\nWhat happens<\/th>\n<\/tr>\n<\/thead>\n
            Wait for my Publish<\/strong> (default)<\/td>\nTranslations wait in Webflow as unpublished changes until you publish the site.<\/td>\n<\/tr>\n
            Publish CMS items<\/strong><\/td>\nA translated CMS item goes live in its language at once, if it is published in the primary language. Pages and components still wait for your Publish.<\/td>\n<\/tr>\n
            Publish the whole site after each job<\/strong><\/td>\nWhen a job wrote something, LATW Cloud publishes the site to all its domains. This also publishes every other unpublished change made in the Designer. Needs sites:write<\/code>.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            If publishing fails \u2014 the token has no sites:write<\/code>, or Webflow refused \u2014 the translations are
            \nstill saved, and the job’s timeline says why the site was not published.<\/p>\n

            Slugs<\/strong> \u2014 the address of CMS items and pages in a translated language:<\/p>\n

              \n
            • Translate slugs not translated yet<\/strong> (default) \u2014 the slug is made from the translated name or
              \npage title, but only while it is still the same as in the primary language. A slug that was
              \ntranslated once is never changed, so links and search results keep working. Letters with accents
              \nand Cyrillic or Greek letters become plain Latin letters; a name in Chinese or Japanese keeps the
              \noriginal slug.<\/li>\n
            • Keep the slugs as they are.<\/strong><\/li>\n<\/ul>\n

              When Webflow refuses a slug \u2014 it is taken in that language \u2014 the translation is written with the
              \nslug the item had, and the job’s timeline says so. The home page, template pages and utility pages
              \nkeep their slugs. Webflow lets you change page slugs in a secondary language only on its Advanced
              \nand Enterprise localization plans.<\/p>\n

              What it costs and how long it takes<\/h2>\n

              Words are counted and billed the same way as on any other site \u2014 see LATW Credits and Pricing<\/em>.
              \nBecause a job sends the whole items, translating an item again costs as much as its first
              \ntranslation, even if only one text changed. The estimate counts every text of the selected items.<\/p>\n

              Webflow limits how many API requests a token makes: 60 a minute on Starter and Basic site plans,
              \n120 on CMS, Business and E-commerce. The panel’s Content<\/strong> tab and the jobs share that limit.
              \nLATW Cloud therefore works on one item of a Webflow site at a time, and a large job on a smaller
              \nWebflow plan simply takes longer. When Webflow says the limit is reached, LATW Cloud waits and
              \ncontinues on its own; the Content<\/strong> tab asks you to try again in a minute. Lists in the
              \nContent<\/strong> tab can be up to two minutes old.<\/p>\n

              Replacing the token<\/h2>\n

              When Webflow deletes the token \u2014 you removed it, or it was not used for a year \u2014 or it lacks a
              \nscope, the site’s jobs wait and the site shows as Unreachable<\/strong>. Generate a new token with the
              \nsame access and paste it in the site’s Settings \u2192 Connection \u2192 Replace token<\/strong>. LATW Cloud checks
              \nthat it belongs to the same Webflow site and uses it from then on.<\/p>\n

              Disconnecting<\/h2>\n

              Open the site’s Settings<\/strong> tab and press Disconnect site<\/strong>. A site with active jobs can’t be
              \ndisconnected \u2014 cancel them or wait until they finish.<\/p>\n

              LATW Cloud stops using the token and forgets it. Translations already written stay in Webflow.
              \nThe Webflow API can’t delete a token, so delete it yourself in Site settings \u2192 Apps &
              \nintegrations \u2192 API access<\/strong>.<\/p>\n

              To connect the site again, paste a new token in Sites \u2192 Add site \u2192 Webflow<\/strong>; the site comes
              \nback with its jobs and settings.<\/p>\n

              If something does not work<\/h2>\n
                \n
              • “Add a language in Webflow Localization”<\/strong> \u2014 Localization is off or has no other language.<\/li>\n
              • “The token has no \u2026 scope”<\/strong> \u2014 generate a new token with the access listed above.<\/li>\n
              • A job waits with “Webflow refused the request”<\/strong> \u2014 the token can’t write (no write access to
                \nPages, CMS or Components) or Localization was turned off. Fix it in Webflow, replace the token if
                \nneeded, and resume the job.<\/li>\n
              • A translation was refused<\/strong> \u2014 the job shows Webflow’s reason, e.g. a text longer than the
                \nfield allows, or HTML that does not match the page’s.<\/li>\n<\/ul>\n

                Site Unreachable<\/em> lists the causes for every platform.<\/p>\n","protected":false},"excerpt":{"rendered":"

                A Webflow site connects to LATW Cloud without a plugin and without a Webflow app: you generate a site token in Webflow and paste it in\u2026<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_latwm_translated_slug":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-167","post","type-post","status-publish","format-standard","hentry","category-latw-cloud"],"_links":{"self":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/167","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/comments?post=167"}],"version-history":[{"count":0,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/posts\/167\/revisions"}],"wp:attachment":[{"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/media?parent=167"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/categories?post=167"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/docs.latw.ai\/pl\/wp-json\/wp\/v2\/tags?post=167"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}