Privacy-focused web analytics platform that provides simple, lightweight, and GDPR-compliant website statistics
Privacy-focused web analytics platform that provides simple, lightweight, and GDPR-compliant website statistics On Nagent, Plausible Analytics is exposed as a fully-configurable analytics integration that any agent can call — 13 actions, and API key authentication. No code is required to wire Plausible Analytics into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Plausible Analytics to automate the kinds of tasks analytics teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Plausible Analytics into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Plausible Analytics, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PLAUSIBLE_ANALYTICS_CHECK_HEALTHTool to check the health status of the Plausible Analytics API. Use when verifying API connectivity and service availability before making other API calls.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_GET_BREAKDOWN_STATSTool to retrieve breakdown statistics for a specific property (dimension) from Plausible Analytics. Use when you need to analyze top sources, top pages, device breakdown, geographic distribution, or any other dimensional breakdown of your site traffic. This is a legacy Stats API v1 endpoint used for Top Sources, Top Pages and similar reports.
Input parameters
Date for period context or custom date range. For 'custom' period, use two ISO-8601 dates separated by comma (e.g., '2023-01-01,2023-01-31'). For other periods, single date in YYYY-MM-DD format to anchor the period
Page number for pagination. Use with limit parameter to retrieve results beyond the first page. Starts at 1
Maximum number of results to return (1-1000). If not specified, returns all available results up to 1000
Time period for stats. Valid values: '12mo' (last 12 months), '6mo' (last 6 months), 'month' (current month), '30d' (last 30 days), '7d' (last 7 days), 'day' (current day), 'custom' (custom range using date parameter with two ISO-8601 dates separated by comma). Defaults to '30d'
Filters to apply to the query. Format: 'property==value' or 'property==value;property2==value2'. Use semicolon to separate multiple filters. Supports operators: == (equals), != (not equals), ~ (contains), !~ (does not contain)
Comma-separated list of metrics to include. Available metrics: visitors (unique visitors), visits (total visits), pageviews (total page views), views_per_visit, bounce_rate (percentage), visit_duration (seconds), events (total events), conversion_rate (percentage), time_on_page (seconds). If not specified, only the visitor count for each breakdown value is returned
Domain of your site on Plausible (e.g., 'example.com'). This is the site ID as configured in your Plausible account
Property to break down by. Supported values: event:page, event:goal, visit:source, visit:referrer, visit:utm_medium, visit:utm_source, visit:utm_campaign, visit:utm_content, visit:utm_term, visit:device, visit:browser, visit:browser_version, visit:os, visit:os_version, visit:country, visit:region, visit:city, visit:entry_page, visit:exit_page, or event:props:<custom_prop_name> for custom properties
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_GET_PLUGIN_CAPABILITIESTool to retrieve available capabilities for the Plausible Analytics Plugins API. Use this to check which features are enabled for the authenticated account, such as Goals, Funnels, Stats API, and more.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_GET_REALTIME_VISITORSTool to retrieve the number of current visitors on your site in the last 5 minutes. Use this to get real-time visitor counts from the Plausible Analytics Stats API v1.
Input parameters
Domain of your site on Plausible (e.g., 'example.com')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_GET_SITETool to retrieve details for a specific Plausible Analytics site. Use when you need site configuration including domain, timezone, custom properties, and tracker script settings.
Input parameters
Domain/ID of the site to retrieve (e.g., 'example.com' or 'composio')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_GET_TIMESERIES_STATSTool to retrieve timeseries visitor data from Plausible Analytics over a specified time period. Use this to get historical trends for metrics like visitors, pageviews, bounce rate, and visit duration. This is the legacy Stats API v1 endpoint typically used for the main visitor graph.
Input parameters
Time period for the timeseries data. Examples: '6mo' (6 months), '12mo' (12 months), '30d' (30 days), 'day' (today), 'month' (current month). If not specified, defaults to '30d'.
Filter expression to drill down data. Format: 'property==value' or 'property==value;property2==value2'. Examples: 'event:page==/blog', 'visit:source==Twitter'.
Comma-separated list of metrics to show for each time bucket. Valid options: 'visitors', 'visits', 'pageviews', 'views_per_visit', 'bounce_rate', 'visit_duration', 'events', 'conversion_rate'. Defaults to 'visitors' if not specified.
Domain of your site on Plausible (e.g., 'example.com')
Interval for grouping timeseries data.
Whether to include imported statistics from other analytics platforms. Defaults to false if not specified.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_LIST_CUSTOM_PROPSTool to list all custom properties configured for a site. Use when you need to retrieve custom property configurations for a Plausible Analytics site. Enterprise feature only.
Input parameters
Domain of the site to retrieve custom properties for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_LIST_GOALSTool to list all goals configured for a site. Use when you need to retrieve conversion goals and custom action tracking configured for a Plausible Analytics site.
Input parameters
Pagination cursor for fetching the next page of results. Use the 'after' value from a previous response's meta.
Maximum number of goals to return per page. Defaults to API default if not specified.
Pagination cursor for fetching the previous page of results. Use the 'before' value from a previous response's meta.
Domain of the site to retrieve goals for.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_LIST_GUESTSTool to list all guest users who have access to a site's dashboard in Plausible Analytics. Use when you need to see which guests have been granted access to view a specific site's analytics. This is an Enterprise feature.
Input parameters
Domain of the site to list guests for (e.g., 'example.com')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_LIST_SITESTool to list all sites the API key owner's Plausible account can access. Returns domain, timezone, and creation info with pagination support. Use when you need to retrieve all sites or paginate through large site lists.
Input parameters
Pagination cursor for fetching the next page of results.
Maximum number of sites to return per page. Defaults to 100 if not specified.
Pagination cursor for fetching the previous page of results.
ID of the team to scope the list of sites by. If provided, only sites belonging to this team will be returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_LIST_TEAMSTool to list all teams available for the API key owner. Use when you need to retrieve teams for site provisioning to a specific team.
Input parameters
Pagination cursor for fetching the next page of results.
Maximum number of teams to return per page. Defaults to 100 if not specified.
Pagination cursor for fetching the previous page of results.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_QUERY_STATSTool to query analytics stats for a site using the Stats API v2. Use when you need to retrieve historical or real-time statistics such as visitors, pageviews, bounce rate, visit duration, and more. Supports filtering, grouping by dimensions, and custom date ranges.
Input parameters
Array of filter conditions to apply to the query. Each filter is an array with format: \[dimension, operator, value\]. Operators: 'is', 'is_not', 'contains', 'does_not_contain'. Example: \[\['event:page', 'is', '/blog'\], \['visit:country', 'is', 'US'\]\].
List of metrics to calculate. Available metrics: 'visitors' (unique visitors), 'visits' (total visits), 'pageviews' (total page views), 'views_per_visit' (average pages per visit), 'bounce_rate' (percentage of single-page visits), 'visit_duration' (average visit duration in seconds), 'events' (total events), 'scroll_depth' (average scroll depth percentage), 'percentage' (percentage of total), 'conversion_rate', 'group_conversion_rate', 'average_revenue', 'total_revenue', 'time_on_page' (average time on page in seconds).
Domain of your site on Plausible to be queried (e.g., 'example.com', 'composio').
Date range to query. Use predefined periods: 'day' (today), '7d' (last 7 days), '30d' (last 30 days), 'month' (current month), '6mo' (last 6 months), '12mo' (last 12 months), 'year' (current year), 'all' (all time), or custom ISO8601 date array like \['2024-01-01', '2024-01-31'\].
List of dimensions to group results by. Common dimensions: 'event:goal' (goal names), 'event:page' (page paths), 'event:hostname' (hostnames), 'visit:source' (traffic sources), 'visit:referrer' (referrer URLs), 'visit:utm_medium', 'visit:utm_source', 'visit:utm_campaign', 'visit:device' (device types), 'visit:browser', 'visit:os' (operating systems), 'visit:country', 'visit:region', 'visit:city'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PLAUSIBLE_ANALYTICS_RECORD_EVENTTool to record a pageview or custom event via the Plausible Events API. Use when tracking Android/iOS mobile apps or server-side tracking. Requires proper User-Agent and optionally X-Forwarded-For headers for unique visitor counting.
Input parameters
URL of the page where the event was triggered. UTM parameters will be automatically extracted (e.g., 'https://example.com/page?utm_source=google').
Name of the event. Use 'pageview' for page views, other names become custom events (e.g., 'signup', 'purchase', 'button_click').
Custom properties for the event as key-value pairs (max 30 properties). Values can be strings, numbers, or booleans.
Domain name of the site in Plausible (e.g., 'example.com').
Revenue data for the event.
Referrer URL for this event (e.g., 'https://google.com/search').
Raw User-Agent string for unique visitor identification and device detection. Should be the actual user agent from the client's browser or app.
Whether the event counts towards bounce rate. Default is true. Set to false for non-interactive events like automatic tracking.
IP address of the client for unique visitor counting and location data (e.g., '203.0.113.195'). If not provided, the server's IP will be used.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 52 agents privately built on Nagent that already use Plausible Analytics.
Build on Nagent
Connect Plausible Analytics to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Plausible Analytics, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Plausible Analytics is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Plausible Analytics is connected, you configure its 13 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Plausible Analytics steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Plausible Analytics event fires, the agent kicks off automatically.
Every Plausible Analytics action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Plausible Analytics ships with 13 pre-built analytics actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Plausible Analytics together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Plausible Analytics-based workflows tailored to your business.