Get Daily Metrics
profitwell.get_daily_metrics
ActionBusiness appsconnection required
Calls the ProfitWell API with the connection's credentials.
Read day-by-day subscription trends for the current or previous month.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- ProfitWell
- Secret shape
- the private API token, or {"api_token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
month The month to break down, written as YYYY-MM. ProfitWell serves only the current month and the one before it here. | string | Yes | — | matches ^\d{4}-(0[1-9]|1[0-2])$ | 2026-09 |
metrics The trends to return, as a comma-separated list such as 'recurring_revenue,new_customers'. Leave blank for every daily trend. The daily endpoint publishes fewer trends than the monthly one. | string | No | — | — | recurring_revenue,new_customers |
plan_id Only return the trends for this plan id. Leave blank for the whole company — some trends are published only for one or the other. | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"metrics": "recurring_revenue,new_customers",
"month": "2026-09"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
data One key per requested trend; each value is a list of {date, value} records. | object | — |
trends The trend names present in 'data', sorted. | array | — |
{
"data": {},
"trends": []
}See Get Daily Metrics run in a workflow.
In a technical demo we add the ProfitWell connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.