Automated iWriter Content Tracking
Every night, WebRun opens iWriter, checks your active orders for articles completed that day, logs each one into an Airtable content tracker with the writer and word count, and flags anything that reads like it needs a revision request in Notion.
How do I track completed iWriter articles automatically?
WebRun checks your active iWriter orders every night for articles completed that day, logging each one into an Airtable tracker with the writer and word count. If an article looks like it misses the brief, WebRun drafts a revision note in Notion for your editor to review, so nothing gets published without a second look.
- Every completed article is logged the same night
- Articles that may miss the brief get flagged before publishing
- Nothing requires a daily manual check of iWriter orders
Built for content agencies · SEO teams · affiliate publishers · content operations managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
iwriter.comin a real browser with your saved login - no setup, no API keys. -
1
iWriter - check completed articles
iwriter.com
WebRun opens iWriter to check completed articles. - Open your active orders and check which completed today
- Read each article's word count and writer rating level
- Skim for anything that clearly misses the brief
Done when Every article completed today has been reviewed.
-
2
Airtable - log each article
airtable.com
WebRun opens Airtable to log each article. - Add a record for each completed article with writer and word count
- Set the status to Delivered
- Keep the tracker organized by the order's topic or campaign
Done when The Airtable tracker has a record for every article completed today.
-
3
Notion - flag ones needing revision
notion.so
WebRun opens Notion to flag ones needing revision. - Flag any article that appears to miss the brief
- Note the specific concern for your editor to check
- Draft a suggested revision request. Leave it unsent for your editor
Done when Every flagged article has a drafted note waiting for editor review.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it request a revision or reject an article on its own?
No. WebRun only drafts a suggested revision note in Notion. Sending a revision request on iWriter stays your editor's decision.
How does it flag an article as needing review?
It skims each completed article against the order's brief and flags anything that appears to miss it, so your editor's attention goes to genuine concerns first.
Does it catch articles delivered outside the nightly check?
Yes. It checks the live status in iWriter each night, so anything completed that day gets logged regardless of when during the day it was delivered.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.