PumbleInstall

Summary

Search messages in a Pubble channel using a query term, with optional filtering by channel, user, and pagination.

Inputs

• query (required) — The search term to look for in messages. Required; an empty query throws an error.
• returnAll — Whether to return all results or only up to a given limit. When true, pagination continues until no nextCursor is returned; when false, a single API request is made.
• limit — Max number of results to return. Ignored when returnAll is true. The API caps this at 20, regardless of the UI value (1–100).
• additionalFields — Optional collection of filters and pagination state. Options include: 'in' (multiOptions, filters by channel IDs/names loaded via getChannels), 'from' (multiOptions, filters by user IDs/names loaded via getUsers), and 'cursor' (string, pagination cursor from a previous request).

Output shape

An array of message objects matching the search criteria. When returnAll is true, results are accumulated across paginated requests until no nextCursor remains. Otherwise, a single request returns up to the limited number of messages (max 20). Results are wrapped in n8n execution metadata via constructExecutionMetaData and returnJsonArray.

The API endpoint POST /searchMessages is called with a body containing { text: query, [in: [...]], [from: [...]], [limit: N, [cursor: '...'] ]}. The response shape is expected to contain a 'messages' array (or the entire response if flat), and a 'nextCursor' field for pagination.

Links

• n8n community nodes installation guide