Pulse Talent icon

Pulse Talent

Talent resource from Pulse API

Actions32

Overview

The node interacts with the "Talent Quizz Sessions" resource of the Pulse API, specifically supporting the operation to share a Talent Quiz Session link. This operation generates or retrieves a shareable URL for a given quiz session, allowing users to distribute the quiz easily.

This node is beneficial in scenarios where you want to automate the distribution of talent assessment quizzes, for example:

  • Sending quiz links to candidates automatically after scheduling an interview.
  • Sharing quiz sessions with team members or external evaluators.
  • Integrating quiz sharing into recruitment workflows or onboarding processes.

Properties

Name Meaning
Session ID * The unique identifier of the quiz session for which the shareable link will be generated or retrieved.

Output

The output contains a JSON object representing the result of the share link operation. Typically, this includes the shareable URL of the Talent Quiz Session. The exact structure depends on the API response but generally provides at least:

  • A URL string that can be used to access or share the quiz session externally.

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 helper utilities bundled within the node's codebase.
  • Proper configuration of the API credentials in n8n is necessary to successfully call the Pulse API endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing Session ID: Ensure the Session ID provided exists and is correct.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network or API downtime: Check connectivity and Pulse API status.

  • Error messages:

    • "The operation "shareTestLink" is not supported for resource "quizzSessions"!" — This indicates a mismatch between the selected operation and resource; ensure both are correctly set.
    • Errors returned from the API (e.g., 404 Not Found) usually mean the session does not exist or is inaccessible.

  • Resolution tips:

    • Double-check input parameters.
    • Confirm API credentials and permissions.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion