Integration · Cloud and hosting
AI agents for Backblaze B2
List Backblaze B2 buckets, browse and search files and their versions, read a file's details, copy files, and hide or delete files, with a B2 application key, through the native B2 API.
- Actions
- 7
- Read
- 4
- Write
- 3
Actions
What your agents can do in Backblaze B2
7 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 4
Look things up. Nothing changes.
List buckets
Lists the account's buckets (only the key's bucket for a key restricted to one), as buckets.
List files
Lists the files in a bucket by name, as files: each with fileId, fileName, contentLength (bytes), contentType, uploadTimestamp (milliseconds) and action.
List file versions
Lists every version of the files in a bucket, newest first per name, including hidden ones, as files (each with fileId, fileName, contentLength, uploadTimestamp and action: upload, hide or start).
Get file details
Reads one file version by its fileId: fileName, bucketId, contentLength, contentType, contentSha1, fileInfo (custom metadata), uploadTimestamp, action and any retention or legal hold.
Write 3
Create, change or send.
Copy a file
Copies a file version, by its fileId, to a new name, in the same bucket or another one of the account (files up to 5 GB).
Hide a fileDeletes data
Hides a file by name: it disappears from List files and downloads by name, but its versions stay (and stay billed) until lifecycle rules remove them.
Delete a file versionDeletes data
Deletes one version of a file for good, by its fileId and fileName.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Enter the sign-in details Backblaze B2 gives you for its API.
What you enter
- keyID
- applicationKey
Settings
- Cluster
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Backblaze B2 data
Ask a question in plain words. The agent can list buckets, list files or list file versions in Backblaze B2, then answers with what it found.
- 02
Let an agent update Backblaze B2
Have the agent copy a file or delete a file version in Backblaze B2 as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Backblaze B2 and Slack: it can list buckets in Backblaze B2 and post a summary to a Slack channel in the same run.
FAQ
Backblaze B2 and MyDeepAgents
Can MyDeepAgents connect to Backblaze B2?
Yes. The Backblaze B2 connector has 7 actions: 4 read and 3 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Backblaze B2?
Enter the sign-in details Backblaze B2 gives you for its API. You'll need: keyID and applicationKey. The connection also asks for: Cluster. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Backblaze B2 without asking?
Only if you let it. Each of the 3 actions that change data can be set to wait for a person's approval before it runs, and the 2 that delete data ask first by default.
Can I use Backblaze B2 in workflows as well as agents?
Yes. Every Backblaze B2 action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Backblaze B2 to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.