Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with Easy Redmine to perform operations on various resources such as issues, leads, opportunities, accounts, and more. Specifically, the Account - Get Many operation retrieves multiple account records from Easy Redmine based on optional filtering queries and pagination parameters.
Common scenarios for this node include:
- Fetching a list of accounts for reporting or synchronization with other systems.
- Retrieving filtered subsets of accounts using predefined queries.
- Paginating through large sets of account data efficiently.
For example, a user might use this node to get all accounts matching a specific query (e.g., accounts in a certain region) or to retrieve a limited number of accounts starting from a particular offset for batch processing.
Properties
| Name | Meaning |
|---|---|
| EasyRedmine Accounts Query Name or ID | Choose a predefined query to filter the accounts returned. You can select from a list or specify an ID via expression. |
| Return All | Whether to return all matching results or limit the output to a specified number. |
| Offset | The starting position in the result set from which to begin returning accounts (used if not returning all). |
| Limit (1-100) | Maximum number of account records to return when not returning all. Must be between 1 and 100. |
Output
The node outputs an array of JSON objects representing the retrieved accounts. Each object corresponds to one account entity with its associated fields as provided by Easy Redmine.
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.
Dependencies
- Requires an API key credential for authenticating with the Easy Redmine instance.
- The base URL for API requests is configured from the user's credentials.
- No additional external dependencies beyond the Easy Redmine API and n8n's HTTP request capabilities.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying an invalid query ID or name may result in empty results or errors.
- Requesting too many records without enabling "Return All" may truncate results unexpectedly.
- Using an offset beyond the available data range will return no results.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
- Validation errors on input properties suggest incorrect parameter values; ensure limits and offsets are within allowed ranges.
- Network or API errors may occur if the Easy Redmine server is unreachable or misconfigured.
Resolving these usually involves checking credentials, verifying query IDs, and adjusting pagination parameters.