Avoid Slack rate limits with our new features

Written by Owner

Updated at August 20th, 2025

+ More

Table of Contents

New trigger: New Message From Query New input field: Optimized data

Note

This information was accurate at the time of publication. Please check out the latest product update notes for any updates or changes.

We've introduced two new features to improve the reliability of your Zaps using Slack triggers and prevent Slack’s rate limits.

New trigger: New Message From Query

This polling trigger optimizes API usage by making a single request to Slack, reducing the risk of rate limits.
It's perfect for filtering specific messages, making it a more efficient replacement for the Anywhere Message trigger and a filter step.

This input field allows you to fetch data from Slack more quickly and reliably, reducing the impact of rate limits. It's compatible with the following triggers:
- New Public Message Posted Anywhere
- New Message Posted to Slack Channel
- New Message From Query

The following table outlines the high-level differences in output fields based on whether you use the Optimized data field:

Type of information	Results without optimized data	Results with optimized data
User information	Name, profile picture URL, phone, email	User ID
Message Content	Yes	Yes
Timestamp	Yes	Yes
Channel information	Name, ID	Name, ID, Type
Team information	Name, URL	ID, URL
Reply information	No	Yes
Bot information	No	Yes