The idea is:
A new “SSO Trigger” node that allows a workflow to start when a user authenticates via a Single Sign-On (SSO) mechanism. This node would present a login page to the user using standard authentication protocols such as OpenID Connect, SAML, Google Login, Microsoft Login, etc.
Once the user is authenticated, the workflow is triggered with access to the authentication token and user information (e.g., email, name, roles). This allows subsequent nodes in the workflow to customize actions or responses based on the identity of the user.
My use case:
This would be useful for building user-facing workflows that require authentication, such as:
- Personalized dashboards or portals
- Access-controlled automations
- User-specific form submissions
- Internal tools or bots that must verify who is accessing them
I think it would be beneficial to add this because:
It would greatly expand n8n’s ability to serve as a platform for building secure and personalized automation interfaces. Many real-world use cases require knowing who the end-user is, and currently there is no built-in way to securely authenticate users within a workflow.
This trigger would enable more advanced and secure use cases without requiring a separate frontend or authentication layer outside of n8n.
Any resources to support this?
- OpenID Connect Documentation
- SAML Specification
- OAuth 2.0 Overview
- Google Identity Platform
- Microsoft Identity Platform
Are you willing to work on this?
Possibly — open to collaborating or helping define the functional specifications.
I have POC workflow to authentify a user with OIDC.