Zapier SQL static IP update guide

This guide explains how to update your SQL database firewall so Zapier can continue connecting using new static IP addresses. Follow the steps carefully to avoid connection failures and keep your automations running smoothly.

Why Zapier SQL connections need new IP addresses

When you connect a SQL database to Zapier, the connection is secured by firewall rules that allow traffic only from specific static IP addresses. If these IP addresses change and you do not update your firewall, your Zaps may begin to fail because the database will block the connection.

The update described in the original support notice applies to SQL integrations such as:

• MySQL
• PostgreSQL
• Microsoft SQL Server (SQL Server)

To avoid downtime, you need to add the new static IP addresses to your database firewall or access control list (ACL) before the old ones stop working.

Before you update your Zapier SQL firewall rules

Prepare the information below before changing any settings. This helps you complete the process quickly and safely.

• Identify which SQL databases are connected to Zapier.
• Confirm where your database is hosted (for example, AWS, Azure, Google Cloud, or on-premises).
• Locate your current firewall or network security group settings.
• Plan a maintenance window if changes might affect production traffic.

If other systems also depend on static IP rules, coordinate with your networking or security team so all changes are documented and approved.

How to find the new Zapier static IP addresses

The new static IP addresses you must allow are documented in the official support notice. Always rely on that source so you do not miss any required address or range.

1. Open the official support page in a browser: Zapier SQL static IP update article.
2. Review the list of new IP addresses and any region-specific details.
3. Verify whether any older IP addresses are being deprecated and when.

Keep this support page bookmarked so you can return to it if you need to audit or troubleshoot your firewall rules later.

Step-by-step: update firewall rules for Zapier

The exact steps will differ depending on your hosting provider and firewall technology, but the process follows the same pattern. Use the instructions below as a general framework and adapt them to your environment.

1. Locate your existing Zapier SQL firewall entries

First, identify the rules that currently allow connections from Zapier to your SQL database.

1. Sign in to your database host or cloud console.
2. Open the section that controls network access, such as:
   • Firewall rules
   • Security groups
   • VPC rules
   • IP access lists
3. Search for rules that contain the known static IP addresses previously assigned to Zapier.

Document these existing entries, including IP addresses, labels, and any comments. This will help you verify that the configuration is consistent after you add the new IPs.

2. Add the new Zapier static IP addresses

Next, add the new values from the official support article.

1. Return to the Zapier SQL IP update page and copy each new static IP address or range.
2. In your firewall or security group settings, add a new rule for each IP address or CIDR block listed.
3. For each rule:
   • Set the source to the new Zapier static IP or block.
   • Set the destination to your SQL database host or subnet.
   • Allow traffic only on the port used by your database (for example, 3306 for MySQL, 5432 for PostgreSQL, 1433 for SQL Server).
   • Restrict access to the minimum required protocols (typically TCP).
4. Label or comment each rule clearly, for example: “Zapier SQL integration – static IP”.

Make sure you enter every IP address noted in the support article. Missing even one can cause intermittent failures if Zapier routes connections from multiple IPs.

3. Keep or remove old Zapier IPs as instructed

The support page may specify whether you should:

• Keep existing IP addresses temporarily until a certain cutoff date, or
• Remove older addresses immediately after adding the new ones.

Follow that guidance carefully so you avoid blocking valid traffic or leaving unnecessary access open. If a deprecation date is provided, schedule a follow-up review to remove any old rules after that date passes.

4. Save and deploy your firewall changes

After entering all new rules for Zapier access, apply the configuration.

1. Review your new and existing rules to confirm there are no typos or overlapping entries.
2. Save the configuration in your firewall or cloud console.
3. Deploy or publish the rules, if required by your platform.
4. Record the changes in your internal change log or ticketing system.

This documentation is important for audits and for troubleshooting any unexpected behavior later.

Test your Zapier SQL connection

Once your firewall rules are updated and deployed, test connectivity to confirm that Zapier can still reach your database successfully.

1. Log in to your Zapier account.
2. Open a Zap that uses your SQL database connection.
3. Go to the step where the SQL app is used.
4. Click to test or reconnect the SQL account, following the prompts.
5. Run a test trigger or action that queries or writes to your database.

If the test passes and no connection errors appear, your new firewall configuration is working correctly with the updated static IP addresses.

Troubleshooting Zapier SQL firewall issues

If you see timeout or authentication errors after updating the rules, use the checklist below.

Verify firewall entries for Zapier

• Confirm every new IP address from the support article is added.
• Check for typos in IP ranges or CIDR notation.
• Ensure the correct database port is open.
• Make sure rules are set to allow rather than deny.

Check database and network configuration

• Confirm your SQL server is listening on the expected network interface.
• Verify that no additional internal firewalls or VPN rules are blocking Zapier traffic.
• If your host uses region-based access lists, confirm the region used by Zapier is allowed.

Confirm Zapier credentials and SSL settings

• In your Zapier connection settings, verify username, password, and database name.
• Check any SSL or TLS requirements on your database.
• Align SSL settings between your database configuration and Zapier connection options.

Best practices for maintaining Zapier SQL access

To keep your integrations stable and secure, build ongoing maintenance around your Zapier SQL connections.

• Subscribe to product or status updates from the support center so you hear about any future static IP changes.
• Review firewall rules regularly to remove unused access while keeping required Zapier entries active.
• Document which Zaps depend on each SQL database to make impact analysis easier when changes are needed.
• Use separate database users with least-privilege access for all automations.

For additional automation strategy or integration planning beyond basic firewall work, you can consult an external resource such as Consultevo to design robust workflows around your data.

Summary: keep Zapier SQL integrations running safely

Updating your SQL firewall rules to include the new static IP addresses is essential for keeping your Zapier database integrations online and secure. By locating your existing rules, adding every new IP, following the deprecation guidance, and thoroughly testing your connections, you can prevent interruptions to your automated workflows while maintaining tight control over database access.

Need Help With Zapier?

Work with ConsultEvo — a

Zapier Certified Solution Partner

helping teams build reliable, scalable automations that actually move the business forward.

Get Zapier Help