A per-user request limit for your service — holds on its own

The scenario counts each user's requests per minute and per hour and rejects the excess, keeping the service from being overloaded.

  • Counts requests per key
  • A limit both per minute and per hour
  • Rejects the excess requests
  • The service doesn't buckle under load
Webhook
Set it upScriptera

How it works

To connect oneC and Wekan, you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: Webhook1
  2. Then: Set
  3. Then: Redis
  4. Check: Per minute
  5. If yes: Set2
  6. Then: Redis1
  7. Check: Per hour
  8. If yes: Airtable
  9. Then: Function
  10. If no: Set1
  11. If no: Set3

You can launch this oneC + Wekan integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios