Lindy Rate Limits

Important: Credit limit enforcement is not instant. Lindy can only limit usage after the limit has been breached, not precisely when it is reached. A task that starts before the limit may complete and push usage slightly over.

Instructions

Step 1: Monitor Credit Usage

In the Lindy dashboard:

1. Navigate to Settings > Billing
2. Review current credit consumption
3. Track per-agent credit usage
4. Set up alerts for high-consumption agents

Step 2: Reduce Per-Task Credit Cost

Choose the right model for each step:

Reduce action count per task:

• Combine multiple LLM calls into one prompt with structured output
• Use deterministic actions (Set Manually) instead of AI-powered fields where possible
• Eliminate unnecessary condition branches
• Use Run Code for data transformation instead of LLM steps

Step 3: Optimize Trigger Frequency

Prevent credit waste from over-triggering:

Problem: Email Received trigger fires on ALL emails → 200 tasks/day
Solution: Add trigger filter: "sender contains '@customers.com'
          AND subject does not contain 'auto-reply'"
          → 20 tasks/day (90% reduction)

Trigger filter best practices:

• Use AND/OR conditions with condition groups
• Filter by sender, subject, label for email
• Filter by channel, keyword, user for Slack
• Add keyword filtering to exclude automated messages

Step 4: Implement Webhook Rate Limiting

When your application triggers Lindy agents via webhooks, rate-limit on your side:

// Rate limiter for outbound Lindy webhook triggers
class LindyRateLimiter {
  private tokens: number;
  private maxTokens: number;
  private refillRate: number; // tokens per second
  private lastRefill: number;

  constructor(maxPerMinute: number) {
    this.maxTokens = maxPerMinute;
    this.tokens = maxPerMinute;
    this.refillRate = maxPerMinute / 60;
    this.lastRefill = Date.now();
  }

  async acquire(): Promise<boolean> {
    const now = Date.now();
    const elapsed = (now - this.lastRefill) / 1000;
    this.tokens = Math.min(this.maxTokens, this.tokens + elapsed * this.refillRate);
    this.lastRefill = now;

    if (this.tokens >= 1) {
      this.tokens -= 1;
      return true;
    }
    return false;
  }

  get remaining(): number {
    return Math.floor(this.tokens);
  }
}

// Usage: limit to 30 webhook triggers per minute
const limiter = new LindyRateLimiter(30);

async function triggerLindy(payload: any) {
  if (!(await limiter.acquire())) {
    console.warn(`Rate limited. ${limiter.remaining} tokens remaining`);
    throw new Error('Lindy trigger rate limited');
  }
  await fetch(WEBHOOK_URL, {
    method: 'POST',
    headers: { 'Authorization': `Bearer ${SECRET}`, 'Content-Type': 'application/json' },
    body: JSON.stringify(payload),
  });
}

Step 5: Budget Alerts

Set up monitoring to catch runaway agents before they drain credits:

// Credit usage monitor
interface CreditAlert {
  threshold: number;   // percentage of monthly credits
  action: 'warn' | 'pause' | 'notify';
}

const alerts: CreditAlert[] = [
  { threshold: 50, action: 'warn' },    // 50% used: log warning
  { threshold: 80, action: 'notify' },  // 80% used: Slack alert
  { threshold: 95, action: 'pause' },   // 95% used: pause non-critical agents
];

Step 6: Cost Attribution

Track which agents consume the most credits:

1. In dashboard: review per-agent task counts and credit usage
2. Identify top consumers — agents with frequent triggers or large models
3. For each high-cost agent, evaluate: Can the model be smaller? Can steps be consolidated?

Resource Protection

Lindy includes built-in protection: when a task starts using more resources than expected, Lindy pauses and checks in before continuing. This prevents runaway agent steps from consuming unlimited credits.

Error Handling

Resources

• Lindy Pricing
• Lindy Documentation

Next Steps

Proceed to lindy-security-basics for API key and agent security.