Automation library · Content

Post PR preview page screenshots to GitHub pull requests

Started by another system calling it, and works across GitHub. 10 steps, 1 branch, 2 loops or waits: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
2Loops or waits
1Service it connects to

The flow

Starts it 1Logic 7Service 2

The steps in the order they run, from what starts it.

  1. 1When a Pull Request Preview Is ReadyWebhookStarts it
  2. 2Build Preview Page ListCodeLogic
  3. 3Wait for Preview to SettleWaitLogic
  4. 4Loop Over Changed PagesSplit In BatchesLogic
  5. 5Build PR CommentCodeLogic
  6. 6Capture Preview PageSnapshot SiteService
  7. 7Post Preview Screenshots on the PRGithubService
  8. 8Check for API ErrorIfLogic
  9. 9Record Failed CaptureSetLogic
  10. 10Record Page CaptureSetLogic

How it's built

Starts on
Another system calling it
Steps
10, with 1 branch, 2 loops or waits
Size
Medium: a working afternoon
Connects to
GitHub
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 10 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 10 steps before you point it at anything that matters.