Journey Monitor

⚡ Built-in — Platform Built-in

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. Read-only: forms and payments are never submitted, and only your own live domains can be visited. Paid plans.

⚡ Built-in — No Setup Required This integration is built into the WebsitePublisher platform. All endpoints are available immediately — no API key needed.

Endpoints (6)

POST set-journey

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.

GET list-journeys

All journeys of this project with their last status, and the plan limits. fill values are shown as (hidden).

No input parameters required.

POST delete-journey

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

POST run-now

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

GET get-runs

Recent runs, newest first, optionally for one journey_key.

Field	Type	Required	Description
`journey_key`	string	No
`limit`	integer	No	Default 20, max 100.

GET get-config

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`

← Back to all integrations