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 manage various resources, including Accounts. Specifically, the Account Create operation allows users to create a new account record in Easy Redmine. This is useful for automating CRM workflows, such as adding new customer accounts or business entities directly from n8n without manual data entry.
Typical use cases include:
- Automatically creating accounts when a new lead is qualified.
- Syncing account data from other systems into Easy Redmine.
- Bulk creation of accounts based on external triggers or batch processes.
Properties
| Name | Meaning |
|---|---|
| Industry ID | Numeric identifier representing the industry classification of the account |
| Name | The name of the account (account name) |
| Accounts Type ID | Numeric ID indicating the type/category of the account |
| Account Manager ID | Numeric ID of the user assigned as the account manager |
| External Account Manager ID | Numeric ID for an external account manager |
| Account Status ID | Numeric ID representing the current status of the account |
| Account Level ID | Numeric ID indicating the level or tier of the account |
| Author ID | Numeric ID of the author who created the account |
| Account Opened | Date and time when the account was opened |
| Account Closed | Date and time when the account was closed |
| Customer Left Reason ID | Numeric ID explaining why the customer left |
| Custom Fields | Collection of custom fields, each with an ID and string value |
Billing Fields (accountPrimaryBillingCreateOptions)
| Name | Meaning |
|---|---|
| Company Name | Name of the billing company |
| Street | Billing street address |
| City | Billing city |
| Country Code | ISO country code |
| Country Division | Subdivision or state code |
| Postal Code | Postal or ZIP code |
| Billing contact email | |
| Telephone | Billing phone number |
| VAT Number | VAT identification number |
| VAT Rate | VAT rate percentage |
| Bank Account Number | Bank account number |
| IBAN | International Bank Account Number |
| Variable Symbol | Variable symbol used for payments |
| SWIFT | SWIFT/BIC code |
| BIC | Bank Identifier Code |
Contact Fields (accountContactBillingCreateOptions)
Same structure and meaning as Billing Fields but for contact information related to the account.
Output
The node outputs JSON data representing the newly created account entity as returned by the Easy Redmine API. This typically includes all the properties of the account, such as IDs, names, statuses, dates, and any custom fields set during creation.
If the API supports binary data output (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires an active connection to Easy Redmine via an API key credential configured in n8n.
- The node uses the base URL provided in the credentials to make REST API calls.
- No additional external dependencies are required beyond the Easy Redmine API access.
Troubleshooting
- Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid field values (e.g., non-numeric IDs where numbers are expected) may result in API validation errors.
- Required fields not set (like account name) can cause the API to reject the request.
- Error messages:
- Authentication errors usually indicate incorrect or expired API tokens.
- Validation errors from the API will list which fields are problematic; ensure all required fields are correctly formatted.
- Network or connectivity issues may cause timeouts or unreachable host errors.
- Resolution tips:
- Verify API credentials and permissions.
- Double-check input property types and required fields.
- Use the node's error output to identify specific API error messages.
Links and References
- Easy Redmine Official Website
- Easy Redmine API Documentation
- n8n Documentation - for general node usage and credential setup