Clay Icon

Issue with Smartlead API Limits and Column Errors

ยท
ยท

Hi! Im using native integration to smartlead, but their API can not handle more than 60 requests per minute. And columns are returning an error. Any way to sort this out?

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    You can resolve this by configuring rate limits in your Clay integration settings. Here's how: 1. Locate the rate limit settings in your HTTP API configuration 2. Set the Request Limit to 60 (or slightly lower to be safe) 3. Set the Duration to 60000 milliseconds (60 seconds)This configuration will ensure your requests stay within Smartlead's API limits by controlling how many requests are sent within the one-minute window. Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University

  • Avatar of Mensur
    Mensur
    ยท
    ยท

    Im not using HTTP integration. I'm using native smartlead integration

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    When using Smartlead's native integration, there are a few potential reasons why you might be experiencing these issues: 1. Lead Limit Issues: โ€ข Check if you've reached your Smartlead account's lead limit โ€ข You may need to adjust or increase your limits with Smartlead 2. Duplicate Lead Settings: โ€ข Verify your "Allow Duplicates" setting in Smartlead โ€ข If duplicates are disabled, leads won't be updated or added 3. Blocked Leads: โ€ข Check if any leads are blocked in your account, as these won't be processedTo help manage the flow of leads and prevent errors: ** Use the Lookup action in Clay to check if leads already exist in your campaign ** Set up conditional runs to control when the integration runs * Consider using duplicate checking features to prevent processing the same leads multiple times Source: Smartlead integration overview | Documentation | Clay University

  • Avatar of Channeled
    Channeled
    APP
    ยท
    ยท

    Hi Mensur! This thread was recently closed by our Support team. If you have a moment, please share your feedback: