Hi @mjhalfdozen, if you’re submitting to the Marketplace you must verify any domains your app uses (redirect URLs, webhook bases, policy pages) and it’s a one-time, account-level check
You can’t validate n8n.cloud since you don’t control it, so validate workway.co and route the OAuth redirect through it (e.g., /zoom/callback) then relay to n8n
If your automation only acts on your own Zoom account without user interaction, prefer Server-to-Server OAuth - Zoom’s guidance on when to use S2S vs OAuth fits this
If clients in other Zoom accounts must authorize, use a standard OAuth app and Marketplace distribution; build your flow around a redirect hosted on your verified domain per Create an OAuth app
For n8n-only execution, keep the Zoom OAuth redirect and webhooks on your verified domain then hand off to n8n via HTTP nodes - the key is that Zoom sees only your verified domains
The solution here really depends on your use case so hopefully the info above helps inform you on which solution to use