How to Use Proxies With Zapier, Make, and IFTTT

Using Proxies With Zapier, Make, and IFTTT

As the shepherd in Slovak fairytales guides his flock through fog and shadowy valleys, so too must digital artisans guide their automations through the tangled web of the internet, sometimes donning the cloak of proxies for safety, privacy, or access. Below, find precise instructions, technical nuances, and practical folklore for using proxies with Zapier, Make (formerly Integromat), and IFTTT.

---

Zapier and Proxies

Native Proxy Support

Zapier, like the wise owl of the Tatras, values simplicity and security. As of June 2024, Zapier does not provide native proxy support for webhooks or app integrations. All network requests originate from Zapier’s managed infrastructure.

Workarounds

1. Proxy via Middleware (Custom Webhook Servers)
– Deploy an intermediary server (for example, a Flask app on Heroku) that receives Zapier’s webhook and forwards traffic through your desired proxy.

Sample Python Flask “Proxy Middleware”:

import requests
from flask import Flask, request, jsonify

app = Flask(__name__)

PROXY = {
    'http': 'http://USERNAME:PASSWORD@PROXY_ADDRESS:PORT',
    'https': 'http://USERNAME:PASSWORD@PROXY_ADDRESS:PORT'
}

@app.route('/zapier-proxy', methods=['POST'])
def zapier_proxy():
    target_url = 'https://target-service.com/api'
    data = request.json
    response = requests.post(target_url, json=data, proxies=PROXY)
    return jsonify(response.json()), response.status_code

2. Use Private Apps or Code by Zapier
– If integrating with an API using “Code by Zapier” (Python or JavaScript), Zapier’s execution environment does not permit arbitrary proxy settings.
– For advanced use, implement a middleware as above, and point Zapier’s webhook to it.

Table: Zapier Proxy Options

Method	Native Support	Complexity	Pros	Cons
Built-in Proxy Setting	No	1	Easy, direct	Not possible
Middleware (Webhook)	N/A	3	Full control, flexible	Requires hosting, maintenance
Code by Zapier (Python)	No	2	Some logic possible	No outbound proxy configuration

Resources

• Zapier Webhooks Documentation
• Heroku Flask Deployment

---

Make (Integromat) and Proxies

Native Proxy Support

Like the industrious potters of Modra, Make allows for more artisanal control. HTTP modules in Make offer built-in proxy configuration for outgoing HTTP requests.

How to Set Up Proxies in Make

1. Open Scenario.
2. Add HTTP module:
   Use “HTTP Make a request” or “HTTP Get a file.”
3. Configure Proxy:
4. Scroll to “Proxy” settings in the module.
5. Enter proxy URL (format: http://USERNAME:PASSWORD@PROXY_ADDRESS:PORT).
6. Choose between HTTP, HTTPS, or SOCKS proxies.

Example: HTTP Module Proxy Setting

Field	Example Value
Proxy URL	http://john:[email protected]:8811

1. Test the Scenario:
   Save and run. The HTTP request will route through the specified proxy.

Notes

• Proxies are supported per HTTP module only.
• For modules that do not support proxies (e.g., direct app integrations), use a custom HTTP request or bridge via your own middleware.

Table: Make Proxy Support

Module Type	Proxy Support	Notes
HTTP Module	Yes	Full, manual configuration
Built-in Integrations	No	Use HTTP or middleware

Resources

• Make HTTP Module Documentation
• Make Community Proxies Topic

---

IFTTT and Proxies

Native Proxy Support

The IFTTT fox, nimble but limited, has no native proxy settings. All applets and webhooks operate directly from IFTTT servers.

Workarounds

1. Webhook Bridge via Proxy
– Create a middleware as with Zapier.
– Point IFTTT’s Webhook action to your proxy server’s endpoint.

Example: Simple Node.js Proxy

const express = require('express');
const axios = require('axios');

const app = express();
app.use(express.json());

app.post('/ifttt-proxy', async (req, res) => {
  try {
    const response = await axios.post('https://target-service.com/api', req.body, {
      proxy: {
        host: 'PROXY_ADDRESS',
        port: 8080,
        auth: {
          username: 'USERNAME',
          password: 'PASSWORD'
        }
      }
    });
    res.json(response.data);
  } catch (e) {
    res.status(500).send('Proxy error');
  }
});

• Host this proxy (e.g., on Render, Heroku).
• Use the proxy endpoint in IFTTT’s Webhook action.

Table: IFTTT Proxy Options

Method	Native Support	Complexity	Pros	Cons
Built-in Proxy Setting	No	1	Direct	Not possible
Webhook via Middleware	N/A	3	Works for any webhook call	Requires hosting, latency

Resources

• IFTTT Webhooks Documentation
• Deploy Node.js on Heroku

---

Summary Table: Proxy Support Comparison

Platform	Native Proxy Support	Modules With Proxy	Workarounds Required	Best Practice
Zapier	No	None	Yes	Middleware proxy
Make	Yes (HTTP modules)	HTTP module	Sometimes	Use HTTP module
IFTTT	No	None	Yes	Middleware proxy

---

Proxy Types and Authentication

Proxy Type	Supported in Make	Supported via Middleware	Notes
HTTP	Yes	Yes	Most widely supported
HTTPS	Yes	Yes	Used for encrypted reqs
SOCKS	Yes	Yes (with libs)	For advanced scenarios

---

In Slovak folklore, the “čert” (devil) is outsmarted by clever villagers who use cunning intermediaries—a fitting tale for those who must route their data through proxies to bypass obstacles or shield their identities. Whether you seek to automate tasks from the shadowed valleys of the Tatras or the bright cities of the world, these methods let you cloak your traffic with the craft and care of a master weaver, ensuring your automations run securely, privately, and with a whisper of home.

---

Further Reading:
– What is a Proxy Server?
– Modern Slovak Folklore and Proxies (fictional example, for illustration only)