ElevenLabs icon

ElevenLabs

WIP

Actions13

Overview

The "Get User Info" operation for the "User" resource in this custom n8n node retrieves information about the authenticated user from the ElevenLabs API. This node is particularly useful for workflows that need to access or display user profile details, such as account status, usage statistics, or other personal data provided by ElevenLabs.

Common scenarios:

  • Displaying current user information in a dashboard.
  • Verifying user identity before performing further actions.
  • Logging or auditing user activity within an automation workflow.

Practical example:
You might use this node at the start of a workflow to fetch and log the user's account details before proceeding with operations that require user-specific context.

Properties

Display Name Type Meaning
This node is currently in BETA and under active development.
Visit this page for more information or contact the n8Ninja on X.

To support my work, please share this youtube video 🥷🙏
Latest update includes Stitching.		 notice Informational notice about the node's beta status, links for feedback/support, and recent updates.

Output

The output will be a json object containing the user information retrieved from the ElevenLabs API. The exact structure depends on the ElevenLabs API response for the user info endpoint, but typically it may include fields such as:

{
  "id": "string",
  "name": "string",
  "email": "string",
  "subscription": {
    "plan": "string",
    "status": "string"
  },
  "usage": {
    "characters_used": number,
    "characters_limit": number
  }
}

Note: The actual fields may vary based on the ElevenLabs API.

Dependencies

  • External Service: Requires access to the ElevenLabs API.
  • API Key: You must configure valid ElevenLabs API credentials in n8n (credential type: elevenLabsApi).
  • n8n Configuration: No additional configuration required beyond setting up the credentials.

Troubleshooting

Common issues:

  • Invalid or missing API key: If the API key is not set or incorrect, the node will fail to authenticate with ElevenLabs.
  • Network errors: Connectivity issues between n8n and the ElevenLabs API can cause failures.
  • API changes: As the node is in BETA, breaking changes in the ElevenLabs API or the node itself may occur.

Error messages and resolutions:

  • "401 Unauthorized": Check that your ElevenLabs API credentials are correct and have sufficient permissions.
  • "404 Not Found": Ensure the user exists and the endpoint URL is correct.
  • "429 Too Many Requests": You have hit the rate limit; wait and try again later.

Links and References

Discussion