Hi @Celso 

Zapier plans have Task allotments, which can impact the processing of triggered Zap Runs.

https://zapier.com/app/pricing?blockRedirectToPlanbuilder=true

Info about rate limits and throttling for Zap apps: https://help.zapier.com/hc/en-us/articles/8496181445261-Rate-limits-and-throttling-in-Zapier#h_01H91ED0PQ56S166BSB7MJNZNT

The Zapier Interfaces Zap app triggers are instant meaning those are fired via webhooks.

I understand its 30 requests per second .

Right, i am an on the Professional plan.

I am creating a solution for my business and I try to undestand the SLAs

@Celso

If you want to get an official answer, you can try opening a ticket with Zapier Support: https://zapier.com/app/get-help

Zapier Interfaces Zap app triggers are instant, which means those use webhooks.

• Each user’s webhooks are subject to a 429 status code rate limit after 10,000 requests in a 5-minute window. This includes subscription webhooks and REST Hooks.
• Each individual webhook will return a 429 status code after 30 requests per second to encourage a smooth delivery of hooks instead of massive bursts. This includes subscription webhooks and REST Hooks.
• Legacy webhook routes without the user ID in the URL will return a 429 status code after 1,000 requests are received in a 5-minute window (per webhook route). This includes subscription webhooks and REST Hooks.
• During heavy periods of sustained webhook activity, Zapier may return a 200 status but still delay the processing of your webhooks by several minutes.
• If you want to ensure delivery of webhooks, retry delivery on anything besides a 200 status code from Zapier and use an industry-standard exponential backoff interval for retries.