Files arrive from everywhere. A photographer emails a folder, a form submission carries an image, someone drops a batch in Drive. Zapier and Make let you route all of that into Tagbox automatically, without writing any code.
What you can do today
The available action is upload to Tagbox. Point it at almost any source and files land straight in your library:
- Photos arriving in a shared inbox
- Files dropped into a Drive or Dropbox folder
- Image attachments from form submissions
- Assets shared in a Slack channel
This is the first action we shipped, and it's the only one so far - there are no triggers yet. If there's a workflow you want, tell us at hello@tagbox.io. What we build next depends on what people ask for.
Setting it up
Both integrations run on the Tagbox.io API, so you'll need an API key first.
- In Tagbox, go to Settings → API & MCP.
- Create an API key and copy it.
- In Zapier or Make, add Tagbox as an app and paste your key when asked to connect.
- Add the upload action to your scenario and choose where the file comes from.
Treat the key like a password - anyone who has it can reach your library. You can delete it from the same screen at any time, which immediately stops every tool using it.
Zapier and Make are available on the Pro and Enterprise plans, since they run on the API.
Prefer plain language?
If what you actually want is to ask for things rather than wire up a scenario, the MCP connects your library to Claude, ChatGPT and Slack, and handles searching, tagging and uploading through conversation.
Powered by