AI Automation / Zapier Workflows
Design Zaps that respect API rate limits — prevents 429 errors and account lockouts.
Why This Prompt Exists
APIs have rate limits. Exceed them and your Zap fails — temporarily or permanently. High-volume Zaps need rate limit planning.
You get:
- 429 errors that stop your Zap in the middle of processing
- temporary account lockouts (annoying) or permanent bans (catastrophic)
- Zaps that work at low volume but fail during peak times
- no visibility into how close you are to rate limits
- manual work to retry failed records after rate limit resets
But rate limits can be managed:
- spreading: distribute actions across time (don’t burst)
- queuing: hold records and process slowly
- prioritization: process critical records first
- caching: avoid duplicate API calls
- batch processing: combine multiple actions into one API call
Without planning, high-volume Zaps hit limits and fail.
This prompt designs rate-limit-aware Zaps for high-volume use cases.
The Prompt
Assume the role of an API reliability engineer who plans for rate limits. Your task is to design a Zap that respects API rate limits. Generate: 1. API RATE LIMITS (per app used) | App | Limit (per minute) | Limit (per hour) | Limit (per day) | Burst allowed? | |-----|-------------------|------------------|-----------------|----------------| | [app] | X | Y | Z | Yes/No | 2. ZAP VOLUME ANALYSIS - Expected daily triggers: [X] - Peak hour triggers: [Y] - Peak minute triggers: [Z] 3. RISK ASSESSMENT - Which actions are closest to rate limits? - Which time periods exceed limits? - Risk level: Low / Medium / High 4. RATE LIMIT STRATEGY - Spread: [delay between actions in milliseconds] - Queue: [use Zapier Queue or storage] - Batch: [combine multiple records into one API call] - Prioritize: [process high-value records first] 5. IMPLEMENTATION PLAN - Step 1: [add delay between actions] - Step 2: [implement queue for peak times] - Step 3: [add retry with exponential backoff] - Step 4: [monitor rate limit headers] 6. FALLBACK FOR RATE LIMIT ERRORS - What to do when 429 occurs: [retry after X seconds / save to queue / notify team] - Retry strategy: [linear / exponential backoff] 7. MONITORING RECOMMENDATIONS - Track: [rate limit remaining headers] - Alert when: [remaining < 10% of limit] INPUTS: Apps in this Zap: [E.G., "Salesforce, HubSpot, Google Sheets"] Known rate limits (if known): [E.G., "Salesforce: 15 requests per second"] Expected daily volume: [E.G., "50,000 records per day"] Peak hour volume: [E.G., "10,000 records between 9-10 AM"] RULES: - Research rate limits before building high-volume Zaps (don't assume) - Always add delay between actions for apps with low per-second limits - Use Zapier's built-in queue for bursty traffic (Storage by Zapier) - Implement exponential backoff for retries (1s, 2s, 4s, 8s...) - Test with 10x expected volume to find limits before production - Monitor rate limit headers (X-RateLimit-Remaining) when available
How To Use It
- Research API rate limits before building high-volume Zaps — don't assume limits.
- Add delays (Pause action) between actions for apps with low per-second limits.
- Use Zapier's Storage app as a simple queue for bursty traffic.
- Implement exponential backoff retries (Zapier's built-in retry is linear).
- Test with 10x expected volume in a staging environment to find limits.
Example Input
Apps in this Zap:
"Salesforce (create leads), Slack (notifications)"
Known rate limits:
"Salesforce: 15 requests per second, 50,000 per day. Slack: 1 request per second per workspace."
Expected daily volume:
"30,000 records per day"
Peak hour volume:
"10,000 records between 9-10 AM"
Why It Works
Most Zapier users discover rate limits when their Zap starts failing — usually during peak traffic when failures are most damaging.
This framework improves outcomes by forcing:
- rate limit inventory (what limits does each app have?)
- volume analysis (how close will you get to limits?)
- risk assessment (when are you most likely to exceed limits?)
- mitigation strategy (spread, queue, batch, prioritize)
- fallback planning (what to do when a 429 occurs)
Great rate limit planning doesn't prevent all 429s — it ensures your Zap survives them gracefully.
Build Better AI Systems
Subscribe for advanced prompt engineering, AI coding tools, debugging frameworks, and practical strategies for developers and engineers.