Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with the Easy Redmine platform to perform various operations on different resources such as issues, leads, opportunities, accounts, attendances, personal contacts, time entries, and users. Specifically, for the Account resource with the Get One operation, the node retrieves a single account entity by its unique identifier.
Typical use cases include:
- Fetching detailed information about a specific account in Easy Redmine for further processing or reporting.
- Integrating account data into workflows that require up-to-date customer or company information.
- Automating retrieval of account details before performing updates or adding comments.
Example: You want to get the details of an account with ID 12345 to check its status or related metadata before triggering other workflow steps.
Properties
| Name | Meaning |
|---|---|
| Account ID | The unique numeric identifier of the account to retrieve. This is required to specify which account to fetch. |
Output
The node outputs JSON data representing the retrieved account entity. The structure corresponds to the account object as defined by Easy Redmine's API, typically including fields such as account name, contact details, address, custom fields, and other metadata.
If multiple items are processed, each output item corresponds to one account entity fetched.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to an Easy Redmine instance via an API key credential.
- The node expects the base URL of the Easy Redmine API to be configured in the credentials.
- Proper permissions on the API key to read account data are necessary.
Troubleshooting
Common Issues:
- Invalid or missing Account ID: The node requires a valid numeric ID; ensure it is provided and correct.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network or connectivity problems: Ensure the Easy Redmine domain is reachable from n8n.
Error Messages:
- Errors returned from the API will be surfaced, often containing messages about invalid IDs or permission issues.
- If the node fails and "Continue On Fail" is disabled, execution stops with an error referencing the problematic item index.
- When "Continue On Fail" is enabled, errors are returned as part of the output JSON with an
errorfield describing the issue.
Links and References
- Easy Redmine Official Website
- Easy Redmine API Documentation (for detailed API schema and endpoints)
- n8n Documentation (for general usage of nodes and credentials)