Journey Monitor
Check that your own site still works for visitors: define a journey (open a page, click, fill, check text) and run it in a real browser. Run it on demand or on a schedule, and get an email when it starts failing and again when it recovers. Read-only: forms and payments are never submitted, and only your own live domains can be visited. Paid plans: the number of journeys, runs per day, shortest schedule and days of history depend on your plan (see get-config). Runs on your own Browserless account: create a free account at browserless.io and store your API key with setup_integration (browserless_api_key); runs use your Browserless units.
setup_integration or the Dashboard Vault — they're encrypted
with AES-256-GCM and never exposed.
- Create a free account at browserless.io.
- Copy your API key from your Browserless dashboard (API Keys).
- Ask your AI assistant to run setup_integration for journey-monitor with that key (browserless_api_key). It is stored encrypted in your project vault.
Required Credentials
Get your API key at www.websitepublisher.ai →
Try it with your AI assistant
Once WebsitePublisher is connected to your AI assistant, paste one of these into the chat. Replace the parts in [brackets] with your own details.
@WebsitePublisher set up a daily check that my [page] loads and shows the Book now button, and alert me if it fails@WebsitePublisher run my checkout journey now and tell me which step fails, if any@WebsitePublisher show the recent runs of my site checks and any failures this weekWith WebsitePublisher, set up a daily check that my [page] loads and shows the Book now button, and alert me if it failsWith WebsitePublisher, run my checkout journey now and tell me which step fails, if anyWith WebsitePublisher, show the recent runs of my site checks and any failures this weekWith WebsitePublisher, set up a daily check that my [page] loads and shows the Book now button, and alert me if it failsWith WebsitePublisher, run my checkout journey now and tell me which step fails, if anyWith WebsitePublisher, show the recent runs of my site checks and any failures this weekEndpoints (6)
Create or replace a journey, matched on journey_key. start_url and every navigate url must be https:// on one of your own live hosts (see get-config allowed_hosts). Steps run in order after the start page loads. Actions: navigate {url}, click {selector}, fill {selector, value}, wait {ms 100-10000}, wait_for {selector}, assert_visible {selector}, assert_text {text, selector?}. Selectors are CSS selectors. Only GET requests leave the browser, so a submit or payment button is blocked; check the page up to that point. Use test values in fill, never real personal data.
| Field | Type | Required | Description |
|---|---|---|---|
journey_key |
string | ✓ Yes | Lowercase letters, digits, - and _, e.g. "checkout-flow". |
name |
string | No | |
start_url |
string | ✓ Yes | |
steps |
array | No | e.g. [{"action":"click","selector":"a[href='/pricing']"},{"action":"assert_text","text":"Pricing"}]. Max 25. |
viewport_width |
integer | No | 320-1920, default 1280. |
viewport_height |
integer | No | 480-1600, default 800. |
is_active |
boolean | No | false pauses the journey. |
interval_minutes |
integer | No | Run automatically every N minutes, from the minimum of your plan (get-config min_interval_minutes) up to 1440. 0 or omitted = manual runs only. Scheduled and manual runs share the runs per day of your plan. |
alerts_enabled |
boolean | No | Default true: for scheduled runs, mail the project owner once when the journey starts failing and once when it passes again. |
All journeys of this project with their last status, and the plan limits. fill values are shown as (hidden).
No input parameters required.
Delete a journey and its run history permanently. To pause it instead, use set-journey with is_active false.
| Field | Type | Required | Description |
|---|---|---|---|
journey_key |
string | ✓ Yes |
Run a journey now in a real browser and return the result: status passed / failed / error, the failing step and why. Takes up to about a minute. Counts toward the runs per journey per day of your plan; at least 2 minutes between runs of the same journey.
| Field | Type | Required | Description |
|---|---|---|---|
journey_key |
string | ✓ Yes |
Recent runs, newest first, optionally for one journey_key: status, trigger (manual or scheduled), failing step and reason. History is kept for the retention_days of your plan (see get-config).
| Field | Type | Required | Description |
|---|---|---|---|
journey_key |
string | No | |
limit |
integer | No | Default 20, max 100. |
Whether Journey Monitor is available on this plan, the hosts a journey may visit, the allowed actions and all limits, including the shortest schedule (min_interval_minutes).
No input parameters required.
MCP Tool Names
When using this integration through an AI assistant (Claude, ChatGPT, Cursor, etc.), the endpoints are available as MCP tools:
| Endpoint | MCP Tool Name |
|---|---|
| set-journey | journey-monitor_set_journey |
| list-journeys | journey-monitor_list_journeys |
| delete-journey | journey-monitor_delete_journey |
| run-now | journey-monitor_run_now |
| get-runs | journey-monitor_get_runs |
| get-config | journey-monitor_get_config |
Website