IP2Location Integrations

If you're storing IPs in a PostgreSQL table, this integration can scan them for geolocation data and record the results on another. Once active, it will respond to every new row you add on PostgreSQL, automatically sending the IP information to IP2Location and storing the results on a different PostgreSQL table.

Note: Record the resulting IP location data in a different table from the one that triggers this Zap so you don't cause a loop.

How this PostgreSQL-IP2Location-PostgreSQL integration works

1. A new row is added to a PostgreSQL table
2. Zapier sends an IP from it to IP2Location for geolocation query
3. Zapier adds the results to another PostgreSQL table row

Apps involved

• PostgreSQL
• IP2Location

Need to know more about the IPs you're logging? Set up this automation, and Zapier will do the digging for you. It will trigger with every new document you add to MongoDB, sending the IP information to IP2Location for processing. The results will then automatically be logged in a new MongoDB document, saving you the trouble of looking them up yourself.

Note: Record the resulting IP location data in a different document from the one that triggers this Zap so you don't cause a loop.

How this MongoDB-IP2Location-MongoDB integration works

1. A new document is added to MongoDB
2. Zapier sends an IP from it to IP2Location for geolocation query.
3. Zapier adds the results to another MongoDB collection.

Apps involved

• MongoDB
• IP2Location

Zapier lets you easily query geolocation data from a database so you don't have to search for it yourself. This automation will trigger with every new row you add to a SQL Server table, automatically looking up IP information via IP2Location and copying the results to a new row on SQL Server.

Note: Record the resulting IP location data in a different table from the one that triggers this Zap so you don't cause a loop.

How this SQL Server-IP2Location-SQL Server integration works

1. A new row is added to a SQL Server table
2. Zapier sends an IP from it to IP2Location for geolocation query
3. Zapier adds the results to another SQL Server table row

Apps involved

• SQL Server
• IP2Location

Tired of searching for that IP information yourself? Set up this integration, and we'll do it for you. From then on, whenever you add a new row to a specific MySQL table, Zapier will pass the data along to IP2Location, adding the returned response to a new row on a different MySQL table.

Note: Record the resulting IP location data in a different table from the one that triggers this Zap so you don't cause a loop.

How this MySQL-IP2Location-MySQL integration works

1. A new row is added to a MySQL table
2. Zapier sends an IP from it to IP2Location for geolocation query
3. Zapier adds the results to another MySQL table row

Apps involved

• MySQL
• IP2Location

You never have to look up IP data manually again. Set up this automation, queue up messages on Amazon SQS, and we'll do the rest. Whenever we detect a new message, the IP information will be passed through IP2Location, and Zapier will then log the resulting geolocation data in a message on another queue.

How this Amazon SQS-IP2Location-Amazon SQS integration works

1. A new message is added to an Amazon SQS queue
2. Zapier sends an IP from it to IP2Location for geolocation query
3. Zapier adds the results to another message in an Amazon SQS queue

Apps involved

• Amazon SQS
• IP2Location