Easy Redmine icon

Easy Redmine

Easy Redmine Operations

Actions37

Overview

This node integrates with the Easy Redmine platform to perform various operations on different resource types, including Personal Contacts. Specifically, the Get One operation for the Personal Contact resource retrieves a single personal contact entity by its unique identifier.

Typical use cases include:

  • Fetching detailed information about a specific personal contact stored in Easy Redmine.
  • Integrating contact details into workflows that require up-to-date contact data.
  • Automating retrieval of contact info for CRM or support ticket enrichment.

For example, you might use this node to get the full profile of a personal contact by providing their ID, then use that data downstream to send personalized emails or update other systems.

Properties

Name Meaning
Personal Contact ID The unique numeric identifier of the personal contact to retrieve.

The node also requires selecting the Resource as "Personal Contact" and the Operation as "Get One" to activate this property.

Output

The output is a JSON array containing one object representing the requested personal contact's data. This object includes all available fields returned by Easy Redmine for that contact, such as name, email, phone number, and any custom fields defined in the system.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "id": 123,
    "firstName": "John",
    "lastName": "Doe",
    "email": "john.doe@example.com",
    "phone": "+1234567890",
    ...
  }
]

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the Easy Redmine instance.
  • The node uses the base URL from the credential configuration to connect to the Easy Redmine API.
  • No additional external dependencies are needed beyond the Easy Redmine API access.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Personal Contact ID will likely result in an error or empty response.
    • Network connectivity problems or incorrect API credentials can cause authentication failures.
    • If the Easy Redmine API changes or is unavailable, the node may fail to retrieve data.

  • Error messages:

    • Errors returned from the API are captured and presented in the node output if "Continue On Fail" is enabled.
    • Typical errors include "Not Found" when the ID does not exist, or "Unauthorized" if credentials are invalid.

  • Resolutions:

    • Verify the Personal Contact ID is correct and exists in Easy Redmine.
    • Check that the API key credential is valid and has sufficient permissions.
    • Ensure the Easy Redmine service is reachable from the n8n environment.

Links and References

Discussion