SQL Server and Zapier connect to automate your database work. You can trigger actions when new rows or columns are added and create or update rows in your tables.
Available on plans:
Free
Pro
Team
Enterprise
Prerequisites
To use the SQL Server app on Zapier, you must have:
- A SQL Server database instance, version 2012 or newer, accessible from outside your network. Be aware that SQL Server 2008 R2, and Azure SQL may have compatibility issues.
- The following network and firewall configurations are also necessary:
- Network configuration allowing external connections with the database host accessible via IP address or hostname.
Localhostand127.0.0.1are not valid. - Firewall configuration to allow connections from Zapier's IP address (
54.86.9.50) on the appropriate port (default port1433).
- Network configuration allowing external connections with the database host accessible via IP address or hostname.
- Special account permissions allowing Zapier to connect at the network level, server level, and SQL Server level.
- Optional: A dedicated database user account with limited permission scope specifically for Zapier access (recommended for security).
- A paid Zapier account. SQL Server is a premium app on Zapier.
Connect SQL Server to Zapier
To create an app connection to SQL Server on Zapier:
- Go to the Apps page.
- Click + Add connection.
- A new dialog box will appear. Search for and select SQL Server.
- Click Add connection.
- A Connect an Account page will open in a browser tab or window.
- Complete the following fields:
- Required fields:
-
Host: Enter your database instance's IP address or hostname (e.g., db.example.com). It must be accessible from outside your network to these IPs
54.86.9.50. -
Port: Enter your database port (
1433is the default). - Database: Enter your database name to read data from.
- Username: Enter your database username (create a new Zapier-specific user with limited permission scope).
-
Host: Enter your database instance's IP address or hostname (e.g., db.example.com). It must be accessible from outside your network to these IPs
- Optional fields:
- Password: Enter your database password.
- Schema: Enter your schema that the selected database resides in.
- Enforce encryption: Select from the dropdown menu to enforce SSL/TTL for encrypting communication between Zapier and your database.
- Allow self-signed certificates: Select from the dropdown menu if you're connecting to a database that uses self-signed certificates.
- Required fields:
- Click Yes, Continue to SQL Server.
Your SQL Server account is now successfully connected to Zapier.
About SQL Server's app
Triggers, searches, and actions
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.
- New or Updated Row (Custom Query) (Polling) - Triggers when new or updated rows are returned from a custom query that you provide. Uses row contents for deduplication.
Searches
- Find Multiple 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
- Create Custom Query - Executes a custom query.
- Update Row - Updates an existing row.
- New Row - Adds a new row.
Limitations
- Only supports SQL Server version 2012 or newer, with SQL Server 2005 being not compatible and SQL Server 2008/2008 R2/Azure being only maybe compatible.
- Your database must be accessible from Zapier's static IP address 54.86.9.50.
- Each poll captures only the 50 most recent rows, meaning if more than 50 rows are added in a polling interval, some data will be lost.
- Only UTF-8 encoding is supported - databases must use UTF-8 encoding to prevent garbled or incorrectly converted data.
- DateTime column type can cause conversion errors when converting text into DateTimes. It's recommended to use
datetype ordatetimeoffsettype instead. - When a non-default, or named, SQL Server instance is used, some users may experience unknown connection timeouts. This happens because SQL Server changes the communication port but relies on SQL Server browser to relay messages through the default port,
1433. To avoid this issue, Zapier recommends using the default SQL instance. If that's not possible you must ensure that TCP communication is enabled and a static port is set for the service. - Password encryption issues can cause login failures. Long alphanumeric passwords are recommended to avoid connection string encryption problems. You cancreate long alphanumeric passwords using this tool.
- New or Updated Row trigger requires ORDER BY clause with a date/time field to properly detect updates.
Templates
View all of SQL Server's templates.
0 comments
Article is closed for comments.