I’ve four questions about using the embedded workflows that don’t seem easy to resolve. I’ve looked through the documentation for quite some time but still am having difficulty with the following:
Is it possible to use basic auth for accessing my app’s workflow API? (Documentation on using Authentication is here.). I am using www.cloudmailin.com for processing reply-to emails to my app. In testing, all is OK when using the API without authentication; unfortunately, not able to do so with authentication. (I’m connecting to an endpoint created for a workflow named “mg_connect”.
https://[URL encoded bubble login]:[bubble password]@appname.bubbleapps.io/version-test/api/1.0/wf/mg_connect)
Will auth work without having to specify header values from the remote servers? (One of the remote services I’m trying to use makes post requests to the bubble app but there isn’t the ability to specify header values to specifically call an authentication type.)
Or are there any instructions for using bubble OAuth2 service as stated in the documentation?
Use OAuth 2.0 authentication. This is the prefered method of allowing an un-trusted web application to make requests on behalf of one of your users. Documentation coming soon; for now, contact [email protected] for assistance.
- How can you create Login workflows based on the API credentials?
Create sign up / login api workflows. This is useful for building an alternative front-end to your Bubble app, such as a native app that you develop. When an API workflow contains a sign up or a login action, a user ID, a token and an expiration (in seconds) are returned with the response of the call.
The login workflows only show options for login using the standard login & pass but not API tokens.