HideMail icon

HideMail

Interact with HideMail API - Create and manage email aliases

Actions7

Overview

This node interacts with the HideMail API to create and manage email aliases. Specifically, the "Create A Token" operation under the "Endpoints" resource allows users to generate an authentication token by providing their email, password, and device name. This token can then be used for subsequent authenticated requests to the HideMail service.

Common scenarios where this node is beneficial include automating user authentication workflows, integrating HideMail alias management into larger automation pipelines, or securely generating tokens for session management without manual intervention.

Practical example: A user wants to programmatically log in to HideMail from an automation workflow, obtain a token, and then use that token to create or manage email aliases dynamically.

Properties

Name Meaning
Email The user's email address used for authentication.
Password The user's password associated with the email for authentication.
Device Name The name of the device or client requesting the token (e.g., "Raycast").

Output

The node outputs JSON data containing the response from the HideMail API after attempting to create a token. This typically includes the authentication token and possibly related metadata such as expiration time or user details.

If the API returns binary data (not indicated here), it would represent raw response content, but based on the context, output is expected to be JSON only.

Dependencies

  • Requires an API key credential for authenticating requests to the HideMail API.
  • The node uses the base URL and API token provided via credentials configured in n8n.
  • The HTTP request headers include Accept: application/json, Content-Type: application/json, and an Authorization header with a Bearer token derived from credentials.

Troubleshooting

  • Invalid Credentials: If the email or password is incorrect, the API will likely return an authentication error. Verify the credentials are correct.
  • Missing Device Name: The device name is required; omitting it may cause the request to fail.
  • API Connectivity Issues: Ensure the base URL and network connectivity to the HideMail API are correct.
  • Authorization Errors: Make sure the API token credential is valid and has necessary permissions.
  • Error Messages: Common errors might include 401 Unauthorized (invalid credentials), 400 Bad Request (missing parameters), or 500 Internal Server Error (server issues). Check the error message returned in the JSON response for specifics.

Links and References

Discussion