Actions37
- Issue Actions
- Lead Actions
- Opportunity Actions
- Account Actions
- Attendance Actions
- Personal Contact Actions
- Time Entry Actions
- User Actions
Overview
This node integrates with the Easy Redmine platform to perform various operations on different resources. Specifically, for the Personal Contact resource with the Update operation, it allows users to update details of an existing personal contact in their Easy Redmine account.
Typical use cases include:
- Modifying contact information such as first name, last name, email, or job title.
- Updating associations like Account ID or Partner ID linked to the personal contact.
- Adding or changing custom fields associated with the contact.
For example, a user might automate updating contact details when receiving new information from a CRM system or after a form submission.
Properties
| Name | Meaning |
|---|---|
| Personal Contact ID | The unique numeric identifier of the personal contact to update. |
| Update Fields | A collection of fields to update on the personal contact. Includes: |
| - Account ID | Numeric ID of the associated account. |
| - Partner ID | Numeric ID of the associated partner. |
| - First Name | Contact's first name (string). |
| - Last Name | Contact's last name (string). |
| Contact's email address (string). | |
| - Job Title | Contact's job title or position (string). |
| - Custom Fields | Multiple custom fields to update, each with: |
| -- ID | Numeric identifier of the custom field. |
| -- Value | String value to set for the custom field. |
Output
The node outputs JSON data representing the updated personal contact entity as returned by the Easy Redmine API. This typically includes the updated fields and any metadata provided by the API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the contact, but this is not applicable for the update operation on personal contacts.
Dependencies
- Requires an active connection to Easy Redmine via an API key credential configured in n8n.
- The node uses the base URL from the credential configuration to send requests.
- No additional external dependencies are required beyond the Easy Redmine API access.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Personal Contact ID will result in errors indicating the contact was not found.
- Missing required authentication or incorrect API credentials will cause authorization failures.
- Invalid data types for fields (e.g., string instead of number) may cause validation errors.
Error Messages:
- Errors returned from the Easy Redmine API are captured and presented. For example, "Contact not found" or "Invalid field value".
- If the node is set to continue on failure, error messages are included in the output JSON under an
errorproperty.
Resolution Tips:
- Verify that the Personal Contact ID exists in Easy Redmine.
- Ensure API credentials are correctly configured and have sufficient permissions.
- Validate input data types and formats before running the node.