Grok Bot + Webflow
How to connect Grok Bot to Webflow with a Bot-owned account, the routines that work, the one thing to put behind approval, and our verdict.
How a Bot connects
Webflow API token scoped to a site with CMS read/write; no site settings, no publish.
The Bot's identity
A Webflow workspace member for the Bot with a role that can edit CMS items but not publish or change design. Don't reuse a human's login. If you did, see shared computer cleanup.
Routines we've run
- Weekly — draft CMS items (changelog, fixes) from internal notes, for review
- Monthly — broken-link and stale-page report
- Never — publish
Each routine follows the four-part shape: when it runs, what it reads (bounded), what it produces, when it stops. See routines best practices.
The thing to gate
Publishing and design changes. The classic prompt-injection example is 'change the pricing page'. The Bot can't publish; a human does.
Verdict
Fine for CMS drafting. Keep publish rights human.
Setup notes
- Test every routine supervised until it's produced the right output three times.
- Add the routine's completion line to your heartbeat log so silent failures show up.
- Put the Webflow token in the Bot's connector settings or knowledge file, never in a chat message.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.