Skip to content
Notifications
Clear all

Help: API rate limits are killing our automated reporting flow.

2 Posts
2 Users
0 Reactions
31 Views
(@crm_hopper_2028)
Honorable Member
Joined: 5 months ago
Posts: 354
Topic starter   [#20886]

Okay, I’ve hit a wall with Lindy and I need to know if anyone else has found a workaround or if I’m just using it wrong.

We built a pretty sweet automated reporting flow that pulls data from Lindy into our data warehouse hourly. It was running smoothly for a couple weeks, but now we’re constantly getting throttled by their API rate limits. It’s bringing the whole process to a crawl, and our dashboards are starting to show stale data.

Here’s our basic setup and the specific pain points:
* We’re primarily using the `GET /activities` and `GET /contacts` endpoints.
* Our sync process is iterative and respects pagination, but we have a high volume of daily activities.
* The limit seems to be around 100 requests per minute? The documentation isn’t super clear, and the `429` errors don’t come with clear retry-after headers.
* This is a dealbreaker for us because the whole value prop was having near-real-time insights.

I’ve come from setups with Salesforce and HubSpot, where you can at least:
* Pay for higher API tiers
* Get precise, documented limits
* Use bulk API endpoints for large data sets

Does Lindy have anything like that? Or am I stuck implementing complex retry logic with exponential backoff just to get basic reporting data?

Curious if other power users have run into this and what your strategy has been. Did you switch to webhooks for some events? Are there any undocumented best practices for batching? Or is this just a fundamental limitation of their current infrastructure? 🤔


Still looking for the perfect one


   
Quote
(@darrenk)
Honorable Member
Joined: 3 months ago
Posts: 392
 

Ugh, I feel your pain. That shift from the "everything works" phase to hitting the undocumented rate limit wall is so frustrating.

We ran into something similar and ended up having to build a queuing system with exponential backoff right into our Zapier workflow. It's clunky, but it got us through. Have you checked if Lindy has webhook support for activity creation? Sometimes pushing data out is less restricted than pulling it in hourly.

It's wild that they don't have clear bulk endpoints or higher tiers. That's table stakes for a platform handling sales data.


dk


   
ReplyQuote