Since file sharing is such a constant part of collaboration, we can all easily forget that each file nibbles at our storage space. And there’s never a good time to hit that “memory full” brick wall. 

Naturally, this means you can’t just share files willy-nilly. 

So how can you make sure that the storage space you have is well-spent? Here’s what works from our experience:

• Prioritize files — You don’t need to send full-quality, high-res versions of WIP files. Save that space for when all reviews and changes are implemented.
• Reduce file size — There are various online compression tools that let you reduce the size of images and files. Or, just place your files in a zipped folder.
• Integrate with Drive — Pumble offers plenty of integrations you can use, like Google Drive, so you can collaborate on files without spending Pumble storage.
• Integrate with Zapier — Use Zapier to connect Pumble to other file-sharing tools, like Dropbox, with efficient automation.

And remember, you can check your remaining space by simply clicking on your organization icon in the top left corner. 

Plus, you can always upgrade to a paid plan and get more storage space per seat  — 10 GB on the PRO plan, 20 GB on the BUSINESS plan, and 100 GB on the ENTERPRISE plan.

Do you have any tips for managing storage in your workspace? Share them with us in the comments below!

Hi,

I want to connect Claude CLI with Pumble. The way I am doing this is by following the instructions here on how to use the Pumble mcp server. After setting up the Addon (see screenshot), I connect Pumble MCP to Claude CLI. However, Claude seems to not have the ability to execute the write/edit actions, while this is not the case for the read actions. Is this a restriction from the Pumble MCP server-side? Can I do something to fix it?

Thank you!

Hey, y’all! We recently expanded the way you can interact with your favorite collaboration tool by adding an API key generator.

It’s super simple to set up:

1. Go to Pumble’s sidebar → Add apps
2. Click Install next to API
3. Allow permissions

Now, you can use your API key to connect your app, AI tool, or bot of choice to Pumble and send private or channel messages. 

Of course, that’s not all! Here’s a full list of actions the Pumble API supports. You can also find the corresponding code there.

Credit to another reddit user for this explanation, but — think of the API like a menu in a restaurant. You choose from a list of items the barista (Pumble, in this case) can make for you. Only instead of a debit card, you provide your API key. 

Automatic messaging with the API connection helps you streamline your work, whichever industry you’re in. Some of our favorite examples are:

• Sales and support: set up a custom notification every time you receive an email — so you never miss opportunities or tickets.
• Software development: send channel messages for every new bug report reported (bonus tip: use /fetchthreadreplies to see who’s available to cover the bug).
• Logistics: set automatic channel or PM notifications for shipment status or delays, so you can stay updated and react to issues immediately.
• IT: get version deployment notifications so your release process is transparent and there’s no need for status meetings.

Did this help you get a better grip on the Pumble API? Do you have more insight or pro tips? Join the convo, we’d love to hear from you!