🔥 App update: The new HTTP app is here with a major upgrade

Connecting any app via API?

:electric_plug: Meet the new generation of the HTTP app :electric_plug:

Hey Makers! :waving_hand:

We’re proud that you can use a vast library of 3,000+ native apps with Make, but we want to enable you to break free from any limits and connect even niche, brand-new, or custom internal tools.

The HTTP app is your bridge to the open web, and today it’s getting a massive upgrade. We’ve rebuilt it to make connecting to any API faster, more secure, and intuitive – no code required.

What’s new?

  • Built-in pagination: Fetch large datasets (like all CRM records or invoices) automatically. Just toggle it on in the module settings, no manual loops needed.
  • Revamped UI: Our new UI with helpful hints and guided layout makes setup intuitive and fast.
  • Visual data structures: Build error-free JSON bodies visually. Map fields just like you do in native apps and say goodbye to syntax errors.
  • Enterprise-grade security: Connect to private servers and high-security tools with native support for Mutual TLS (mTLS), Proxies, and a secure Keychain for your credentials.

Helpful resources

:books: Learn how to use it in the Help Center
:memo: Read our blog: Connect to any API faster with Make’s new HTTP app

:puzzle_piece: Explore and try our templates:

Happy automating!

Valery
The Make Team

6 Likes

:clap:

Are there limits to what type of pagination it handles or does it adapt and work with all of them? (Link to next page, items per page, etc.)

This is great news but I’m having some trouble just downloading a file with this new HTTP module.

I do an API call and i get full CSV data back, I have tried content-type text/plain and other things but I just get Response body is not a valid JSON.

Should we still use the legacy http module or download file http module for this?

1 Like

Thank you for your question. You can choose from four types of pagination: cursor/token, offset, page number, and URL, which are the most common pagination solutions.

1 Like

Thank you for your question. We are currently in the process of releasing the new version of the HTTP app. The new equivalent of “HTTP > Get a file” module will be released in the coming days.

Awesome!

The Authentication type option is a huge step toward improving security, especially for beginners!

Most YouTube tutorials use standard HTTP calls without proper token/password encryption, so people have been storing tokens and sometimes even sharing them as plain text.

4 Likes

This is the GAME-CHANGER we have been waiting for. Thank you! :folded_hands:

3 Likes

Have your old Http modules stopped working and are timeouting?
FYI @Valery.Mezencev

Mine are still working fine.

1 Like

Nope, the old HTTP modules are still working as before :+1:

It was just a coincidence that one of the providers had a temporary service outage. I received the newsletter, and then two scenarios went down :slight_smile: Now they’re working properly again.

1 Like

Hi Make Team,
Is there any deadline for migrating to the new version of the module ?
What I mean is, till when the old version will work ? I’ve bunch of scenarios, not only mine, but many of our customers with the old version. Need a proper plan to swipe.
Is there any proper way to copy settings, or any easy way to migrate from one to another ?
It’s not a breaking change purely speaking, but at least a new way of spending time on each scenario :grin:
Thanks for your insight

1 Like

It’s probably unlikely, the old modules will not get deleted, as there are hundreds and thousands of scenarios using these modules.

However, in future Make may decide to prevent selection of the older version’s modules, once the new version is stable and fully operational. Once this happens, it is much harder to get support for the older modules, and we’ll just recommend you to switch to using the new ones. Upgrading the module as soon as possible gives you time to test and adjust to the new changes

That’s how app version upgrades work on Make anyway. For more information, see Replacing Legacy Modules with New Modules — Make Help Centre.

1 Like

Would there be any way to show examples of actually using this? I’ve been trying to set up the new HTTP module to connect to ShipHero and send a graphql query to get a list picks_per_day results, but I can’t figure out how I need to actually configure everything. I know ShipHero has its own set of modules, but I have to manually handle pagination with those for the things I want to get, and I was hoping I could use the new HTTP module to automate paginating through the queries.

For example, if I just try a basic test with a known good bearer token and the correct url and query, I get a generic 500 error back from the server. I don’t see anywhere in the input bundle that a token is even being passed to the server, so I have no way of knowing at which point the test is failing. And that doesn’t even touch on how to handle things like token expiration and refreshes. So some examples of different setups, pagination styles, etc, would be really great.

I believe I see how it works. I am trying to test it on an API call to Quickbooks though that embeds the values into the call. (a Quickbooks query). That requires startposition to be part of the body.

It looks like it would work if we had access to the paging values as variables. Unfortunately it doesn’t look like we have access to that, so it wont work in this particular use case.

If possible, would we be able to get that key value as a variable in a later update? (page/token/startposition)

any plans to have an "update to new version” button?
there is no way I am copy pasting everything one at a time from all my old modules to the new module.

1 Like

Hi everyone.

The new HTTP module seems great.

I have a question related to the pagination config.

How do you refer to the page token and the page size fields when they are sent in the request body?

We already have QuickBooks app in Make. May I ask why you prefer the HTTP app to access your QuickBooks account in Make?

Support for GraphQL requests is on our roadmap.

Our HTTP documentation includes a page with OAuth 2.0 setup guide, with examples:

There is no need to handle the access and the refresh tokens’ expiration manually.

Support for paginated requests to GraphQL is on our roadmap.