Resources · Make integration

PostgreSQL Make integrationAutomate PostgreSQL with Make.

Your database can take in new rows and hand back answers while you work elsewhere. The PostgreSQL Make integration gives you 6 modules: 5 actions and 1 search. This guide is for ops and product people who own a table, and it walks you from the connection to a first working scenario.

Try the PostgreSQL integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PostgreSQL Make integration do for you?

It lets a Make scenario (the automation you build in Make, a chain of modules) read and write your PostgreSQL tables without a line of glue code. Each module is one brick of that chain: here, an action that changes rows or a search that fetches them.

A clean intake table. A form tool or a shop sends a new record, and Insert row into a table stores it as one row. Every item that flows through is called a bundle: one order, one lead, one row.

Records that stay current. When a deal changes stage in your CRM, Update row(s) in a table rewrites the matching rows, so reports built on the database show the latest status.

Data pushed out to the team. Select row(s) from a table pulls rows, and the next module in the scenario sends them to a spreadsheet or a chat. For logic that already lives in the database, Execute a function calls it by name.

What this app does not offer: a trigger. Nothing in PostgreSQL wakes Make up, so a scenario starts on another app or on a schedule. There is also no generic API call module. If you are weighing tools, the n8n vs Make comparison covers the choice, since PostgreSQL often has an n8n node too. For the basics of the editor, see the Make training, and when a run fails, keep Make troubleshooting close.

Connect

How do you connect PostgreSQL to Make?

  1. 01

    Open the connection window

    In your scenario, add any PostgreSQL module and click Create a connection. A connection is your database account linked to Make once, then reused by every PostgreSQL module. The Connection name field is optional, but a clear name helps when you have several databases.

  2. 02

    Fill in the database details

    Enter the Host, the Port (a number between 1 and 65535), the Database, your User name and Password. You can also set Client Encoding, Encrypt, Keep-Alive and its delay in milliseconds if your setup needs them.

  3. 03

    Save and confirm

    Click Save. If Make asks you to authenticate or confirm access, do it in the same window. Once the connection is saved, the module can list the tables it is allowed to see, so you pick them instead of typing names.

First scenario

Your first scenario with PostgreSQL

GoalWhen a new order arrives in another app, Make stores it as a fresh row in your PostgreSQL orders table.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where orders come in (your shop or form tool) and its module that watches new orders.

  2. 02

    Add the PostgreSQL action

    Click the + on the right of that first module, search for PostgreSQL and choose Insert row into a table. Select your connection, or create it as shown above.

  3. 03

    Map the order to columns

    Pick the orders table from the list Make shows. For each column, map a value from the previous module: the customer email in one column, the amount in another.

  4. 04

    Test with Run once

    Click Run once, then place a test order. Read the bundles each module received, and check the new row in your database.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on each bundle counts as one operation on your plan.

Modules

What the PostgreSQL modules do

PostgreSQL gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PostgreSQL1

Delete row(s) from a table

Action

Removes rows from a table you choose, which keeps staging tables or expired records from piling up. Like the update module, its name allows for several rows in a single run.

When to use it
a customer cancels their account in another tool and their pending rows should go.
Watch out
a deleted row does not come back, so run it once against a test table before pointing it at production.
PostgreSQL2

Execute a function

Action

Calls a function already defined in your database, so the business rules your developers wrote stay in one place and Make simply triggers them. That is most likely why the doc asks for read access to the routines and parameters tables.

When to use it
an invoice is approved and a database function should recalculate the customer balance.
Watch out
if it misbehaves, first check that the connected user can read those two tables.
PostgreSQL3

Execute a query (advanced)

Action

Gives you the flexible route when the table modules are too narrow, by running a query you write yourself. The label says advanced for a reason: you need to be comfortable with SQL.

When to use it
you need a join across two tables or a statement none of the other five modules covers.
Watch out
what the query does is entirely up to you, so test it with Run once on sample data.
PostgreSQL4

Insert row into a table

Action

Adds one new row per bundle, turning whatever arrives from another app into a proper database record. Make lists the table columns once the connection works, so you map values instead of typing names.

When to use it
a lead fills in a signup form and you want it stored for reporting.
Watch out
if the same event reaches Make twice, you get two rows, so decide how your table handles duplicates.
PostgreSQL5

Update row(s) in a table

Action

Rewrites existing rows so the database reflects what just changed in another tool. Note the plural in its name: one run can touch several rows at once.

When to use it
a support ticket is closed in your helpdesk and the matching record should switch to resolved.
Watch out
since one run can change several rows, open the table after your first Run once and confirm only the expected records moved.
PostgreSQL6

Select row(s) from a table

Search

Fetches rows and hands them to the next module, which is how data leaves PostgreSQL for a sheet, an email or a chat. As a search, it can return zero, one or many bundles.

When to use it
a sales rep asks for the open orders of a client and a later module formats the list.
Watch out
every row found becomes its own bundle, and each module after it runs once per bundle, counting operations.
Need help

Need help automating PostgreSQL with Make?

A person reads every message.

FAQ

PostgreSQL Make integration: common questions

01Is the PostgreSQL Make integration free?
Yes. PostgreSQL is a standard app, available from the Free plan. That plan gives you 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations: one module running on one bundle. A scenario that selects many rows uses operations quickly, so watch that module first.
02What do you need to connect PostgreSQL to Make?
You need the database host, the port (between 1 and 65535), the database name, a user name and its password. Optional settings cover client encoding, encryption and TCP keep-alive. The user you connect with needs read access to the information_schema routines and parameters tables, a prerequisite listed in the Make doc. If a firewall protects the server, allow traffic from make.com addresses: Make connects from servers with valid PTR records, so a rule on that domain works. Then click Save and confirm access if Make asks.
03Does the PostgreSQL Make integration react in real time?
No, because PostgreSQL has no trigger module in Make: nothing in the database tells Make that a row changed. You start the scenario another way. Either another app opens the flow, for example a form or a shop that sends a new order, and PostgreSQL modules follow. Or you put Select row(s) from a table first and let the scenario run on its schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute.
04What if a PostgreSQL module is missing in Make?
Start with Execute a query (advanced). Its name tells you it runs a query you write, which covers most cases the five table modules do not reach, such as a join. If the logic already exists in the database, Execute a function calls it directly. This app has no Make an API Call module, so there is no generic fallback beyond these two. If neither fits, another app in your stack may hold the same data, or the Hack'celeration team can look at the setup with you.
05Should you use Make or n8n for PostgreSQL?
It depends on where the rest of your automations already live. PostgreSQL often has a node in n8n as well as its 6 modules in Make, so the database side rarely decides the question. On the Make side, the connection is set up once and reused by every module, and the visual editor shows each bundle after Run once, which helps when you are new to scenarios. Compare both tools on your other apps and your team's habits rather than on this single database, and pick the one where your full chain fits.
Same platform

Other docs you might need on this stack.

Browse all integrations