The goal would be to limit the amount of code written by the end user while extending the plugin to the full capacity of what we can offer as a Loops integration.
We would need to handle some things like support for pulling in dynamic keys and/or supporting free-form keys as well as making sure we have 100% support for the api. Here’s our new Make integration for reference if it helps: https://www.make.com/en/integrations/loops
Looking for someone with experience creating an integration and wants to follow Bubble best practices.
Are we talking about setting up the api requests for your service? It looks like something that anybody can integrate using the built in api connector. You can set them up in the “api calls” section of the plugin without the need of using code. This will leave only 2 things missing:
rate limit needs to be handled in userland with the actions in the app editor
data variables (send transactional email), need to be passed as a json object by the user who will be responsible for creating a valid json. This is needed only for a general plugin, if a user integrates the request directly with the api connector in the project it actually get easier to tailor the request to your specific payload.
If you want to take care of rate limiting and handle data variables in a easier way for the user then you will need to go with code and a server side action. Keep in mind that server side action are priced at more than double compared to api request made with api connector or “api calls” of plugins.
Sooner or later any person building in bubble realize that you need to reach for the api connector because it’s more flexible, easier and faster to debug/change compared to plugins, so you may want to create a bubble specific guide about how to setup the api connector. It would be valuable as much as a ready made plugin.
