Connect to SQL Server on Zapier
SQL Server (MSSQL) uses custom authentication to authenticate your account on Zapier. To connect to SQL Server, you’ll need to provide a static IP address listed below.
Required authentication fields
-
Host: This is your database instance's IP address or hostname (db.example.com). It must be accessible from outside your network. Note:
localhostand127.0.0.1are not valid. Make sure it is accessible from these IPs:54.86.9.50 - Port: 1433 is the default. Change it if you're using a non-standard port.
- Database: This is the name of the database to read data from.
- Username: This is the username that will access the database. You should create a new Zapier-specific user with a limited permission scope.
Optional authentication fields
- Password: This is the password of the database to read data from.
- Schema: This is the 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 and requires a check against a list of trusted certificate authorities.
About SQL Server's app
| Are self-hosted or cloud-hosted accounts supported? | Self-hosted and cloud-hosted accounts |
|
| Is a paid SQL Server plan required? | No | |
| Are any special account permissions required? | Yes |
You must allow Zapier to connect in:
|
| Are there usage limits? | N/A | |
| Are there pagination limits? | N/A | |
| Do trigger samples use real data from your account or generic data? | Real sample data | |
| Are custom fields supported? | Yes | |
| Do update actions overwrite or append to existing data? | Overwrite existing data | |
| Is there any additional info? | Yes |