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 retrieve multiple Lead records based on a specified query filter. It is designed to fetch many leads at once, supporting pagination and filtering through predefined or custom queries.
Common scenarios where this node is beneficial include:
- Exporting or syncing lead data from Easy Redmine into other systems.
- Generating reports or dashboards that require bulk lead information.
- Automating workflows that depend on filtered lists of leads, such as targeted marketing campaigns or sales follow-ups.
For example, a user might configure the node to get all leads matching a specific saved query in Easy Redmine, then pass those leads downstream for further processing or notification.
Properties
| Name | Meaning |
|---|---|
| EasyRedmine Leads Query Name or ID | Choose a predefined query or specify its ID to filter which leads are returned. This allows retrieving only leads matching certain criteria. |
| Return All | Boolean flag indicating whether to return all matching leads or limit the number of results. |
| Offset | Number specifying the starting point (offset) in the result set when not returning all results. Useful for pagination. |
| Limit (1-100) | Maximum number of lead 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 leads. Each object corresponds to a single lead 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 deals solely with JSON lead data.
Dependencies
- Requires an API authentication credential configured in n8n to connect to the Easy Redmine instance.
- The base URL for API requests is taken from the credential's domain configuration.
- No additional external dependencies beyond the Easy Redmine API.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Specifying a non-existent query ID or name may result in empty results or errors.
- Requesting too many records without enabling "Return All" may truncate results unexpectedly.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
- Typical error messages include authentication errors, invalid query references, or rate limiting notices.
Resolutions:
- Verify API credentials and permissions.
- Confirm the query ID or name exists and is accessible.
- Use pagination parameters (Offset and Limit) appropriately or enable "Return All" for full datasets.
- Check network connectivity and retry if transient issues occur.