IntegrationsMySQL
MySQL + Monthwrap

Databases & warehouses reporting

MySQL reporting for agencies.

Use a saved read-only query to bring dated numeric results from MySQL or MariaDB into Monthwrap, with definitions your agency and client agree on.

AvailableDatabase credentials and saved query
Inside the monthly reportSample data
Northside Systems / Cedar Home Services

Completed work, straight from the system

Jobs completed56Total across the four sample days
Days returned4One dated result per row
SourceSaved queryRead-only MySQL reporting access
Query resultsMonthly report
Illustrative reporting view · values formatted for reading
RecordReported numbers
2026-10-0112 jobs
2026-10-0215 jobs
2026-10-0311 jobs
2026-10-0418 jobs

The example query counts completed jobs. It does not import individual job records or attribute those jobs to a marketing channel.

Fictional query result · four sample days · completed jobs

MySQL, at a glance.

Connect with
Database credentials and saved queryConnect with read-only database credentials, preview a query returning dates and numbers, then save it on the client’s reporting 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 operational totals from MySQL or MariaDB.

Built around your client’s questions

The business already knows the outcome. Report that definition.

For agencies reporting on custom applications, booking systems and client databases.

A custom application may hold the client’s most useful results: completed jobs, attended consultations or approved orders. Those definitions often depend on internal status fields that an advertising platform cannot see. A saved database query lets your agency use the agreed business result without turning the report into a copy of the application.

Monthwrap’s MySQL route also supports MariaDB. Connect the database, preview a query returning a date and named numeric columns, then save it on the client’s source. After syncing, those columns become custom report measures. Check a known period before placing the results beside marketing activity and the work your agency delivered.

Choose the numbers that matter

What MySQL
brings to the report.

Dated operational totals from MySQL or MariaDB. Choose the relevant figures, add comparisons where the data supports them, and explain what changed.

01

Confirmed operational counts

Count the events that match the client’s definition, such as jobs with a completed status. Keep requested, booked, canceled and completed events distinct in the query and report labels.

02

Defined monetary results

Return an agreed amount for each day and configure the metric’s money settings. Explain whether it represents orders, invoices or collected payments instead of applying a generic revenue label.

03

Several measures from one query

A query can return multiple numeric columns after the date. Use readable column names so the resulting report measures communicate their meaning without exposing internal database terminology.

04

A consistent reporting period

Use the supplied start and end dates to select the intended period. Return daily results at a suitable scale; repeated rows for the same day are added, so accidental joins can inflate totals.

For your next client report

A service business with a custom system

Report completed jobs from the operational database beside calls and inquiries from other sources. The comparison helps explain follow-up without claiming that every completed job came from a recent campaign.

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 MySQL
to the right client.

Connect with read-only database credentials, preview a query returning dates and numbers, then save it on the client’s reporting source.

Connection methodDatabase credentials and saved queryAvailabilityAvailableYour connected account’s API permissions and plan apply.
  1. 01

    Arrange restricted reporting access

    Ask the database owner for a dedicated read-only account limited to the required tables or views. Use encrypted transport and a reporting endpoint that can be reached from Monthwrap; private-network hosts are not supported.

  2. 02

    Configure the approved connection

    An owner or admin enters the host, port, database and reporting credentials in the workspace. The database administrator should restrict network access to the connection address shown there, rather than open the database broadly.

  3. 03

    Preview and save the query

    Return the day first and numeric columns after it. Test a known period, resolve reported problems and save the query on the correct client source before syncing its numbers.

Know what each
number means.

Numeric reporting, not a full database import

This route supplies dated measures. It does not import contact records, arbitrary text columns or a complete operational database, and it does not currently provide a second query for a ranked text-and-number table.

Keep queries focused

The connection accepts one read query, with a 30-second limit and at most 5,000 returned rows. Aggregate close to the source and validate joins so the result is both manageable and correct.

Before you connect

A few useful
answers.

Does this support MariaDB too?

Yes. The MySQL database route also supports MariaDB. Use the client’s approved reporting credentials and verify a representative query, rather than assuming every database-specific expression behaves identically.

Does Monthwrap need permission to change the database?

Use a dedicated read-only database account. The connector accepts a single read query and uses a read-only transaction, but database permissions should still limit the account to the reporting data it needs.

Can I connect a database that is only on a private network?

The current route refuses private-network hosts. Ask the database owner whether an appropriately restricted, externally reachable reporting endpoint is available; do not expose the operational database broadly just to enable reporting.

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