CONTENT CREATION

Recapture affected doc screenshots on every frontend deploy

When a Vercel frontend deploy succeeds, this finds Notion knowledge-base articles touching the changed UI areas and recaptures their screenshots so docs update the moment…

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerVercel deploy-success webhook firesVercelVercel
  • LogicResolve changed routes to user-facing UI pages
  • ActionFind Notion KB articles tagged with those routesNotionNotion
  • ActionRecapture each documented screen post-deployBrowserbase
  • ActionReplace stale images in matching Notion pagesNotionNotion
  • OutputPost updated-article summary to SlackSlack

What it does

Listens for a successful Vercel production deploy, reads which UI routes changed, maps those routes to the Notion knowledge-base articles that document them, and recaptures the relevant screenshots in a fresh browser session. The updated images are written back into the Notion pages automatically.

When to use it

Use it when your docs live in Notion and you want screenshots to track the product in near real time instead of waiting for a scheduled sweep. Ideal for fast-moving teams shipping UI changes daily.

How it works

  1. 1A Vercel deploy-success webhook triggers the workflow.
  2. 2A logic step reads the deployment's changed routes and resolves which are user-facing UI pages.
  3. 3Notion is queried for articles tagged with those routes.
  4. 4Browserbase recaptures each documented screen against the new deploy URL.
  5. 5The fresh captures replace the stale images directly in the matching Notion pages.
  6. 6A summary of updated articles posts to the docs channel in Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect VercelDeploys, runtime logs, analytics.
  2. 2
    Connect NotionPages, databases, comments.
  3. 3
    Connect BrowserbaseHeadless browsers, sessions, replays.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.