Resources · n8n integration

ProfitWell n8n integrationAutomate ProfitWell with n8n.

Closing the month should not mean copying numbers by hand. The ProfitWell n8n integration exposes 2 resources and 2 operations: your company account settings, and a financial metric broken down by day. Built for teams that report on subscription numbers on a schedule.

Try the ProfitWell integration on n8nSee the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the ProfitWell n8n integration actually cover?

The ProfitWell node plugs ProfitWell into any workflow you build in n8n. It reads two things: the account settings of your ProfitWell company, and one financial metric, returned broken down by day for either the current month or the last. Both operations are reads, so a workflow starts by pulling numbers and then decides where they go.

Monthly reporting without the copy and paste. A Schedule Trigger fires once the month is closed, the node runs metric.get with Type on Monthly, and the result lands in a tab through Google Sheets. The month you ask for is written as YYYY-MM, and it has to be the current one or the one before.

A short recap for the team channel. On Daily, the metric comes back broken down by day, which is enough to post a morning summary into Slack without anyone opening ProfitWell. Choose the trends you want in Metrics, or leave the field alone and the node returns all of them.

Feeding a dashboard you already watch. The same scheduled call gives Grafana a series to plot next to the rest of your operational numbers, and the Plan Name or ID option narrows the answer to a single plan when you track one product line apart from the others.

When the node is not the right tool: anything outside the operations it exposes goes through the HTTP Request node, which calls any endpoint of the ProfitWell API and reuses the same credential through its predefined authentication. No second token to manage.

Two things to plan around before you build. Month accepts only the current or the previous month, so a workflow that backfills a year of history is not a single node. And ProfitWell has no trigger node in n8n, which means the workflow starts with a Schedule Trigger on a fixed interval, an n8n Webhook called by a third-party service, or another tool's trigger. If you are still comparing platforms, the n8n review is the honest version, and the n8n training covers building the workflow itself.

Connect

How do you connect ProfitWell to n8n?

  1. 01

    Generate the API token in ProfitWell

    You need a ProfitWell account first. Inside it, open Account Settings, go to Integrations and select ProfitWell API. That screen is where the API token is issued. Copy it before you leave the page, because the token is the only thing n8n will ask for on the ProfitWell side.

  2. 02

    Create the credential in n8n

    In n8n, open the Credentials menu and add a ProfitWell credential, which is the stored login n8n reuses instead of asking you for the token in every node. Paste the value into the API Token field and save. A credential is created once and shows up in the dropdown of every ProfitWell node you add afterwards, on n8n Cloud or on a self-hosted instance.

  3. 03

    Run a first read to confirm it works

    Drop a ProfitWell node into a workflow, pick the credential in its list, and select the Company resource with company.getSetting. It takes no parameters, so a single execution tells you whether the token is accepted. Once it returns, swap the resource to Metric and start filling in the real call.

Actions

What can the ProfitWell node do?

The ProfitWell node exposes 2 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetGet Settings
Company✓
Metric✓

Company

1 operation
01

Get settings for your company

company.getSetting

What you see in n8n

Notes & use cases

Reads the ProfitWell account settings of your company. The operation takes no parameters at all, so selecting the credential and the Company resource is the whole configuration.

Use cases
the fastest way to confirm a fresh API token is accepted before you wire anything else, and a useful first node in a longer workflow that reads the account settings once and carries them alongside the metrics pulled further down the canvas.

Metric

1 operation
02

Get a metric

metric.get

What you see in n8n

Notes & use cases

Retrieves a financial metric broken down by day, for the current month or the last.

Key parameters

  • Type: Daily returns it broken down by day; Monthly returns all monthly financial metric for your company.
  • Month: written as YYYY-MM, current or previous month only.
  • Metrics: in Options, the metric trends to return, such as recurring_revenue or churned_customers. Default returns all.
  • Plan Name or ID: in Options, limits the metric to one plan. Pick it from the list or use an expression like {{ $json.field }}.
  • Simplify: turned on, it hands back a simplified version of the response instead of the raw data the API would otherwise return.
Use cases
a scheduled pull that writes one row per closed month into a reporting sheet.
Need help

Need help automating ProfitWell with n8n?

A person reads every message.

FAQ

ProfitWell and n8n, the questions that come next

01Is the ProfitWell n8n integration free?
Yes on the n8n side. The ProfitWell node ships with n8n, so there is nothing to install and nothing extra to pay for it, whether you run n8n Cloud or a self-hosted instance under the Community Edition and its Sustainable Use licence. A workflow behaves the same way in both setups, so you can prototype on one and move it to the other without rewriting the nodes. What a ProfitWell account itself costs is a separate question and not one this page answers. The only thing you need on that side is an account and an API token.
02What credentials does the ProfitWell node need?
One API token. In ProfitWell, open Account Settings, then Integrations, then select ProfitWell API to get it. In n8n you create a ProfitWell credential from the Credentials menu, paste the value into the API Token field, and save. That credential is stored once and reused across every workflow, so a second ProfitWell node just picks it from a dropdown instead of asking again. There is no authentication selector on the node, so the token is the only thing to set up. And since the same credential also works with the HTTP Request node through its predefined authentication, you never need a second one.
03What are the limits of the ProfitWell node in n8n?
The node covers 2 operations across 2 resources: the company account settings, and a financial metric. The Month parameter is the one real constraint to design around, because it accepts the current or the previous month only, and the format has to be YYYY-MM. So a workflow that rebuilds a long history is a sequence of runs over time, not one call. For anything the node does not expose, the HTTP Request node calls any endpoint of the ProfitWell API and reuses the same credential through its predefined authentication, which keeps the workflow on a single login.
04Can a ProfitWell event trigger an n8n workflow in real time?
No, because ProfitWell has no trigger node in n8n. A workflow that involves ProfitWell starts somewhere else and calls the node when it needs numbers. Three usual starting points: a Schedule Trigger that fires on a fixed interval, which fits monthly and daily reporting well, an n8n Webhook that a third-party service calls, or the trigger of another tool already in your stack. In practice the Schedule Trigger covers most of it here, since the metric is returned broken down by day and the useful window is the current month or the last.
05n8n or Make for ProfitWell?
It depends on four things, and price is only one of them. Make is a hosted automation platform with no self-hosting option, billed per operation, so the cost follows your volume. n8n can run on your own infrastructure or on n8n Cloud, which matters when subscription and revenue data is not supposed to leave your environment. The visual logic differs too: both are visual builders, but they do not model branches and loops the same way, and that shows up once a workflow grows. Try the ProfitWell flow you actually need on both before committing to either.
Same platform

Other docs you might need on this stack.

Browse all integrations