Actions11
Overview
The node provides integration with a recruitment platform's API, specifically managing quiz sessions for candidates. The "Update Quizz Session" operation allows users to modify details of an existing quiz session, such as its name and expiration date. This is useful in scenarios where quiz sessions need to be extended, renamed, or otherwise updated after creation.
Practical examples include:
- Extending the expiration date of a candidate’s quiz session if more time is needed.
- Renaming a session to better reflect its purpose or status.
- Correcting session details without creating a new session.
Properties
Name | Meaning |
---|---|
Session ID * | The unique identifier of the quiz session to update. Required to specify which session to modify. |
Name | The new name for the quiz session. Useful for labeling or renaming the session. |
Expires At | The new expiration date and time for the session, defining when the session will no longer be valid. |
Output
The output contains a JSON object representing the updated quiz session data returned from the recruitment platform's API. This typically includes the session's current state after the update, such as its ID, name, expiration date, and any other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the recruitment platform's Pulse API.
- The node depends on the Pulse API helper utilities bundled within the node's codebase to perform HTTP requests.
- Proper configuration of the API credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or expired Session ID will result in errors indicating the session could not be found.
- Incorrectly formatted dates for the "Expires At" property may cause validation errors.
- Missing required properties (e.g., Session ID) will prevent the operation from executing.
Error messages:
"The operation "updateQuizzSession" is not supported for resource "quizzSessions"!"
— indicates a misconfiguration of the operation or resource selection.- API authentication errors suggest issues with the provided API key or credentials.
- Network or connectivity errors may occur if the Pulse API service is unreachable.
To resolve these:
- Verify that the Session ID corresponds to an existing session.
- Ensure date/time values are correctly formatted according to ISO 8601 standards.
- Confirm API credentials are valid and have sufficient permissions.
- Check network connectivity and API endpoint availability.
Links and References
- Pulse API Documentation (Replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- General best practices for Date and Time Handling