Request for feedback: What 3rd party integrations are missing?

[nicolas_dap]

@vini_brito

I just want to reaffirm: beef up the plugin editor and API connector and we’ll do miracles there! There are lots of ideas through the forum and I know that several people (including me) has emailed support several other suggestions.

100% agree.

@allenyang Before integrating other services, empower us. The plugin Editor and the API Connector are limiting us. Here just few posts about it !

We Really Need a GET Method for Workflow APIs

+1 also. I’m stuck for implementing the full CloudConvert API because the callback is done as a GET request on the endpoint : [image] @Bubble Can you tell us if it on the roadmap or a workaround such as using Amazon API Gateway is necessary with Bubble ?

Plugin Editor limitations

Hi @Bubble I’m very willing to contribute to the community but the Plugin Editor is frustrating to use. There are some requests : 1/ Duplicating an already initialized API call, the copied call is also active but we may need to work on it before we publish it. Can you add a way to remove the initialization ? [image] 2/ Using the same API, some API calls need different authentification parameters, for instance some client-side with Publishable keys whereas most of the calls use Secret Key. …

/!\ API calls - initial parameters applied when empty

@Bubble Here a new exemple why empty field should be considered when we use a plugin’s api call. see with the plugin MailChimp Extended. I subribe a new user : [image] but the values used to setup the API call are used : [image]

API - Returned Value - Set DATE format

@Bubble, could you add “Date (UNIX)” as a type and convert it ? Right now we must use another plugin to handle this basic thing. Here an exemple from Stripe : [image] and have you think auto-detecting the UNIX date ? All dates between 1990 and 2200 are between 631.148.400 and 4.102.441.200. That would enable detecting 99% of the UNIX dates and few numbers are that high