Rewrite sections, not pages
It is almost impossible to learn anything from whole-page rewrites. If conversion changes, it is never clear whether the headline, the proof section, or the button made the difference, so the following version is just a guess presented as a decision.
Section-level changes fix that. Each section makes a separate statement as to why the page is underperforming, and each of them can be accepted, rejected, or undone individually.
Review is quick because each rewrite is paired with the original. When a reviewer compares two versions of a single section, they can form an opinion in a matter of seconds. If they read a new page, they have to form an impression.
Before all this, you have to ask honestly whether copy really is the limiting factor. A page that has the wrong kind of traffic does not have a copy issue, and changing it produces a better page that no one wanted.
How the ActionFlow runs on the canvas
A Scrappey node reads the current copy from the live URL, or you paste it.
The Generate Object node begins by dividing the page into its sections (hero, proof, objection handling, and call to action) and returns those sections as an array. Because the split happens before the rewrite, every later step is scoped to a section.
The Loop node walks the sections. Inside it, the Generate Text node rewrites one section based on the target audience and offer, and provides a one-line explanation.
A Merge node assembles a comparison that includes, in order, the original, the rewrite, and the rationale for each section.
A Notion node receives the comparison as a single page, which is the artifact the reviewer works with. The Slack node in the Human in the Loop category gathers decisions for each section rather than giving a single verdict on the page.
If you keep both versions in Notion, reverting a section means copying a block rather than restoring the page. When you run a test, a Google Sheets node keeps a record of which sections were live in each variant, so the results can be attributed.
Nodes this ActionFlow uses
- Scrappey (Util): reads the live page. Start takes pasted copy instead.
- Generate Object (AI Core): splits the page into sections as an array before anything is rewritten.
- Loop (Control): walks the sections one at a time.
- Generate Text (AI Core): rewrites one section and returns a one-line rationale with it.
- Merge (Control): assembles the original, rewrite, and rationale in order.
- Notion (Integration): holds the comparison and both versions for selective revert.
- Slack (Human in the Loop): collects decisions per section rather than per page.
- Google Sheets (Integration): records which sections were live in which variant.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.