1What FoxPlug reads from Webflow
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Your sites | the list of sites the token can see, first 3 read: site id, display name (or short name) and the time the site was last published |
| Pages of each site | up to 100 pages per site: id, title, created time, and whether the page is a draft or archived. Only a page created since the last check, not a draft and not archived, is kept |
| CMS collections and their newest published items | up to 5 collections per site, 30 items each, newest published first: item id, name (or slug), created time, last published time, draft and archived flags. Only an item created since the last check and published is kept |
| When the site itself was last published | the last published time on the site record; a publish later than the last check becomes one moment for that site |
2Moments it finds, and what each becomes
A moment is one thing that happened in Webflow worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
you publish a Webflow site
The moment is titled like this: Published Acme Studio
You press Publish on a site called Acme Studio. When you next press Check for what's new, FoxPlug makes one moment titled 'Published Acme Studio' with the line 'Acme Studio was published on Webflow.' It is scored like any other update.
a new page goes live on the site
The moment is titled like this: New page: Pricing
You add a Pricing page and publish. The moment reads 'New page: Pricing' with the line 'A new page, Pricing, is live on Acme Studio.' A page still in draft or archived is not counted.
a new CMS item is published
The moment is titled like this: Published: How we cut load time in half
You write a blog post in your Blog collection and publish it. The moment reads 'Published: How we cut load time in half' with the line 'How we cut load time in half was published to Blog on Acme Studio.'
you edit the words on a page or fix a typo in an old CMS item
The moment is titled like this: none: edits are skipped on purpose
You change a headline on the About page and republish. No page is new and no item is new, so the only moment is the site publish itself. Copy tweaks are not worth a post.
3How the brain uses it
The rules below are the ones that apply to Webflow. The same rules, with worked examples, are on the brain page.
- A page that went live, or a CMS item that was published, is an update; a copy tweak (an edited page or edited item) is skipped. How the brain decides
- Webflow also sends live events, checked by a signature; page metadata and edited-item events are logged and ignored. How the brain decides
- Under 35 no post is written; the update is marked too small to post. How the brain decides
- Reads are read-only and happen only when you press Build the brief or Check for what's new. How the brain decides
4Set up Webflow in a few steps
Access: site token (one token per Webflow site). What to give it: site token, read-only (Sites, Pages, CMS) plus Webhooks.
- Open your site in Webflow. You must be a site administrator.
- Go to Site settings, then Apps and integrations, then API access.
- Press Generate API token and give it a name such as FoxPlug.
- Set Sites, Pages and CMS to Read-only, and Webhooks to Read and write so live events can be set up.
- Press Generate, copy the token and paste it into FoxPlug.
- A token belongs to one site, so repeat these steps with a new token for each extra site.
5Limits worth knowing
Where it stops, so nothing surprises you.
- First 3 sites, first 100 pages per site, first 5 collections per site and 30 newest items per collection.
- The window is the time since the last check, or 7 days back on the first read; the first read keeps only the single newest moment.
- A page or item counts as new only by its created time, so an old draft that you publish today is not seen as a new page or item.
- If the pages list or the collections list fails for one site, that part is logged and skipped while the rest still reads.
- A site with more than 100 pages is read only for its first 100; no second page of results is requested.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Form submissions, e-commerce orders, customers or members (only the sites list, the pages list and the CMS collections and items are requested)
- Draft or archived pages and draft or archived CMS items (they are dropped before a moment is made)
- Anything it changes: the reader only asks for data and edits no page, item or setting
7Questions
Is the Webflow token read-only?
Mostly. You set Sites, Pages and CMS to Read-only. Webhooks are set to Read and write, only so FoxPlug can register its own live-event hooks on your site; disconnecting removes them. The reader itself only asks Webflow for data.
Does one token cover all my Webflow sites?
No. The connect guide says a Webflow site token belongs to one site, so each site needs its own token.
Will a typo fix or a changed headline become a post?
No. Edited pages and edited CMS items are treated as copy tweaks and skipped. Only a new page, a newly published CMS item or a site publish makes a moment.
When does FoxPlug look at Webflow?
When you press Check for what's new. Webflow can also send live events to FoxPlug, but they only mark a moment as waiting; nothing is fetched until you press.
What does a post look like for a published blog item?
The moment's title is 'Published:' followed by the item's name, and its line says it was published to the collection on your site. The post text is written from that after scoring.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.