Softr export

Questions
1

Describe the problem/error/question

Hi, I’m currently on the n8n Starter plan (5 concurrent executions) and plan to upgrade to Pro (20) when the product goes live. Users upload 5 large CSV files into 5 n8n workflows, which clean the data and send them to 5 different Softr databases. Since Softr is limited to 30 requests per second, I’m running into errors when several CSVs are processed in parallel. Ideally, I’d like a single entrance queue line shared by these 5 workflows (or a single concurrent execution for all 5) so they can write to Softr at full speed without hitting the limit, but this doesn’t seem possible. Is there any workaround or recommended pattern for this?​ thanks

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Since Softr’s 30 req/s limit is global across all callers, you need to throttle at the workflow level. In each of your 5 workflows, wrap the Softr HTTP calls with a Split in Batches node (batch size ~5) followed by a Wait node set to 200ms — this gives you ~25 req/s total across all 5 workflows running in parallel, safely under the limit. Adjust batch size or wait time depending on how many workflows actually run simultaneously in your worst case.

3

Hi @Stephane_S , welcome to the n8n community!

I’ve run into the same pattern with rate-limited APIs, and the cleanest workaround is to stop letting five workflows write to Softr independently. Instead, I centralize all Softr writes into a single “writer” workflow and make the other four workflows only do parsing/cleanup, then hand off the final rows to the writer (for example via Execute Workflow / webhook). Inside the writer I throttle on purpose (Split in Batches + a small Wait between batches) so I never exceed Softr’s 30 req/s, even when multiple CSV uploads happen at the same time. n8n explicitly recommends batching + waits to handle API rate limits.