GateKit icon

GateKit

Universal messaging gateway - send messages across multiple platforms
Join our community

Actions51

Overview

The node provides integration with the GateKit universal messaging gateway API, enabling various operations across multiple resources such as API keys, authentication, identities, members, messages, platforms, projects, platform logs, and webhooks. Specifically, for the Auth - Login operation, this node allows users to authenticate by logging in with an email address and password. This is useful for workflows that require user authentication to obtain access tokens or session information before performing further actions within the GateKit platform.

Practical examples include:

  • Automating login to GateKit to retrieve a session token for subsequent API calls.
  • Validating user credentials as part of a workflow that manages user sessions or permissions.
  • Integrating GateKit authentication into broader automation pipelines requiring secure access.

Properties

Name Meaning
Email address The user's email address used for login authentication.
Password The user's password used for login authentication.

These properties are required inputs for the login operation under the Auth resource.

Output

The node outputs JSON data representing the response from the GateKit API after attempting to log in. This typically includes authentication tokens, user details, or error messages depending on the success or failure of the login attempt.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the GateKit API.
  • The node uses the base URL provided by the API key credential's configuration.
  • The login request is made via HTTP POST to the /api/v1/auth/login endpoint with email and password passed as query string parameters.

Troubleshooting

  • Invalid credentials error: If the email or password is incorrect, the API will return an authentication failure. Verify the credentials and try again.
  • Missing or invalid API key: Ensure the API key credential is correctly set up in n8n and has appropriate permissions.
  • Network or connectivity issues: Confirm that the API URL is reachable from the n8n environment.
  • Password requirements: Although not explicitly stated here, ensure the password meets any complexity requirements enforced by GateKit (e.g., minimum length, character types).
  • Unexpected API responses: Check the API documentation or logs for detailed error messages if the login fails unexpectedly.

Links and References

Discussion