Overview
This node interacts with a remote API service to manage various data entries related to the "Chat GPT" resource. Specifically, for the UPDATE operation, it updates the description and optionally adds markup tags or timeline information to an existing entry identified by its ID.
Common scenarios where this node is useful include:
- Updating metadata or descriptions of entities such as agencies, projects, features, or tags in a centralized system.
- Adding additional contextual markup (tags or timeline markers) to entries for better categorization or tracking.
- Automating updates to project-related data within workflows that integrate with the external API.
Practical example:
- A user wants to update the description of a specific project tag and mark it with a custom tag number or timeline status to reflect progress or categorization changes.
Properties
| Name | Meaning |
|---|---|
| Entry | The type of entity to update. Options: Agency, Business Category, Country, Feature, Project, Services Category, Tags. |
| ID | The unique identifier of the entry to update. |
| Description | The new description text to set for the entry. |
| Additional Markup | Optional extra data to add when updating: |
| - Mark With Tag | A numeric tag to associate with the entry. |
| - Mark With Timeline | A string representing a timeline status or marker (default is "done"). |
Output
The node outputs a JSON array with one object indicating the result of the update operation:
- On success:
{ "status": "done" } - On failure:
{ "status": false }
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential to authorize requests.
- Makes HTTP POST requests to
https://data2.cloodo.com/api/user/execProjectErp/to perform updates. - Uses the Axios library for HTTP communication.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authorization failures.
- Providing an incorrect or non-existent ID will likely result in unsuccessful updates.
- Network connectivity problems can prevent reaching the API endpoint.
Error messages and resolutions:
- If the response does not contain a successful status, the node returns
{ status: false }. Check credentials and input parameters. - Ensure the "Entry" value matches one of the supported options; otherwise, the API may reject the request.
- Verify that the "ID" corresponds to an existing record in the external system.
- If the response does not contain a successful status, the node returns
Links and References
- Axios HTTP client
- External API documentation is not included in the source but would be necessary for detailed usage.