Automatic import of modules

:bullseye: What is your goal?

Automatically (or semi-automatically) insert/update modules in our Custom App.

:thinking: What is the problem & what have you tried?

We provide an API for our partners. With every new product release, the API is extended with additional actions (modules) and/or webhooks.
To make all these actions and webhooks available to our partners in Make, we currently need to manually create each module, prepare a test scenario in Make, and submit it for review.

Is there any way to automate this process? We generate an OpenAPI specification, so we are wondering whether it can be imported into Make.
Alternatively, does Make provide an API that would allow us to programmatically create or update modules?

Our goal is to fully automate this update process, but even partial automation would be a significant improvement.

Thank you

Hi @Reservanto_Dev,

I think the SDK apps endpoints can be used to partially automate this process: SDK Apps | Make API | Make Developer Hub

Though I have not used this at all, so I don’t know if you can go as far as changing mappable params for example.

Hope this helps a bit.

Cheers,
Henk

Hey there,

there was an AI made with the idea to automatically create modules from API documentation. I don’t know what happened with it though and can’t find any recent news about it.
I guess give it a couple of months and it will be there.

OpenAPI specs are great for defining APIs, but they don’t contain any context on how you want those APIs to be presented to users in a Make app.

A lot of that is based on use-case:

  • Do you need Dynamic Options RPCs to make ID selection more user-friendly?
  • Would it make more sense to use nested parameters to hide some levels until needed?
  • What parameters should be hidden under the advanced toggle?
  • Should you implement Polling Triggers using a list endpoint?

These (and more) are all things we’re aiming to handle within an AI-based solution.

1 Like