When an automation sends a request to another service, the request comes from one of a few Tape IP addresses (IP addresses are the numeric addresses that servers use to find each other). Some services only accept requests from known addresses. In that case, you add the Tape addresses to the allowed list of that service.
You can use these addresses for many things, including:
Letting an automation reach your accounting system behind a firewall.
Checking that a request in your server logs comes from Tape.
Note:
Tape may change these addresses. If you rely on them, an integration can stop working when they change. Avoid allow lists when you can.
Only outgoing requests use these addresses. They apply when an automation calls your service, not when your service calls Tape.
IP addresses of automations
When an automation sends a remote HTTP request, for example with Send HTTP request, it uses one of these addresses:
18.185.193.17252.29.64.18218.153.113.1952.29.124.7
Add all four to the allowed list of your service. Some features may not work if you leave one out. The addresses apply to every remote HTTP request, including Send HTTP request and Send API request.
Emails sent with Tape's sending account don't use these addresses.
Add the addresses to an allowed list
To allow Tape in your firewall or service:
Open the security or network settings of the service you call.
Find the allowed list, sometimes called an allow list or whitelist.
Add the four addresses above.
Save the change, then run the automation once with
Manual runto test the connection.
The steps differ for each service. If you aren't sure where to find the setting, ask the provider of the service.
Services Tape can't reach
Tape only calls services that are reachable on the public internet. If the address you enter points to a private or internal address, such as localhost, a server in a private network, or a metadata endpoint, Tape refuses the request. Tape looks up the IP address behind the host name and checks that address, so a host name that leads to a private address is refused too. Loopback and link-local addresses are blocked as well. You can't turn this off.
This check applies to Send HTTP request, Send API request, and the http client in Execute script.
IP address errors
The service rejects the request. Check that all four addresses are on the allowed list.
It worked before and now fails. The addresses may have changed. Check this page again. Tape can change these addresses over time. Where you can, protect the service with a secret in a header or an API key instead of relying on IP addresses.
Tape refuses the request before it is sent. The address you entered points to a private network. Use a public address.
Learn more
FAQs
Does Tape have one fixed IP address?
Does Tape have one fixed IP address?
No. Tape uses several addresses. Allow all of them.
Can I call a service in my private network?
Can I call a service in my private network?
No. Tape blocks requests to private addresses for security reasons.
Do I need to allow the addresses to receive webhooks?
Do I need to allow the addresses to receive webhooks?
No. The addresses only matter when an automation calls your service. Webhooks that other tools send to Tape need no allow list on your side. Tape accepts webhooks from any address. The secret part of the webhook address protects it.
Why does Tape not promise fixed addresses?
Why does Tape not promise fixed addresses?
The servers behind automations can change over time. Tape recommends that you don't depend on a fixed address if another way of securing your service is possible.
Are you a developer using the Tape API for automations?
Are you a developer using the Tape API for automations?
The automation API has its own documentation for developers. Go to the developer docs →
Still have questions? Find answers and get help from community experts in the Tape community →
