The shape of the build
We wanted every Reevez customer to get a private, isolated n8n deployment without us managing one VPS per tenant. The architecture: shared n8n instance, deterministic webhook paths keyed by user-workflow ID, credentials encrypted at rest with AES-256-GCM and only decrypted inside the n8n execution context via an internal-API-key-protected endpoint.
Where Bull queues earn their keep
Activating a new workflow on n8n can take 5–15s (creating the workflow, attaching credentials, calling /activate). If we did that inline on the user's purchase request, half the HTTP requests would time out.
Instead, the purchase request returns a 202 immediately and a Bull job picks up the activation in the background. Failures retry with exponential backoff three times before the user is notified. The customer sees "Setting up your workflow..." → "Active" within seconds.
What we kept
This engine now powers every workflow we ship — both off-the-shelf templates (the public library at /workflows) and one-off custom builds for paying customers. Adding a new workflow is a single PR: drop the n8n JSON export, declare integrations + pricing, push to main.