Replace Schedule Trigger with Redis Trigger + Rate Limiting for http request (exact online) API

Describe the problem/error/question

I have a working n8n workflow that processes Exact Online orders using a schedule trigger every 30 seconds. I want to replace this with event-driven processing using Redis Trigger while preventing API overload.

Current Working Setup:

  • Webhook receives Exact Online events → Redis enqueue

  • Schedule Trigger (30s) → Redis pop → HTTP API call → Process order

  • Works reliably but polls unnecessarily when queue is empty

Goal: Replace the schedule trigger with Redis Trigger that fires when jobs are queued, but ensure only one HTTP request happens at a time to prevent OAuth token issues.

Constraints:

  • Must prevent concurrent Exact Online API calls (OAuth limitations)

  • Need reliable processing of queued jobs

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite): Redis Cloud
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via : Docker (Elestio)
  • Operating system: Windows

Hey, so do you have any particular question around the new setup?

Hi! My goal is to replace the schedule trigger with Redis Trigger that fires when jobs are queued, but ensure only one HTTP request happens at a time to prevent OAuth token issues. When I add a Redis trigger, how do I make sure it pushes one event at a time, instead of multiple in the same seconds?

Hey, you can control this via Concurrency control, but it’s global for all workflows.

That’'s a good suggestion, but I dont want to change it for all flows. I was thinking of some kind of boleanen: is busy > dont process, is not busy > process

Another approach can be:

  • Redis trigger → write events into a queue →
  • Use a Loop node to process events form queue one by one →
  • Send them to sub-workflow and wait for output →
  • Repeat

This can be a good pattern to throttle just that workflow.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.