HTTP Module direct bundles

TT92 · November 21, 2025, 6:32am

Hello,

I am currently migrating my scenarios from the old Pipedrive v1 modules to the new Pipedrive v2 API endpoints using HTTP modules in Make.

With the Pipedrive v1 “Search persons” module I could directly get a collection of bundles, which I then filtered and passed to an Array aggregator based on the organization name, so that I could continue with only one bundle.

Now, when I call the new v2 endpoint via an HTTP module, all items are nested inside a single output bundle.

Is it possible to have the HTTP module output the items directly as collection bundles (similar to the v1 module), instead of having to first use an Iterator and then aggregate them again? I want to avoid i need to add 6 interators…

Henk-Operative · November 21, 2025, 6:59am

Hello @TT92,

No this is not possible. The HTTP module executes a raw request, returning a raw response. To further process the items as separate bundles, you need to iterate over the items array first.

Or, as I understand if from your scenario, pass the items array as whole instead of iterating and then aggregating.

Cheers,
Henk

samliew · November 21, 2025, 8:52am

Option 1:

Use an Iterator + Aggregator combo, with a filter in-between.

Option 2:

Create your own custom app to interface with the external API, and “Iterate” over each result in the array, so that they return as bundles.

See Custom Apps documentation.

Option 3:

Use a single “Code” module that does the filtering of the items.

You can use these modules to run JavaScript code:

Make Code (2 credits per second), or
my “Execute JavaScript” module (default credit usage)

Hope this helps! If you are still having trouble, please provide more details.

— @samliew

TT92 · November 24, 2025, 9:55am

@samliew Thank you for these options, I’ll look into them.

For now, I’ve taken a different approach by mapping the array from the output data. When I query the search person endpoint directly, it’s limited to 2,000 results per organisation, and mapping the array doesn’t seem to have that limitation. If you have any other thoughts on this approach, feel free to let me know.

Furthermore, maybe you or @Henk-Operative can help me with a new challenge during my migration to the V2 API using the HTTP module…

With the old Pipedrive V1 module I was able to create a person and include a custom field containing clickable WhatsApp buttons (app + browser). But when I try to send the exact same value directly via a post request JSON in V2, I get errors saying the JSON is invalid, even though it’s the same value used in the V1 call and the same value I see returned for existing persons with a API get request V2

Clickable links to redirect to Whatsapp Desktop or Web:

Post value V1:

Post V1 value succes:

Post value V2:

Get Person values V2:

I tried to compose in a string, tried to encode url, tried to add blank spaces to the build in variables “space”, but no success till now unfortunately..

TT92 · November 24, 2025, 2:11pm

Found the answer in this post

But pff hard work this migration V1 to V2. Would be great @Make creates a module for the V2 endpoint, way better and visual to create + errors can be handled in the modules!

samliew · November 25, 2025, 3:04am

No problem, glad I could help with "HTTP Module direct bundles"!

1. Which was the most helpful post in this thread?

The Make Community guidelines encourages users to try to mark helpful replies as solutions to help keep this forum organised.

This marks the topic as solved, so that others can:

save time when browsing the latest activity on the forum, and
quickly jump to the solution in this topic

To do this, simply click the checkbox at the bottom of the post that is the most helpful in answering your question.

Here’s a magic link to a list of your other “unsolved” topics: status:unsolved

2. Have you learnt something new?

Do bookmark this topic so you can easily find and return to this topic in future.

Here’s a magic link to a list of your bookmarks /my/activity/bookmarks

3. Have a different/follow-up question? Start a new topic.

Creating a new topic for each question makes it easier for others with the same problem to search for answers. You are also more likely to receive help sooner as new topics are displayed first on the forum’s “new” page!

Hope this helps! If you are still having trouble, please start a new thread.