Pumble offers API integration for businesses to facilitate team communication and messaging across devices.
Start today, cancel anytime.
Always up to date with latest API changes.
Trusted by SMBs.
Make.comAvailable Module Types
- All Modules (10)
- Action
- Search
- Universal
- Trigger (polling)
Pumble API Integration for Make.com
Create custom Pumble automation workflows by using triggers, actions, and search modules listed below.
Trigger (polling)
Watch Messages
Triggers when new messages arrive in a specified channel.
Action
Add a Reaction
Adds a reaction to a specific message in a channel using the Pumble API.
Action
Create a Channel
Creates a new channel in your Pumble workspace with a specified name, type, and optional description.
Action
Delete a Message
Deletes a message from a channel in your Pumble workspace using the message ID and channel ID or name.
Search
List Channels
Retrieves a list of channels.
Search
List Messages
Fetches all messages from a specific channel in your Pumble workspace.
Search
List Users
Retrieves all users in the Pumble workspace.
Universal
Make an API Call
Performs an arbitrary authorized API call.
Action
Send a Message to a Channel
Sends a message to a Pumble channel by name or ID.
Action
Send a Reply
Sends a reply to a specific message in a channel using the Pumble API.
Pumble Automation Use Cases
Explore potential use cases for automations using Pumble API and utilize our integration modules crafted specifically for such workflows.
2 modules
Create Channel for New Projects
Create a new channel for each new project to organize discussions.
List Channels
Create a Channel
2 modules
Send Welcome Message to New Users
Send a welcome message to new users joining the workspace.
Send a Message to a Channel
List Users
2 modules
Add Reaction to Important Messages
Add a reaction to mark important messages in a channel.
Add a Reaction
Watch Messages
2 modules
Delete Outdated Messages
Delete messages that are outdated from specific channels.
Delete a Message
List Messages
2 modules
Notify Channel on User Activity
Send a notification to a channel on specific user activities.
Send a Message to a Channel
List Users
2 modules
Fetch and Display Channel List
Retrieve and display a list of all channels in the workspace.
Make an API Call
List Channels
2 modules
Monitor New Messages in Channels
Monitor and track new messages arriving in specified channels.
List Messages
Watch Messages
2 modules
Archive Messages After Review
Archive messages after they have been reviewed in the channel.
Delete a Message
List Messages
2 modules
Reply to Specific Messages
Send a reply to specific messages in a channel.
Send a Reply
Watch Messages
Supported Platforms
- Make.com
How to start with Pumble on Make.com?
Follow our step-by step guides on setting this API integration on Make.com no-code platform.
Our team of experts needs to know your concern. Please, report any issues you notice during app execution.
Recently reported issues
Below you can find issues that were reported already by other users. Try avoid duplicates.
The Pumble "Watch New Messages" module in Make does not seem to work correctly.
Problem description:
Even when the module is configured with "Choose where to start" = "From now on", it still retrieves older messages instead of only new messages posted after activation.
During testing, the module returned a batch of 10 historical messages from the same channel, with timestamps ranging from older dates up to newer ones, instead of only the latest new message. This suggests the trigger is not respecting the selected starting point.
Additionally, the module is also returning system/channel events as if they were normal new messages. For example, it returned an event with:
subtype = "updated_description"
text like: "set the channel description: ..."
This is not a user message, but a channel system event. The module should either:
ignore these events by default, or provide a clear option to include/exclude them.
Expected behavior:
When "From now on" is selected, the module should only return messages created after the module is activated.
It should not return historical messages already in the channel.
It should differentiate between:
normal user messages
bot/app messages
system/channel events
thread replies
- Actual behavior:
The module returns old messages from the channel even after choosing "From now on"
The module also returns channel system events such as updated_description
As a result, the trigger is unreliable for building automations based on truly new incoming messages
Suggested improvements / solutions:
Make "From now on" strictly respect the current timestamp/checkpoint and ignore any previous messages.
Exclude system events (such as updated_description) from Watch New Messages by default.
Add a filter option in the module UI to choose what should trigger:
only user messages
include/exclude bot messages
include/exclude thread replies
include/exclude system events
Add a dedicated trigger for:
new channel messages
new thread replies
system events
instead of mixing them in the same output.
Ensure the first execution after setup does not backfill old channel history unless explicitly requested.
This issue makes it difficult to use the module as a reliable trigger for real-time message automations.
Resolution: This is expected. The API returs all messages (events). You need to filter out events after trigger using in-built filters feature after the module.