Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node operation creates a User Identity JWT (JSON Web Token) based on provided identity information. It is useful in scenarios where you need to generate a secure token representing a user's identity, which can then be used for authentication or authorization purposes in other systems or services.
Practical examples include:
- Generating a JWT for a user identified by their email address to authenticate API requests.
- Creating a JWT for a user identified by their mobile phone number to enable secure access to mobile applications or services.
Properties
| Name | Meaning |
|---|---|
| Identity Type | The type of identity information. Options are: EMAIL or MOBILE PHONE NUMBER. Determines the format and validation of the identity value. |
| Identity | The actual identity information. Must be a valid email address if Identity Type is EMAIL, or a valid phone number in E.164 format if MOBILE PHONE NUMBER. |
Output
The node outputs JSON data containing the generated User Identity JWT. This JWT represents the encoded identity information and can be used for secure authentication or authorization workflows.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the external service that generates the JWT.
- The node interacts with an external API endpoint (base URL shown as a placeholder in the bundled code).
- Proper configuration of the API credentials within n8n is necessary for successful execution.
Troubleshooting
- Invalid Identity Format: If the identity value does not conform to the expected format (valid email or E.164 phone number), the API may reject the request. Ensure the input matches the required format.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key or token is correctly configured.
- API Endpoint Issues: Network problems or incorrect base URL settings can lead to connection errors. Confirm the endpoint URL and network accessibility.
- Unexpected Response: If the API returns an error or unexpected response, check the input parameters and consult the API documentation for required fields and constraints.
Links and References
- E.164 Phone Number Format
- General JWT Information: https://jwt.io/introduction/
- For more details on configuring API credentials in n8n, refer to the official n8n documentation.