ActionBackblaze B2Updated June 2026

How do I authorize a Backblaze B2 session?

Short answer: You can authorize b2 account in Backblaze B2 by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Backblaze B2 Authorize B2 Account action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Sample request
{}
Returns
{
"apiUrl": "https://api005.backblazeb2.com",
"accountId": "abc",
"downloadUrl": "https://f005.backblazeb2.com",
"authorizationToken": "tok_abc"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Authorize B2 Account.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Authorize B2 Account.

What does the Authorize B2 Account action do in Backblaze B2?
B2's two-step auth — exchanges the application key for a short-lived (24h) session token used for actual operations. The runtime caches the token, so most workflows don't call this directly; it's mostly for explicit re-auth or for debugging.
What inputs does Authorize B2 Account require?
Authorize B2 Account has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Backblaze B2 returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Authorize B2 Account support batch operations?
Yes. Run Authorize B2 Account inside a Loop node to process arrays. TinyCommand handles Backblaze B2's rate limits automatically so you don't have to throttle manually.
More actions

Other Backblaze B2 actions.

Action
List File Names
Returns paginated files within a bucket, optionally filtered by prefix. Useful for inventorying bucket contents or for batch processing of files matching a pattern (e.g., "all .csv files under exports/2026-05/").