PostgreSQL and Zapier connect to automate your database work. You can trigger actions when new rows are added and create or update rows in tables.
Available on plans:
Free
Pro
Team
Enterprise
Prerequisites
To use the PostgreSQL app on Zapier, you must have:
- A PostgreSQL database that is accessible from outside your network (not
localhost
or127.0.0.1
). - Network configuration to allow connections from Zapier's static IP address (
54.86.9.50
). - Configure your firewall to allow incoming connections on your PostgreSQL, which is
5432
by default. If you are using a custom port, be sure to open that specific port instead. - In your
postgresql.conf
file, configure the server to listen to connect from Zapier's IP address. Change the listening_addresses parameters to54.86.9.50
. - A dedicated PostgreSQL user account with limited permissions for Zapier to use.
- Appropriate database permissions granted to the Zapier user (SELECT, INSERT, UPDATE as needed for your use case).
- A paid Zapier plan. PostgreSQL is a premium app on Zapier.
Cloud and services-specific requirements
- If using cloud providers like AWS RDS/EC2, security groups must allow access from
54.86.9.50/32
. - If using Google Cloud Platform CloudSQL, the IP (54.86.9.50) must be added to "Authorised networks".
- For Neon PostgreSQL specifically, a special password format including the endpoint ID (
endpoint=[endpoint_id]$[password]
). Learn more from Neo's documentation.
Connect PostgreSQL to Zapier
To create an app connection to PostgreSQL on Zapier:
- Go to the Apps page.
- Click + Add connection.
- A new dialog box will appear. Search for and select PostgreSQL.
- Click Add connection.
- A Connect an Account page will open in a browser tab or window.
- Complete the following fields:
- Host: Enter your database instance's IP address or hostname (e.g., db.example.com).
- Port: Enter your database port (5432 is the default).
- Database: Enter your database name.
- Schema: Enter your schema name inside PostgreSQL to search for tables.
- Username: Enter your database username.
- Password: Enter your database password.
- Enforce encryption: Select from the dropdown menu to enforce SSL/TTL for encrypting communication between Zapier and your database.
- SSL client certificate: Enter your SSL client certificate if your server requires client validation for SSL.
- SSL private key: Enter your SSL private key if your server requires client validation for SSL.
- SSL CA bundle: Enter your PEM-formatted certificate chain file (Certificate Authority file or CA Bundle).
- Click Yes, Continue to PostgreSQL.
Your PostgreSQL account is now successfully connected to Zapier.
About PostgreSQL's app
Triggers, searches, and actions
Triggers
-
Triggers
- New Column (Polling) - Triggers when you add a new column.
- New Row (Custom Query) (Polling) - Triggers when new rows are returned from a custom query that you provide.
- New or Updated Row (Polling) - Triggers when a new row is added or modified.
- New Row (Polling) - Triggers when you add a new row.
- New Table (Polling) - Triggers when you add a new table.
Searches
-
Searches
- Find Rows via Custom Query - Finds multiple rows in a table via a custom query you control.
- Find Row - Finds a row in a table via a lookup column.
- Find Row via Custom Query - Finds a row in a table via a custom query you control.
Actions
-
Actions
- Update Row - Updates an existing row.
- New Row - Adds a new row.
Limitations
- The database instance must be accessible from outside your network with proper firewall configuration.
- Column names with uppercase characters will cause errors as they are converted to lowercase by default; you must wrap column names in double quotes in custom queries.
- The "New Row" trigger captures only the 50 most recent rows per polling interval (5-15 minutes depending on plan), so more than 50 new rows in one interval will result in data loss.
- Some application require Static UP pool types, and if they are not configured correctly, it can cause authentication failures.
Templates
View all of PostgreSQL's templates.
Use cases
Additional PostgreSQL resources
0 comments
Article is closed for comments.