Two Minute Reports Logo
Connectors

PostgreSQL

Connect PostgreSQL to Google Sheets or Looker Studio

Two Minute Reports' PostgreSQL connector lets you access and analyze your data directly in Google Sheets or Looker Studio. Build custom reports, monitor key metrics, and make data-driven decisions - all without writing any code.

What you can report on

  • Any custom data stored in your PostgreSQL database
  • Sales, orders, and transactional records from your systems
  • User activity and product engagement metrics
  • Operational and logistics data
  • Custom KPIs and business metrics specific to your product

Prerequisites

  • A PostgreSQL server accessible over the network
  • Database host, port, username, and password
  • A database user with SELECT permissions on the tables you want to query
  • TMR's server IPs whitelisted in your database firewall (see IP whitelisting below)

How to create a connection

  1. Go to https://hub.twominutereports.com/connections
  2. Click New Connection to create a connection
  3. Select PostgreSQL from the list of available connectors

  1. Name the connection and authorize with your account credentials

After creating a connection:

  1. Enable the accounts you want to use from the available options

Important: Only enabled accounts can fetch data and count toward your plan usage. You can enable or disable accounts at any time in the hub to manage your plan usage efficiently.

How to get PostgreSQL data into your reports

To pull PostgreSQL data into Google Sheets:

  1. In the TMR sidebar, go to Data Queries and click Add
  2. Select the accounts you want to analyze (can select multiple)
  3. Choose your metrics and dimensions from available options
  4. Select the date range for your analysis
  5. Configure sorting and filtering options as needed
  6. Click Run Query to populate the data into Google Sheets

Dynamic dates

When your query config contains a fixed date range in the SQL WHERE clause, you have to manually update it every time. Instead, use the @startDate and @endDate parameters — TMR replaces them with the date range selected in the report at query time, so the SQL always fetches only the relevant data.

Example — static query:

SELECT * FROM orders
WHERE order_date BETWEEN '2024-01-01' AND '2024-01-31'

Same query with dynamic dates:

SELECT * FROM orders
WHERE order_date BETWEEN @startDate AND @endDate

When the report refreshes, TMR substitutes @startDate and @endDate with the selected date range. This keeps reports fast because the database returns only the requested rows instead of the full table.

IP whitelisting

TMR connects to your PostgreSQL database from these fixed IP addresses. Add all five to your pg_hba.conf before creating a connection:

49.13.34.182
5.75.217.220
116.203.164.91
95.216.182.151
91.99.28.86

Add the following lines to your pg_hba.conf file (replace your_database and your_user):

host  your_database  your_user  49.13.34.182/32   md5
host  your_database  your_user  5.75.217.220/32   md5
host  your_database  your_user  116.203.164.91/32 md5
host  your_database  your_user  95.216.182.151/32 md5
host  your_database  your_user  91.99.28.86/32    md5

After editing, reload PostgreSQL: pg_ctlcluster <version> main reload

Copyright © 2026