How to Use the "Push File to Box Action" in Salesforce Flow?

So in general flow action documentation can be found https://developer.box.com/guides/tooling/salesforce-toolkit/flow-actions

It requires a content version id (what) and and box folder id (where). It makes callouts to box like many of our actions. This requires the correct flow type be used. 
 

Flow Types That Support Callouts

Yes — callouts allowed:

• Autolaunched Flows (no trigger) — when called asynchronously (e.g. from a Scheduled Path, Platform Event, or via @future)
• Record-Triggered Flows — only on asynchronous paths (the "Run Asynchronously" after-save path, or Scheduled Paths). The synchronous before/after-save path cannot make callouts.
• Screen Flows — yes, callouts are allowed since they run in user context
• Scheduled Flows — yes, they run asynchronously
• Platform Event-Triggered Flows — yes

No — callouts not allowed:

• Record-Triggered Flows on synchronous paths (before-save or the default after-save "Run Immediately" path)
• Any flow invoked synchronously from Apex that is already in a transaction that has performed DML (you'd hit the "You have uncommitted work pending" error)

 Here are some things to lookout for if you are having issues.
 

ContentDocument vs ContentVersion: Flow typically gives you a ContentDocumentId, but this action requires a ContentVersion Id. Add a Get Records step first:

ContentVersion WHERE ContentDocumentId = {your id} ORDER BY CreatedDate DESC LIMIT 1

Then pass that ContentVersion.Id into the action.

Other silent failure causes:

• File over 25MB — hard limit, will fail
• Invalid Box OAuth — if the admin token is expired/missing, the action returns nothing; always check isSuccess and errorMessage after the action with a Decision element
• Wrong folder Id format — must be the numeric Box folder Id (e.g. "987654321"), not a record Id or folder name
• Box admin lacks folder access — the action runs as the admin user; that user must have access to the target folder

Hi ​@DavidAtBox - thanks for your reply! 

Understood about that current documentation page. Is there anything more robust than just a listing of what actions exist?

As for my use case - the error message I’m receiving is “Exception caught when pushing file to Box: Error getting token: user hasn't approved this consumer”. 

Can you advise? The Box Admin user owns all of our Box for Salesforce folders, so shouldn’t that user have access?