API limit reached when user information is obtained from Slack

There are two options for obtaining user information using Slack Integration.

  1. Limit
    First of all, i can enter up to 100 limits in n8n. In fact, we can enter up to 1K in the Slack API guide document (users.list method | Slack)

  2. Return All
    The second is when you use Return All.
    In this case, it is not determined exactly, but it seems to be performing about 100 Limits several times. (pagination)
    If the entire Slack user is a 10K user, 100 calls occur, and the Slack API Limit (Tier 2) is reached and the following message is received.
    ERROR: The service is receiving too many requests from you! Perhaps take a break?

The number of people in my workspace is actually 10K+. And you often reach the Rate Limit.
Is there a way to solve this?

Information on your n8n setup

  • **n8n version:0.230.3
  • **Database (default: SQLite): default
  • **n8n EXECUTIONS_PROCESS setting (default: own, main): own
  • **Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • **Operating system: linux

Hi @Supka, I am sorry you’re having trouble. Unfortunately, n8n’s Slack node like most other nodes do not respect rate limits by default. When sending data it’s easy to solve problems arising from this by using the Split in Batches node.

That’s of course not much help when fetching data. So I am afraid you’d have to resort to the HTTP Request node here. Here’s a quick example showing how to fetch multiple users in a loop with configurable Wait times to avoid hitting the rate limit:

In addition to adjusting the Wait time to avoid rate limits, you can also adjust the limit parameter on the HTTP Request node freely, but be aware that Slack suggests relatively low count count here:

To begin pagination, specify a limit value under 1000. We recommend no more than 200 results at a time.

Also, be aware that loading a large number of items at once might eat up considerable amounts of memory, so you would want to keep an eye on the memory consumption of your docker container.

Hope this helps :slight_smile:

1 Like

Thank you so much for your quick and kind reply.
I expected to some extent, and fortunately, I am very happy that you presented a detailed sample flow.

I will try again to make a better flow with the method you suggested.

And I always leave a thank you message to the n8n officials. You’re the best!
Thank you.


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.