Skip to main content
If your site’s pages live in Webflow or WordPress rather than in a repository, Attensira can make the fix itself instead of describing it. What it writes is a draft, an unpublished Webflow item or a WordPress draft revision, sitting in your own editor, where you approve it or throw it away.

​
What we change

On a page that already exists, one field at a time: a meta description, a title, an Open Graph tag, the body of a post. New articles are created as drafts, in Webflow (see New articles). We never publish a new article, and we never delete a page: a URL somebody links to is not something an automation gets to remove.

​
Drafts, and when something goes live

  • Ask or draft mode. Every change we propose is written as a CMS draft and waits in your Inbox. Nothing a reader sees changes until you say yes.
  • You approve it. We publish it. In Webflow that means publishing the site; in WordPress, setting the post to published.
  • Act mode. We publish without asking only when all three hold: the change is hygiene (structured data, a meta tag, alt text, an internal link, not a sentence carrying a price, a number with a unit, a promise or a competitor’s name), the page is inside the paths you allowed, and the workspace is still in act mode at the moment we write. Anything else becomes a draft, and the Inbox says which rule stopped it.
We use the same classifier here as for a repository change (see Approval modes), so a price appearing in a Webflow meta description stops for you just as it would in a file.

​
New articles

When the agent writes an article for your site, it is filed for your approval with where approving will send it. Articles always wait for a person’s yes, in every mode. Where it goes is worked out from what the workspace has connected, in this order:
  1. A connected repository in which a blog directory can be found: a pull request adding the file.
  2. Your site’s CMS: Webflow, then Shopify (an unpublished blog article). WordPress cannot take new articles yet; see below.
  3. Notion: a draft page in your blog database.
  4. Otherwise a copy: you paste it into your site and mark it shipped with its live URL.
A CMS counts only when it can say which collection the article would land in, so an article is never filed for an approval that would fail afterwards: it becomes a copy, with the reason given. If you ask for a CMS that is not connected, the article is still written and becomes a copy, and the reply says why. In Webflow, the article is filed in your Inbox with Publish to Webflow as draft, and approving it creates it as a draft item in your blog collection: the title, a slug made from the title, and the body as rich text. Nothing is published, in any mode, and we never publish the site for a new article. The item waits in your Webflow CMS until you publish it there, and it is recorded as Draft in Webflow. Once it is live, mark the item shipped with its URL; that starts the before-and-after re-reads.
  • Which collection. We look for the collection named like a blog that has a rich text field for the body, or, when none is named like one, the only collection with a rich text field. If we cannot tell which of your Webflow sites is this workspace’s, if several collections could be your blog, if none has a rich text field, if the body field cannot be told apart from the others, or if the collection requires a field we would have to invent a value for, the article is not sent to Webflow. It goes to Notion when Notion is connected, and otherwise is filed as a copy for you to paste, with the reason. If an article was filed for Webflow and one of these becomes true before you approve it, approving brings it back to you with the reason and writes nothing.
  • One article per slug. Approving twice, or a retry after a timeout, finds the item already there and creates no second one. If your collection already has a different item at the same slug, or the same title with different words, nothing is written over it, and the item comes back to you saying what to do instead: paste the new version into that item, or rename one of them and approve again.
  • No HTML from the article reaches your CMS. The body is converted from Markdown with raw HTML switched off, so a tag or a script quoted from a web page is dropped, not stored.
In WordPress, new articles cannot be created yet. The connection we use can edit posts that exist but cannot create one, so an article for a WordPress site goes to Notion when Notion is connected, and otherwise is a copy: paste it into WordPress and mark it shipped with its URL.

​
If the page changed since you approved

We re-read the field immediately before writing. If it no longer holds what the proposal was made against, because somebody on your team edited it in the meantime, we do not write. The item comes back to your Inbox with a fresh diff.

​
What appears in your receipt

Every write is recorded as a page change with a link to the page or the draft. A draft is recorded as a draft; we never write “published” about something nobody can see yet.

​
Connecting

  1. Open Settings → Integrations in your workspace.
  2. Find Webflow or WordPress and press Connect.
  3. Sign in at Webflow or WordPress and authorise the connection. The sign-in happens on their side; we never see your password.
  4. Choose the site or account when asked. You are returned to your workspace with the row showing Connected.
  5. Check the path list under Settings → Autopilot. It decides which pages act mode may publish to on its own, and it starts at your docs and content directories.
You can disconnect at any time from the same screen. If you connect both Webflow and WordPress, we work out which one a page belongs to from the page’s own URL. Permissions we ask for: read your collections, posts and pages; update one item; create an unpublished item in your blog collection (Webflow); publish the site (Webflow) or set a post’s status (WordPress). We never ask for delete.