# 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:
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'@'220.127.116.11', 'integrationuser'@'18.104.22.168', 'integrationuser'@'22.214.171.124';
# Traffic to Workato
# On-premise agent
Workato's on-premise agent (OPA) 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 OPA makes an outbound connection to the Workato cloud's on-premise gateways using a small number of hostnames/IP addresses.
|Host name||IP Addresses||TCP port||Notes|
| ||126.96.36.199 |
| ||188.8.131.52 |
| ||184.108.40.206 |
|N/A||220.127.116.11||443||Deprecated 28 March 2018, not used in recent OPA versions.|
If your organization has strict outbound traffic rules, you will need to whitelist the OPA's access to the Workato cloud.
# IP Addresses
Firewall whitelists should allow outbound TCP connections from the OPA to port 443 on each address listed above.
# DNS resolution of host names
Some organizations also restrict DNS hostname resolution from the machines/networks where the OPA may run. In that case, you should ensure that the machine where OPA will be running can resolve the relevant hostnames above to their corresponding IP addresses.
# Custom APIM domains
When using custom domains for API recipes, client traffic will be routed to a distinct set of IP addresses.
# General (browsers, webhooks, API endpoints)
All other traffic to Workato:
- Browser based user interaction and webhooks at
- API endpoint requests at
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.