Skip to content
GlossaryConceptUpdated May 2026

Throttle

noun · also: rate-limit, queue, exponential-backoff

What is throttle?

A throttle is a deliberate slowdown — capping how many requests per second you send to avoid rate-limiting or overwhelming a downstream system.

Definition

Full definition of throttle

When you bulk-process 10,000 records, hitting an API at full speed will rate-limit you. A throttle (e.g., 5 req/sec) paces the requests. Tiny Command has a built-in Throttle node you can drop in front of any action. Useful for staying under API limits, smoothing spiky load, or being a polite API consumer.

In practice

Throttle examples

Throttle config
Max 5 requests per second, queue the rest
Used by

Apps that exemplify throttle

See throttle in action across real integrations.

FAQ

Common questions about throttle

Throttle vs Rate Limit?
Same concept, different sides. Rate limit = API restricting you. Throttle = you restricting yourself to stay safely under the rate limit.
Where in the workflow does the Throttle go?
Just before the rate-limited action. Earlier steps can run at full speed; only the slow action gets throttled.