IntegrationsPostgreSQL
PostgreSQL + Monthwrap

Databases & warehouses reporting

PostgreSQL reporting for agencies.

Bring dated results from a client’s PostgreSQL database into the monthly report with a prepared query and definitions your agency and the data owner agree on.

AvailableDatabase credentials and saved query
Inside the monthly reportSample data
Northline Home Services

Completed jobs, prepared for reporting

Completed jobs40Total across the four example days
Reporting days4A short format example
Highest daily count12October 4 in this example
Query resultsMonthly report
Illustrative reporting view · values formatted for reading
RecordReported numbers
2026-10-018
2026-10-0211
2026-10-039
2026-10-0412

The four daily counts total 40 completed jobs. This is prepared aggregate data, not customer records or collected revenue.

Fictional query output · October 1–4, 2026 · completed jobs

PostgreSQL, at a glance.

Connect with
Database credentials and saved queryConnect with a dedicated read-only database user, preview a query returning a date followed by numeric columns, then save it on the client’s source.
Updates
Daily sync, with a manual refresh in Sources. Platform reporting delays still apply.
Earlier months
Run the saved reporting query for an earlier month, using the history retained in your database.
In your report
Dated business totals from a read-only query.

Built around your client’s questions

The most useful result may live outside a marketing platform.

Agencies working with custom booking, sales and operational systems

A client may keep completed jobs, confirmed bookings or sales outcomes in a custom system built on PostgreSQL. Those figures can answer a question that advertising and website tools cannot. Agree on the business definition first, then prepare a query that returns the relevant daily totals.

Connect the reporting database in Monthwrap, preview the query’s dates and numbers, then save it on the client’s source. That output becomes the client’s own numeric metrics. Review a known period before using the results alongside marketing activity and the work delivered.

Choose the numbers that matter

What PostgreSQL
brings to the report.

Dated business totals from a read-only query. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.

01

Dated business counts

Prepare daily totals such as confirmed appointments or completed jobs. The database owner defines which records qualify, so the report reflects the client’s process rather than an assumed marketing conversion.

02

Clearly defined value measures

A numeric column can represent booked value, invoiced value or another agreed measure. Give it the correct name and money setting; a database amount is not automatically collected revenue.

03

One measure per numeric column

The first query column supplies the date and each following column supplies a number. Name columns for the report reader, with a consistent definition across reporting periods.

04

Context beside platform results

Place the prepared business figures beside advertising, analytics or CRM sections. Explain the relationship without claiming that a database total is automatically attributed to a particular campaign.

For your next client report

Report beyond a standard CRM

Use a prepared aggregate from the client’s custom operations system when it holds the authoritative job or booking result. Keep the meaning consistent with the client’s internal reporting.

Arrange the report in your own layout

Read it from the client’s side

See the complete
local growth report.

A full fictional agency report, with the work delivered, the numbers behind it and the plan for next month. Use its structure to plan your own mix of sources and client results.

Open the sample report

Make the connection

From PostgreSQL
to the right client.

Connect with a dedicated read-only database user, preview a query returning a date followed by numeric columns, then save it on the client’s source.

How to build monthly reports from a PostgreSQL database
Connection methodDatabase credentials and saved queryAvailabilityAvailableYour connected account’s API permissions and plan apply.
  1. 01

    Prepare access with the data owner

    Ask the database administrator for a dedicated read-only user and the host, port, database and SSL details. The reporting host must be reachable through the access rules the owner approves.

  2. 02

    Connect the reporting database

    An owner or admin enters the connection details in the workspace. Monthwrap checks access before storing the credentials. If the database uses an allowlist, give the administrator the connection address shown in the form.

  3. 03

    Preview and save the client’s query

    Prepare one SELECT, or WITH followed by SELECT, returning dates and numeric columns. Use the reporting start and end dates, preview the totals and resolve any format problems, then save the query on the client source before syncing.

Know what each
number means.

Aggregate results, not a database browser

This route is for dated numeric reporting. It does not import arbitrary customer records, expose a full database explorer or support a query-generated top-products table in the current reporting contract.

Definitions and access need an owner

Use restricted reporting access and agree the date, status and value rules with the client. Private-network-only hosts are not supported by this connection; the data owner should decide the appropriate access arrangement.

Before you connect

A few useful
answers.

Can I check the query before saving it?

Yes. Preview the query for a chosen date range to see sample rows, the resulting metric names and any format problems. A preview does not save the query or sync the client’s numbers; save the checked query on the client source before syncing.

What should the query return?

Return a date first, then numeric columns with readable names. Rows for the same day and metric are added together. Prefer a daily aggregate, and use the supplied start and end dates to keep the reporting period explicit.

Can this run any SQL query?

No. The route accepts a single read-only SELECT or WITH query, with a 30-second limit and up to 5,000 returned rows. It is intended for compact reporting results, not data editing, migrations or unrestricted database analysis.

Start with your next client report

The data has a source.
The story has your name.

Bring your sources together, choose your layout and add the context your client needs.

Start free trial

14-day free trial. No card needed.

Make yourself comfortableMore about cookies and browser storage