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 more. Specifically, for the Lead - Create operation, it allows users to create a new lead entity in Easy Redmine by specifying details like company name, description, and custom fields.
This node is beneficial when automating CRM workflows, such as adding new sales leads from form submissions, marketing campaigns, or other data sources directly into Easy Redmine without manual entry.
Practical example: Automatically creating a lead in Easy Redmine whenever a new contact form is submitted on a website, including custom metadata fields relevant to the business.
Properties
| Name | Meaning |
|---|---|
| Create Options | Collection of options to define the lead's details: |
| - Company Name | The name of the lead's company (string). |
| - Description | A textual description of the lead (string). |
| - Custom Fields | Multiple custom fields, each with an ID (number) and a corresponding value (string). |
Output
The node outputs JSON data representing the created lead entity as returned by the Easy Redmine API. This typically includes the newly created lead's properties such as its unique identifier, company name, description, and any custom fields set during creation.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to Easy Redmine via an API key credential.
- The node expects the Easy Redmine domain URL configured in credentials.
- The node uses HTTP requests with JSON payloads to communicate with the Easy Redmine API.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid custom field IDs or values may result in API errors.
- Network connectivity problems 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 about what went wrong (e.g., "Invalid custom field ID").
- If the node is set to continue on failure, errors for individual items are returned as JSON objects with an
errorproperty describing the issue.
Resolutions:
- Verify that the API key and domain URL are correctly configured.
- Ensure all required fields are provided and valid.
- Check network connectivity and firewall settings.
- Review Easy Redmine API documentation for correct custom field usage.