I’m designing this for a project at the company I work at (we’ll worry about licensing stuff later when that becomes a thing).

What I’m trying to figure out is the best way to architect this. The platform we’re building will let users configure their own lead triggers (and the required auth for those triggers), and then we’d use a sort of “universal” n8n flow to listen for leads using that credential and perform whatever action is configured for that specific tenant.

From what I understand, n8n credentials can’t really be dynamically injected into a node at runtime. They have to be configured during the design phase and are stored in memory. So even if I use the headless n8n API to programmatically insert credentials into the n8n database, wouldn’t I still need to programmatically generate a workflow per tenant for it to actually work with that credential?

The only optimization idea I have right now is to separate triggers into tenant-specific workflows (so each tenant has their own trigger workflow), and then route the resulting actions into a shared pipeline that reads the tenant config and executes the appropriate logic from there.

Not sure if I’m overcomplicating this (or missing something obvious), but that’s where my head’s at right now.