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 various operations on CRM resources, including Opportunities. Specifically, the Get One operation for the Opportunity resource retrieves a single opportunity entity by its unique identifier. This is useful when you need detailed information about a specific sales opportunity, such as its status, value, or related contacts.
Common scenarios include:
- Fetching details of a particular opportunity to display in dashboards or reports.
- Using opportunity data to trigger workflows based on its current state.
- Integrating opportunity information into other systems or processes.
Example: Retrieve an opportunity by its ID to check its current stage before sending a follow-up email.
Properties
| Name | Meaning |
|---|---|
| Opportunity ID | The unique numeric identifier of the opportunity to retrieve. |
Output
The node outputs JSON data representing the requested opportunity entity. The structure typically includes all relevant fields of the opportunity, such as name, status, value, associated contacts, and dates.
If the node supports binary data output (not indicated here), it would be summarized accordingly, but this operation returns only JSON data.
Dependencies
- Requires an API key credential for Easy Redmine with appropriate permissions.
- Needs the Easy Redmine domain URL configured in the node credentials.
- Relies on Easy Redmine's REST API endpoints to fetch opportunity data.
Troubleshooting
Common issues:
- Invalid or missing Opportunity ID will cause the operation to fail.
- Network or authentication errors if API credentials or domain are misconfigured.
- Permission errors if the API key lacks access to the Opportunity resource.
Error messages:
- Errors returned from the API are captured and can include messages like "Opportunity not found" or "Unauthorized".
- If
continueOnFailis enabled, errors are returned as part of the output JSON with anerrorfield. - To resolve, verify the Opportunity ID exists, check API credentials, and ensure network connectivity.