Hi @Eric_Hans
Short answer: no, this isn’t supported in n8n right now.
SSO (SAML) in n8n is only used to authenticate users into the UI. The SSO token or session is not exposed to workflows or custom nodes, and it can’t be reused for node authentication.
Because of that, nodes must always use their own credentials (API keys, OAuth, etc.) configured in n8n. This separation is intentional for security and execution consistency.
If you need user context, the usual workaround is to pass the user identity explicitly (like email or userId) to the workflow and let the external service handle authorization.