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 - Create operation, it allows users to create a new personal contact record in Easy Redmine. This is useful for automating the addition of contacts into your CRM or project management system directly from workflows.
Typical use cases include:
- Automatically adding new leads or contacts collected from web forms.
- Syncing contacts from other systems into Easy Redmine.
- Bulk importing personal contacts as part of onboarding or data migration processes.
Properties
| Name | Meaning |
|---|---|
| First Name | The first name of the personal contact to be created. |
| Last Name | The last name of the personal contact. |
| The email address of the personal contact. | |
| Create Fields | Additional optional fields to specify more details about the personal contact: |
| Account ID | Numeric ID of the associated account. |
| Partner ID | Numeric ID of the associated partner. |
| Job Title | Job title or position of the personal contact. |
| Custom Fields | A collection of custom fields where each field has an ID and a corresponding value string. |
Output
The node outputs JSON data representing the newly created personal contact entity as returned by the Easy Redmine API. This typically includes the unique identifier of the contact, the provided fields, and any additional metadata assigned by the system.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the contact, but this operation focuses on JSON data only.
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 other external dependencies are required.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid field values (e.g., non-numeric Account ID) may result in API validation errors.
- Network connectivity issues can prevent successful API calls.
Error Messages:
- Errors returned from the API are captured and presented in the node output. They often include descriptive messages such as "Invalid field value" or "Missing required field."
- If the node is set to continue on failure, errors for individual items will be included in the output JSON under an
errorproperty.
Resolution Tips:
- Verify that all required fields are correctly filled.
- Ensure the API key credential is valid and has sufficient permissions.
- Check network connectivity and Easy Redmine service status.