Skip to main content

PageVitals integration

Data and analytics connector, available on Zeplik

PageVitals is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect PageVitals and Zeplik can act on your data and analytics for you: PageVitals provides website performance monitoring, synthetic testing, real-user monitoring reports, performance budgets, and optimization insights. You stay in the conversation while the assistant does the work in PageVitals directly.

Zeplik exposes 15 read actions and 13 write actions for PageVitals. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in PageVitals without your consent.

Try PageVitals on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with PageVitals

Read from PageVitals (15)

Runs automatically in any conversation.

  • Get multistep test

    Get one multistep test definition, including its configured steps.

  • Get page metrics

    Get the latest Lighthouse and Chrome UX metrics for one configured page and device.

  • Get page opportunities

    List Lighthouse improvement opportunities for a page/device, or return the full variable-shape details for one opportunity ID.

  • Get page timeline

    Get one historical timeline for a page/device: combined loading metrics, CrUX, network bytes, CPU time, or Google Search performance. Google Search requires that integration on the website.

  • Get test

    Get the detailed Lighthouse, timing, resource, budget, and validation summary for one synthetic test. Provider values, nulls, metric scales, and JSON-looking strings are returned unchanged.

  • Get test report

    Get one specialized synthetic-test report: keyed Lighthouse opportunities, the request waterfall, or grouped HTML validation findings. Validation always omits the embedded raw HTML.

  • Get test series

    Get one synthetic test series and its individual tests, statuses, page IDs, device variants, and failure messages.

  • List budgets

    List performance budgets, current status, notification settings, and affected pages for a website.

  • List configured pages

    List the raw pages configured for PageVitals monitoring on a website.

  • List multistep runs

    List historical runs for one multistep test, including status, duration, interaction, layout-shift, CPU, transfer-size, and blocking-time metrics.

  • List multistep tests

    List multistep tests configured for a website with recent metrics, state, and success rates. A website with no configured multistep tests returns an empty tests list.

  • List page metrics

    List every configured page/device combination for a website with recent timeline and latest performance metrics.

and 3 more.

Act in PageVitals (13)

Runs only after you enable write access.

  • Add configured pages

    Add one or more explicitly supplied pages to PageVitals monitoring for a website. This persistent bulk operation can consume monitored-page quota and cause future synthetic tests, so call it only when the user explicitly requests every URL or path and alias. Never discover or scrape pages automatically.

  • Create budget

    Create a persistent PageVitals performance budget for a website. This changes monitoring and may change owner alerting behavior, so call only when the user explicitly requests the budget and supplies the complete metric, comparison direction, numeric threshold in the metric's native unit, and device scope. Never infer metric units or operator direction.

  • Create multistep test

    Create an empty PageVitals multistep test definition with an explicit name and device profile. This only saves persistent configuration: it does not run the test, trigger any synthetic checks, or consume test-run quota.

  • Create website

    Add a domain to the PageVitals account and begin managing it. This may consume website quota and start monitoring, so call only when the user explicitly asks to add the domain.

  • Delete budget

    Delete one PageVitals performance budget and stop enforcing its threshold. This is a destructive alerting mutation; use only when the user explicitly selects the exact budget ID for deletion.

  • Delete configured page

    Permanently delete one PageVitals configured page and all of its test results, including historical results. This is irreversible; use only for an explicit request naming the exact website ID and configured-page ID.

  • Delete multistep test

    Permanently delete one PageVitals multistep test definition. This is irreversible; use only when the user explicitly identifies the exact website ID and test ID.

  • Delete website

    Permanently delete one PageVitals website and all of its tests, metrics, analytics, and configuration. This is irreversible; use only for an explicit request naming the exact website ID.

  • Run multistep tests

    Trigger exactly one named multistep test or intentionally fan out to every multistep test configured for a website. Every triggered run consumes PageVitals test quota and may incur cost. Choosing target='all' can start many jobs, so use it only when the user explicitly requests an all-tests run.

  • Run test series

    Trigger synthetic tests for selected page/device variants, or for every configured test when pages is omitted. This action consumes PageVitals test quota and may incur cost; call it only when the user explicitly requests a new run.

  • Update budget

    Replace a PageVitals performance budget's complete metric threshold and device scope. This may change monitoring alerts or notifications. Read the current budget first, use its exact website and budget IDs, and provide all four desired state fields because partial PUT behavior was not safely tested.

  • Update configured page

    Update a configured PageVitals page's URL, display alias, or both. This changes persistent monitoring configuration; use the exact page ID from List Configured Pages and provide at least one new value.

and 1 more.

How to connect PageVitals

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try PageVitals immediately.

  2. Connect PageVitals

    Open Settings and go to Connectors, then press Connect on PageVitals. You can also connect from the PageVitals page in the app.

  3. Add your PageVitals API key

    Paste your PageVitals API key when prompted. Zeplik stores it securely on the server and starts working with PageVitals right away.

Frequently asked questions

Can I use PageVitals with Zeplik?
Yes. PageVitals is available as an integration on Zeplik. Connect it once and the AI assistant can work with your PageVitals account inside any conversation.
What can Zeplik do with PageVitals?
Once connected, Zeplik has 15 read and 13 write actions for PageVitals. PageVitals provides website performance monitoring, synthetic testing, real-user monitoring reports, performance budgets, and optimization insights.
How do I connect PageVitals to Zeplik?
You connect PageVitals by pasting your own PageVitals API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in PageVitals without asking?
No. Zeplik reads from PageVitals by default. Any action that changes data in PageVitals requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting PageVitals cost?
Connecting PageVitals is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related data and analytics integrations

More on Zeplik

Connect PageVitals to your AI assistant

Every model, one chat. Bring PageVitals into Zeplik and let the assistant do the work.