Initialized External API (Office 365) still fails for invalid token when called in Bubble API flow

Need help APIs
1

Hey everyone,

I have successfully created and initialized a API POST call using the Bubble API Connector to Office 365.

For scope: my api POST creates an email folder with the display name = my thing Client’s name

api1
api11118×995 61 KB

I successfully initialized the API, the token works, and my POST action is successful in my normal workflow operation. (add a client, POST creates the folder with client name).

My problem When I try to call the same POST action within a recurring Bubble API Workflow, I still get the error of an invalid token. Same environment (deploy vs. live), same parameters sent, etc.

api2
api21386×971 68.4 KB

Use Case for Clarity: I have uploaded about 400 Clients via App Data Editor, but since I did that in Editor, my normal workflow does not run. I was hoping to run this API workflow in Bulk on my created Clients to create the mail folders.

What say you? What am I missing?

2

To anyone who comes across this: I guess the Editor cannot access the API connections that the app can. When I created a button within the app to run my workflow, it went great. You canNOT call an external API connection through the “Bulk” Editor within App Data.

Perhaps @emmanuel & Co. can add that to the roadmap sometime.

3

This works because the workflow uses the same authentication as the user on the page who pushes the button.