Page Load

Run a workflow every time a page whose address matches your patterns finishes loading.

What it does

Each time any tab finishes loading a page, the extension compares the page address with the URL Patterns of every activated workflow that has a Page Load trigger. When one pattern matches, that workflow runs from this trigger, with details of the tab.

It fires once per completed load: opening a page, following a link to a new page, or reloading. Changes inside a page that do not reload it (many modern web apps work this way) do not fire it.

When to use it

• Capture data from a site every time you open it, such as an order page or a dashboard.
• Change or check a page right after it opens, for example read its title or take a screenshot.
• Log the pages you visit on a given site.

To react when a tab is opened, closed or its address changes, use Navigation. To react to a change inside an open page, use Element Change.

Inputs and settings

Réglage	Type	Ce que cela fait
URL Patterns	Tags	Par défaut : ["<all_urls>"]

Each pattern has three parts: scheme://host/path. Use * as a wildcard.

• https://*.example.com/* matches example.com and every subdomain, on any path.
• https://github.com/*/pull/* matches pull request pages on GitHub.
• *://news.ycombinator.com/* matches the site over http or https.
• <all_urls> (the default) matches every web page.

The path part also covers the query string and # part of the address. Add several patterns to watch several sites. Keep them narrow: with the default, the workflow runs on every page you load.

Outputs

• Output

Each output item has these fields:

Field	Type	What it holds
triggerType	Always "pageLoad"
triggeredAt	Text
url	Text
title	Text
tabId	Number
windowId	Number
status	Text

Shape of an output item

{
  "triggerType": "pageLoad",
  "triggeredAt": "…",
  "url": "…",
  "title": "…",
  "tabId": 0,
  "windowId": 0,
  "status": "…"
}

url and title describe the page that loaded, and status is complete. Pass tabId to nodes that act on a tab, such as Tab Control, so they work on the page that fired the trigger. When you test the trigger yourself in the designer, these fields are empty.

Dependencies and credentials

None. This node needs no connection and has no slots for other nodes.

Example workflow

Keep a list of the GitHub pull requests you open:

1. Add Page Load with URL Patterns https://github.com/*/pull/*.
2. Add Data Store with Operation Set, Key last-pr and Value {{ $input.url }}.
3. Add Browser Notification with Title PR opened and Message {{ $('Page Load').title }}.
4. Activate the workflow and open a pull request.

Common issues

• Nothing happens when the page loads. Check that the workflow is activated and that a pattern matches the full address, including https:// and a path part (/*). https://example.com without a path never matches; use https://example.com/*.
• The workflow runs on every page. URL Patterns is still <all_urls>. Replace it with the sites you want.
• It does not fire when a web app changes view. The page did not reload, so no load happened. Use Navigation for address changes the browser reports, or Element Change to watch the content.
• It does not run in the web app. This node runs in the browser extension; install it and activate the workflow there.

Related nodes

• Navigation: fire when a tab is opened, changes address or is closed.
• Element Change: fire when part of an open page changes.
• Tab Control: act on the tab that loaded.