These are Server Side Actions meaning there is a small cold-start delay when using it for the first time within a few minutes of not using them (Bubble limitation).
The returned fields are
"status" which will "success" or "error"
"body" which will be either error returned or the successful response. They do not interpret the response like the API Connector at this time but instead are just text.


Actions:


Send Binary Data:
File URL must be a publicly accessible URL and under 7MB in size (Bubble limitation).

If you are sending secret keys in a header, add the keys on the Plugin tab, then reference them in the action as [Secret Key 1], [Secret Key 2], etc. including the brackets. This guarantees an end user can't see the values.

So a header "Authorization - Bearer [Secret Key 1]" will replace [Secret Key 1] with the one from the plugins tab.

---------

API Request:
Simple API Request very similar to the API Connector. Useful if an endpoint looks at the connecting IP Address and wants the same one for multiple calls.

---------

API Request with Digest Auth:
Simple API Request but with Digest Authorization built in (API Connector doesn't support this).

---------

Publish MQTT Message:
Publishes messages to MQTT servers usually for IoT integration.

---------

CloudConvert - Send Binary Data:
Uses the CloudConvert API as an external server to send files with unlimited size.

Create an account at https://cloudconvert.com and generate an API key. Give it the scopes task.read and task.write. Add the API key to the plugin tab

Each file sent consumes 1 credit from your account.

---------

On the Bubble Forum message me @tylerboodman for any questions or requests!