Resources · Make integration

HTTP Agent Make integrationAutomate HTTP Agent with Make.

Need Make to reach a system that sits behind your On-prem agent? The HTTP Agent Make integration gives you 3 action modules for that, one per way of signing in. This guide shows how to connect it and run a first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the HTTP Agent integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the HTTP Agent Make integration let you automate?

HTTP Agent is a built-in Make app that sends HTTP or HTTPS requests to a connected system configured in your On-prem agent. In a scenario (the automation you build in Make, a chain of modules), it becomes the step that talks to that system, with or without credentials.

Call an internal service that asks for an API key. A form tool or a CRM hands over a new record, and Make an API Key Auth Request passes it on with the key placed where the service expects it, as a header or as a query parameter.

Reach an older tool that still uses a username and a password. Make a Basic Auth Request signs in with the account of that tool, so a scenario can feed it without anyone copying data by hand.

Reach an internal address that needs no sign-in at all. Make a Request covers that case: you only pick the connected system.

Two limits to know first. The app is reserved to Make's Enterprise plan, and it has no trigger, so another app or Make's own schedule has to start the scenario. If you are still weighing the platform, the Make review and the n8n vs Make comparison are good next reads, and the Make agency can help set up the On-prem side.

Connect

How do you connect HTTP Agent to Make?

  1. 01

    Open the connection window

    In your Make account, add any HTTP Agent module to a scenario and click Create a connection. A connection is the link between Make and your system; every HTTP Agent module can reuse it later.

  2. 02

    Name it and pick the system

    Give it a label in Connection name if you like (this is optional), then choose the target in the Connected System dropdown. The list shows the systems already set up in your On-prem agent.

  3. 03

    Add the credentials and save

    What comes next depends on the module. API key: fill API Key, Placement and API Key Parameter Name. Basic auth: Username and Password. Make a Request asks for nothing more. Then click Save.

First scenario

Build your first scenario with HTTP Agent

GoalWhen another app hands Make a new record, HTTP Agent sends it to your internal system with its API key.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since HTTP Agent has no trigger, start with the app that produces the data, a form or a CRM for instance.

  2. 02

    Add the API key request

    Click the + on the right of that first module, search for HTTP Agent and pick Make an API Key Auth Request. Select the connection you created, or create it now.

  3. 03

    Map the incoming data

    Fill the module fields and map values from the previous module into them. Each bundle (one item passed from one module to the next, such as one contact) becomes one request.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check what reached your system before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module: Scheduling is every 15 minutes by default. Keep it or adjust it, then switch the scenario on. Each module run counts as one operation on your plan.

Modules

What each HTTP Agent module does

HTTP Agent gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

HTTP Agent1

Make a Request

ActionIn the docs only

This one sends a plain HTTP or HTTPS request to the connected system you chose, with no extra credential on top. It is the simplest of the three to set up.

When to use it
the address behind your On-prem agent answers without a key or a password, for example a status page your team reads from.
Watch out
if the system later starts asking for credentials, switch to one of the two auth modules rather than adding them by hand.
HTTP Agent2

Make an API Key Auth Request

ActionIn the docs only

You get an authenticated call signed with the API key of the third-party account behind the connected system. You decide whether the key travels as a header or as a query parameter, and under which parameter name.

When to use it
the service documentation hands you a key rather than a login.
Watch out
the key comes from that system, not from Make; its own documentation explains how to generate one.
HTTP Agent3

Make a Basic Auth Request

ActionIn the docs only

Here the request signs in with a username and a password, those of your account on the third-party system reached through the On-prem agent.

When to use it
an older business tool only knows basic authentication and you still want a scenario to feed it.
Watch out
the connection stores that password, so use a dedicated service account instead of a colleague's personal login.
Need help

Need help automating HTTP Agent with Make?

A person reads every message.

FAQ

HTTP Agent and Make: frequent questions

01Is the HTTP Agent Make integration free?
No. HTTP Agent is an Enterprise app, and Make reserves those apps to its Enterprise plan. The Free plan covers the 3,000+ standard apps with 2 active scenarios, a 15 minute minimum between scheduled runs and 512 MB of data transfer, but HTTP Agent is not part of it. Paid plans are Core, Pro, Teams and Enterprise, and only the last one opens this app. The pricing pages of Make give the current details for each plan.
02What do you need to connect HTTP Agent to Make?
You need a connected system already configured in your On-prem agent, plus an Enterprise plan. When you click Create a connection, Make asks for an optional connection name and the connected system in a dropdown. The rest depends on the module: an API key, its placement and its parameter name for the API key module, or a username and a password for the basic auth module. Make a Request needs no extra credential.
03Can HTTP Agent start a scenario by itself?
No. The app has no trigger, only 3 actions, so something else has to start the scenario. You can place a module from another app first, for instance a new form entry or a new CRM record, and let HTTP Agent act on it. You can also rely on Make's own schedule, which runs a new scenario every 15 minutes by default and can be changed on the first module.
04What if an HTTP Agent module is missing in Make?
It depends on what is missing. HTTP Agent has no Make an API Call module, so there is nothing more generic to fall back on inside this app. The 3 modules cover requests without credentials, with an API key and with basic authentication. If your system needs another form of sign-in, look at whether another Make app handles that system directly, or ask the team to review the case with you.
05Should you use Make or n8n for HTTP Agent?
It depends on where your team already works. HTTP Agent is built around the On-prem agent and the connected systems configured there, so if those are in place and your organization is on the Enterprise plan, Make is the direct route. If you are choosing a platform from scratch, compare the two on the criteria that matter to you, such as which apps you need and how your team likes to build. The n8n vs Make comparison on this site walks through them.
Same platform

Other docs you might need on this stack.

Browse all integrations