Pumble Trigger icon

Pumble Trigger

Poll for Pumble events
Join our community

Overview

This node triggers workflows based on events from the Pumble messaging platform. It polls for specific event types such as when a message is received, the bot is mentioned, or a reaction is added to a message. Users can filter events by channel ID for message received events. This node is useful for automating responses or actions in workflows triggered by real-time messaging events in Pumble.

Use Case Examples

  1. Trigger a workflow whenever a new message is received in a specific channel to automate message processing or notifications.
  2. Trigger a workflow when the bot is mentioned to handle commands or interactions directed at the bot.
  3. Trigger a workflow when a reaction is added to a message to track user engagement or trigger follow-up actions.

Properties

Name Meaning
Poll Times Times at which polling should occur, with options for frequency such as every minute, hour, day, week, month, custom cron expressions, or intervals of X minutes/hours.
Trigger On The event type to trigger the workflow on, such as message received, bot mentioned, or reaction added.
Channel ID Filter messages from a specific channel when triggering on message received events. Leave empty to include all channels.

Output

JSON

  • json
    • eventType - The type of event that triggered the workflow (e.g., messageReceived, botMention, reactionAdded).
    • _meta
      * serverTime - The server time when the event was processed.
      * pollInterval - The polling interval used for fetching events.
      * hasMore - Indicates if there are more events available beyond the current batch.

Dependencies

  • Pumble API with API key credential

Troubleshooting

  • If no events are triggering, verify the polling schedule and ensure the Pumble API credentials are correct and have necessary permissions.
  • Errors with codes like INVALID_PARAM or INVALID_TYPE indicate incorrect parameter values; check the node configuration for valid inputs.
  • Database or internal errors from the API (DB_UNAVAILABLE, INTERNAL_ERROR) cause the node to skip triggering temporarily; retry later.

Discussion