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 Opportunity records based on specified criteria. The "Get Many" operation for the Opportunity resource allows users to fetch a list of opportunities, optionally filtered by a saved query, and supports pagination controls such as offset and limit.
Common scenarios where this node is beneficial include:
- Extracting a batch of sales opportunities for reporting or analysis.
- Synchronizing opportunity data from Easy Redmine into other systems.
- Automating workflows that require processing multiple opportunities at once.
For example, a user might configure the node to return all opportunities matching a specific saved query that filters for high-value deals, or retrieve only the first 50 opportunities starting from an offset of 100.
Properties
| Name | Meaning |
|---|---|
| EasyRedmine Opportunities Query Name or ID | Choose a predefined query to filter the opportunities returned. Options are loaded dynamically or can be specified by ID using expressions. |
| Return All | Boolean flag indicating whether to return all matching results (true) or limit the number of results (false). |
| Offset | Number specifying the starting point in the result set (used when Return All is false). |
| Limit (1-100) | Maximum number of results to return when Return All is false. Must be between 1 and 100. |
Output
The node outputs an array of JSON objects representing the retrieved Opportunity records. Each object corresponds to one opportunity entity fetched from Easy Redmine, containing its fields and values as provided by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Easy Redmine via an API key credential.
- The node uses the base URL configured in the credentials to make REST API calls.
- The "EasyRedmine Opportunities Query Name or ID" property depends on dynamically loaded options from Easy Redmine queries.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying an invalid query ID or name may result in no data returned or errors.
- Setting a limit outside the allowed range (less than 1 or greater than 100) will likely cause validation errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
- "No results found" may mean the query filter does not match any opportunities.
- Rate limiting or server errors from Easy Redmine should be retried after some delay.