Reusable HTTP Request Templates

Feature Requests (Old)
1

What would you like to be able to do?

I would like the ability to save and reuse HTTP request configurations across multiple flows in Activepieces. Currently, every time I create a new flow that uses the same API, I have to manually rebuild the entire HTTP request (headers, authentication, body, query parameters, etc.), which is tedious, time-consuming, and inefficient.

Instead, it would be incredibly useful to have a “Saved HTTP Requests” feature, where we can:

  • Create and save HTTP requests (including headers, auth, body, and parameters).
  • Name and organize these saved requests for easy access.
  • Re-use them across multiple flows without needing to set them up again.
  • Modify specific parameters dynamically when inserting a saved request into a new flow.

How would that help you?

This would massively improve efficiency when working with APIs inside Activepieces.

:one: It saves time – Right now, setting up the same HTTP request multiple times across different flows is a waste of time. Having reusable templates would let us build once and use everywhere.

:two: It reduces errors – Manually entering the same API configuration multiple times increases the chance of mistakes (e.g., typos, incorrect headers, missing parameters). A reusable template ensures accuracy and consistency.

:three: It makes up for missing native integrations – Since Activepieces doesn’t yet support every app natively, many users rely on HTTP requests to connect with external services. Reusable HTTP requests would act as a workaround, making it much easier to integrate third-party tools that don’t yet have built-in support. This would significantly enhance the flexibility of Activepieces as an automation platform.

:four: It improves scalability – For businesses and agencies using Activepieces at scale, managing API connections across multiple automations would be much smoother and more organized with saved request templates.

How important is this for you?

This is critical for anyone relying on APIs inside Activepieces. Right now, the manual process slows us down, making Activepieces less competitive compared to tools like Zapier and Make, which offer more streamlined API management.

By adding this feature, Activepieces would:
:white_check_mark: Reduce setup time for API-based automations.
:white_check_mark: Remove friction for power users and developers.
:white_check_mark: Make it a much more viable alternative to competitors.

This improvement would directly increase the platform’s usability, adoption, and long-term value.

2

This is probably not an ideal long-term solution, but you could technically do this now in a sense.

If you were to set up one, (or many), flows which contain only your HTTP request pieces, then you can simply duplicate these flows and then build out the rest of the new flow around it adding the newly required pieces, which should still minimise setup time.

As a side note, don’t forget you can also download the flows as JSON files, so you might be able to save each HTTP request that you set up as its own “template file” of sorts, then simply download it as a JSON file and then you should be able to import it as a new flow/starting point each time you need to re-use it.

As an extra side note (although I have never actually used this piece yet, so I am unsure of its capabilities), there is the Sub Flows Piece - which allows us to call other flows we have created, so maybe after a little planning, there might be a way you can set up some flows containing your HTTP request pieces, then simply call on them in various flows.

EDIT

Also, I forgot to mention that it is more than likely entirely possible to create your HTTP requests using a custom code piece as well. So, as a workaround, you may very well be able to create them in code, which you can simply reuse in as many flows as necessary.

But I do agree that even if your above request is not possible, something like this would be a great addition to AP, even if they could extend the current functionality of what is already possible.

For example, right now, inside a flow, we have the ability to highlight a step (or steps), right-click, copy, and then paste them after the last step. This could be expanded to allow us to copy the step from the current flow and then navigate to a new or different flow and paste it (or even an additional context menu for the duplicate that has duplicate into…), which allows it to be duplicated into an existing flow.

Hope this helps!

Kind regards,

1 Like