ActionPlausible AnalyticsUpdated May 2026

How do I get Plausible analytics?

Short answer: Drop the "Plausible Analytics → Get Plausible Site Stats" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 2 Plausible Analytics actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Site ID siteId	string	Required	Site ID. e.g. "example.com"
Period period	options	Optional	Period. Options: Today, 7 days, 30 days, 6 months, 12 months
Metrics metrics	string	Optional	Metrics

Sample request

{
  "siteId": "example.com",
  "period": "{{trigger.period}}",
  "metrics": "{{trigger.metrics}}"
}

Returns

{
  "results": {
    "visitors": {
      "value": 15000
    },
    "pageviews": {
      "value": 45000
    },
    "bounce_rate": {
      "value": 42
    },
    "visit_duration": {
      "value": 120
    }
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Plausible Site Stats.

Any of these apps can fire this action as part of a workflow.

Gmail → Plausible Analytics

1 Gmail triggers

Slack → Plausible Analytics

13 Slack triggers

Google Sheets → Plausible Analytics

2 Google Sheets triggers

HubSpot → Plausible Analytics

18 HubSpot triggers

FAQ

Questions about Get Plausible Site Stats.

What does the Get Plausible Site Stats action do in Plausible Analytics?

Returns key metrics — visitors, pageviews, top pages, top sources — for a date range. For "weekly traffic digest" reporting workflows without GA4's complexity.

What inputs does Get Plausible Site Stats require?

Required: Site ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Plausible Analytics returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Plausible Site Stats support batch operations?

Yes. Run Get Plausible Site Stats inside a Loop node to process arrays. Tiny Command handles Plausible Analytics's rate limits automatically so you don't have to throttle manually.

More actions