# IP whitelists
IP whitelisting allows you to ensure traffic to/from Workato is not hijacked by a malicious website.
# Traffic from Workato
All traffic from Workato comes through the following IP addresses:
- 52.5.142.59
- 34.226.132.221
- 52.54.43.157
You can add these IP addresses to your application/firewall whitelist. Add all three IP addresses to the whitelist to ensure continuous access.
# Example whitelist configuration
If you have a recipe that accesses a MySQL server running on an Amazon EC2 machine, with a special user called integrationuser, you can run the following SQL command on your database to whitelist the Workato IP addresses.
GRANT ALL ON db1.*
TO 'integrationuser'@'52.5.142.59',
'integrationuser'@'34.226.132.221',
'integrationuser'@'52.54.43.157';
# Traffic to Workato
# On-premise agent
Workato's on-premise agent provides a secure way for Workato to selectively access customer-authorized on-prem apps, databases and folders without having to open inbound ‘ports’ in the corporate firewall. The on-premise agent makes an outbound connection to Workato via an on-premise gateway.
If your organization has strict outbound traffic rules, you should whitelist the on-premise gateway IP address:
- 34.192.94.13
- 34.195.128.7
- 34.226.84.130
- 52.206.58.244 (Deprecated on 28 March 2018)
# General (browsers, webhooks, API endpoints)
All other traffic to Workato:
- Browser based user interaction and webhooks at
www.workato.com - API endpoint requests at
apim.workato.com
may be served by a different set of IP addresses, distinct from IP addresses mentioned in the previous sections. This set may expand and contract based on overall platform utilization, so it is not completely static.