Actions101
- š¤ Chatting Actions
- š„ļø Sessions Actions
- š Auth Actions
- š¼ļø Screenshot Actions
- š¢ Channels Actions
- š¢ Status Actions
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ Groups Actions
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
Overview
This node handles the authorization of a code for a session in an authentication workflow. It is useful in scenarios where a user needs to authorize access by providing a code, such as OAuth or similar authentication mechanisms. For example, it can be used to complete the authorization step after a user receives a code from an external service.
Use Case Examples
- Authorizing a user session by submitting an authorization code received via email or SMS.
- Completing OAuth authorization by sending the received authorization code to the service to obtain access tokens.
Properties
| Name | Meaning |
|---|---|
| Session | The name of the session to be authorized, identifying the authentication context. |
| Code | The authorization code to be submitted for the session authorization process. |
| Request Options | Additional HTTP request options such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
authorizationResult- The result of the authorization process, typically including tokens or status information.
Dependencies
- Requires an API key or authentication token to interact with the authorization service.
Troubleshooting
- Ensure the provided authorization code is correct and has not expired.
- Check network connectivity and proxy settings if requests fail.
- If SSL errors occur, consider enabling the option to ignore SSL issues, but be aware of security risks.
- Timeout errors may require increasing the timeout setting in request options.