Mautic Deal Value Reporting: Amounts, Currency, and Totals

Start with the amount and one currency context

Deal Flow’s deal amount is an optional decimal value. When an amount is present, the interface displays it in the configured currency. The cited tracking guide recommends one consistent currency context and does not describe per-deal conversion.

Keep three states distinct as you review the data:

• Recorded amount: the deal has a decimal value that can contribute to a stage or downstream total.
• Missing amount: the optional field has not been filled in; do not silently treat missing data as a confirmed zero.
• Different currency: normalize it before combining it with values in the configured reporting currency.

Source: How to Track Deal Value in Mautic.

Read raw value by stage

The kanban board shows the amount on each deal card. Each stage header shows both the deal count and the raw total amount for the deals in that stage. These figures answer a concrete question: how much recorded value is sitting in this stage now?

Two other documented surfaces organize the same pipeline view. Stage Coverage groups deal count and value by current stage. The Pipeline Summary dashboard widget shows deal count and total value per stage. Both preserve the stage boundary; neither is described as a single grand total for the entire pipeline.

Sources: Deal Value Tracking and Sales Forecasting.

Define a pipeline total before you calculate it

A pipeline total sounds simple, but its scope changes the answer. The cited n8n recipe moves open deals to a reporting destination, so open deals are the documented status scope for that route. Before calculating, confirm that the workflow output supplies the amount and pipeline context you need, then preserve the reporting time and currency treatment beside the number.

The published product guides document per-stage totals, Stage Coverage, Pipeline Summary, and a weighted forecast. They do not document a standalone raw grand-total report. The defensible route is to calculate that number downstream:

1. Inspect the actual output. Confirm that it includes usable amount data and enough context to identify the intended pipeline.
2. Record the open-deal scope. Preserve the reporting time and the scope documented by the n8n recipe.
3. Keep currencies separate when the output identifies them. Convert values before summing them, or report a total for each available currency context.
4. Sum once at the chosen grain. If the required fields are present, add individual deal amounts rather than adding stage totals and the same deals.
5. Label the result. State that it is a downstream calculation and record which received fields produced it.

This method also prevents double counting. Stage totals are already made from deal amounts, so adding both the deals and their stage totals would count the same value twice.

Keep weighted forecast separate from raw totals

Deal Flow documents Weighted Forecast as the sum of each open deal amount multiplied by its stage probability. Closed deals are excluded from that formula.

A raw stage total describes the full recorded amount in that column. A weighted forecast applies the stage probability to each open deal before adding the results. Do not add the weighted result to the raw pipeline total: they are two views of overlapping deals, built to answer different questions.

Use the raw figure for pipeline inventory and coverage. Use the weighted figure for a probability-adjusted planning view. Review both against the underlying deals rather than presenting either as assured revenue.

Source: Sales Forecasting in Mautic.

Use the API boundary the public reference documents

The current Deal Flow API reference places its routes under /deal-flow/ and uses Mautic’s authentication. Its documented list route is:

The same reference documents deal[amount] as an optional decimal field when creating a deal. It does not publish a list-response schema, filtering beyond pagination, an amount field in that list response, or an aggregate-total response. Inspect and map the actual response from your installed version before using it as reporting input; do not build a total around fields the published reference does not specify.

Source: Deal Flow API Reference.

Calculate the total in a spreadsheet, database, or BI tool

The Deal Flow n8n guide documents a scheduled workflow that lists open deals and writes pipeline data to Google Sheets, a database, or a BI tool. The guide does not specify the returned fields, so the destination can become a reporting layer only when the actual workflow output contains the dimensions and values the calculation needs.

1. Run the documented list action on a schedule. Set the cadence to match the review that will use the number.
2. Map the data your workflow actually receives. Do not assume an undocumented REST response shape or field set.
3. Check for the required context. Continue only if the received data exposes an amount and enough pipeline and currency context for the intended total.
4. Group and sum downstream. When those fields are present, calculate the total in the sheet, database query, or BI model.
5. Expose data quality when possible. If the received data distinguishes a missing amount from zero, report the incomplete-row count beside the total.

This is a reporting recipe, not a claim that Deal Flow or its API returns a pipeline aggregate. The destination performs the grouping and arithmetic after the workflow supplies the rows available to it.

Source: How to Automate Mautic Deals with n8n.

Use a repeatable value-reporting checklist

1. Check currency first. Confirm that every amount in the total shares one reporting currency.
2. Count missing amounts when the data preserves the distinction. Separate incomplete records from genuine zero-value deals only when the received fields allow it.
3. Read stage totals. Use the board, Stage Coverage, or Pipeline Summary for the raw stage view.
4. Choose raw or weighted. Name the measure instead of calling both figures “pipeline value.”
5. Calculate grand totals downstream. Store the pipeline, scope, and run time with the result.
6. Trace the number back to deals. A reviewer should be able to identify the rows that produced it.

A short definition beside every metric does more for reporting accuracy than another chart. State the included deals, currency, calculation, and timestamp so the next reader can reproduce the result.

Sources checked September 1, 2026

• How to Track Deal Value in Mautic for the optional amount, configured currency, kanban amounts, stage totals, reports, and widgets.
• Sales Forecasting in Mautic for raw stage value, Stage Coverage, Pipeline Summary, and the weighted-forecast formula.
• Deal Flow API Reference for the documented list route, authentication context, pagination, and optional amount input.
• How to Automate Mautic Deals with n8n for the scheduled open-deal workflow and downstream destinations.

Frequently asked questions

What does a deal amount represent in Deal Flow?

A deal amount is an optional decimal value. When present, Deal Flow displays it in the configured currency.

Are stage totals the same as a pipeline total?

No. A stage header totals the deals currently in that stage. The cited sources do not document one raw grand total; define the pipeline, status, and currency scope before calculating one downstream.

Does the documented API list route return an aggregate total?

No aggregate response is documented. GET /deal-flow/{page} returns a paginated list of deals visible to the authenticated user, but the published reference does not define a list response schema or total.

How can I calculate pipeline totals outside Mautic?

The n8n guide documents pulling open deals into Google Sheets, a database, or a BI tool. If the actual workflow output includes amount, pipeline, and currency context, group and sum those fields downstream; the published sources do not specify the payload.