Actions11
Overview
This node interacts with the Pulse API to manage recruitment-related data, specifically focusing on "Candidates Quizz Sessions" when the resource is set accordingly. The "Get Quizz Session" operation retrieves detailed information about a specific quiz session by its ID. This is useful in scenarios where you want to fetch the status, results, or details of a candidate's quiz session during the recruitment process.
Practical examples include:
- Fetching quiz session details to review candidate performance.
- Integrating quiz session data into a broader recruitment dashboard.
- Automating follow-up actions based on quiz completion status.
Properties
| Name | Meaning |
|---|---|
| Session ID * | The unique identifier of the quiz session to retrieve. This is a required string input. |
| Include | Optional resources to include in the response. Currently supports including "Quizzes". |
Output
The output JSON contains the detailed data of the requested quiz session. This typically includes session metadata such as session ID, candidate info, quiz details (if included), status, timestamps, and possibly results or scores depending on the API response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API.
- The node depends on the Pulse API service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing Session ID will cause errors; ensure the session ID is correct and exists.
- Network or authentication failures if the API key is invalid or expired.
- Attempting to include unsupported resources in the "Include" property may result in incomplete data or errors.
Error messages:
"The operation "getQuizzSessionById" is not supported for resource "quizzSessions"!"indicates a misconfiguration or typo in operation/resource selection.- API errors returned from Pulse API will be passed through; check the error message for details like "Session not found" or "Unauthorized".
To resolve these:
- Verify the session ID correctness.
- Confirm API credentials are valid and have necessary permissions.
- Use only supported options in the "Include" field.
Links and References
- Pulse API documentation (refer to your internal or public API docs for detailed schema and usage).
- n8n documentation on creating and using custom nodes for API integrations.