Hi Zernio Team,
I've been building a multi-bot setup on top of Zernio and ran into a limitation I'd like to flag.
Webhooks are currently scoped at the workspace level, which means every webhook endpoint receives events from all accounts in the workspace. If you have 3 bots on 3 separate servers, all 3 will receive each other's events, even if those events have nothing to do with them. The only way around it right now is filtering by accountId or profileId on your own server, which works but forces you to duplicate that logic everywhere and still process traffic that was never meant for you.
I get that this is how it works by design, and I know it doesn't touch the rate limit. But for anyone running multi-account or multi-bot architectures, it creates unnecessary noise and makes things harder to maintain cleanly.
The fix seems straightforward: allow webhooks to be scoped to a specific accountId or profileId at creation time, either through a filter field in the UI or a parameter in the API. That way each webhook only gets the events it actually needs.
Would love to see this added. Thanks for considering it ;3
Please authenticate to join the conversation.
In Review
Feature Request
3 months ago

Valentino Barradas
Get notified by email when there are changes.
In Review
Feature Request
3 months ago

Valentino Barradas
Get notified by email when there are changes.