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 different resources such as Issues, Leads, Opportunities, Accounts, and others. Specifically, for the Lead - Update operation, it allows users to update details of an existing lead in Easy Redmine.
Typical use cases include:
- Updating company information or description for a lead after receiving new data.
- Modifying custom fields associated with a lead to reflect changes in business requirements or client information.
- Automating lead updates based on external triggers or workflows, ensuring CRM data stays current.
For example, you might use this node to update the "Company Name" and add a note in the "Description" field for a lead when a sales representative provides new information.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique numeric identifier of the lead to update. |
| Update Fields | A collection of fields to update on the lead: |
| Company Name | The name of the company associated with the lead. |
| Description | A textual description or notes about the lead. |
| Custom Fields | Multiple custom fields can be updated, each specified by an ID and its new value. |
Output
The node outputs JSON data representing the updated lead entity as returned by the Easy Redmine API. This typically includes the lead's updated properties such as ID, company name, description, and any custom fields that were modified.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Easy Redmine via an API key credential configured in n8n.
- The node uses the base URL from the provided credentials to make REST API calls to Easy Redmine.
- No additional external dependencies are required beyond the Easy Redmine API access.
Troubleshooting
Common issues:
- Invalid or missing Lead ID: Ensure the Lead ID corresponds to an existing lead in Easy Redmine.
- Insufficient permissions: The API key used must have rights to update leads.
- Incorrect custom field IDs or values may cause the update to fail.
Error messages:
- Errors returned from the API will be surfaced, often including validation errors for fields.
- If the node fails and "Continue On Fail" is disabled, execution stops with an error referencing the problematic item.
- To resolve, verify input parameters, especially Lead ID and custom field IDs, and confirm API credentials.
Links and References
- Easy Redmine API Documentation (for detailed API endpoints and field definitions)
- n8n documentation on Creating Custom Nodes