Hey! I need to import about 3,500 users into my system running on Memberstack, Webflow and Airtable. Webflow has a API rate limit of 60/minute. I am also sending email to everyone via Gmail. How do you make the import work to match the 60/minute rate? Thanks!
Welcome to the Make community!
Could you please share screenshots of the module fields and/or filters in question? It would really help other community members to see what you’re looking at.
You can also export the blueprint file to allow others to replicate the issue. At the bottom of the scenario editor, you can click on the three dots to find the Export Blueprint menu item.
Uploading it here will look like this:
blueprint.json (119.3 KB)
For a rate limit of 60/min, you’ll likely need to have a sleep module of 1 second somewhere in your scenario before the Webflow module.
For a rate limit of 60/min, you’ll likely need to have a sleep module of 1 second somewhere in your scenario before the Webflow module. This ensures that it never runs more than 60 times per minute.
Webflow sends the number of remaining requests (before hitting the rate limit) in the response headers. Unfortunately Make only shows us the response body, not the response headers.
I would love Make to introduce a Webflow module that could show us the response headers, that way we could do a quick check at the beginning of a path to see if we are close to the rate limit and then add a delay if we are.
@patina.photo That’s a great idea!
Alternatively, in the meantime you can use the generic HTTP module that allows pass-through of headers - You’ll just need to know which endpoint to call using the Webflow API documentation.
Setting up the oauth2.0 for the http module looked a bit intimidating compared to the streamlined setup for the webflow modules ; but maybe I’ll have another look at it tomorrow.
To accommodate a rate limit of 60 requests per minute, it is highly recommended that you incorporate a sleep module with a duration of at least 1 second within your scenario. This brief pause should be strategically positioned before the Webflow module to ensure a smooth and compliant flow of requests while adhering to the specified rate limit.
If I understand this right, I’d need a 1 second sleep before every webflow module, in every scenario otherwise concurrent scenarios could be disrupted. This would also unnecessarily delay actions that don’t hit the rate limit.
It’s seems like a pretty clumsy brute force approach compared to getting the rate-limit data webflow provides (even though make doesn’t make it easy to get that info right now)