Overview
This node interacts with Nimma API to perform CRUD operations on objects within specified applications and models. It supports listing objects, retrieving a single object by ID, creating new objects, updating existing objects by ID, and deleting objects by ID. This node is useful for automating data management tasks in Nimma, such as updating records in a company database or managing application-specific data models.
Use Case Examples
- Updating a company record by specifying the app name, model name, object ID, and the updated data in JSON format.
- Creating a new object in a specified model by providing the app name, model name, and object data.
Properties
| Name | Meaning |
|---|---|
| App Name | The name of the application where the model resides, used to construct the API endpoint. |
| Model Name | The name of the model within the application to target for the operation. |
| ID | The unique identifier of the object to get, update, or delete. |
| Body (JSON) | The JSON-formatted request body used for creating or updating an object. |
Output
JSON
json- The JSON response from the Nimma API representing the object(s) returned or affected by the operation.
Dependencies
- Requires an API authentication token or header obtained via a helper function to authorize requests to the Nimma API.
Troubleshooting
- Ensure the App Name and Model Name are correctly specified to avoid 404 errors from the API.
- Verify that the ID provided exists when performing get, update, or delete operations to prevent errors.
- Check the JSON body format for create and update operations to avoid malformed request errors.
- Handle unknown operation errors by ensuring the operation parameter is one of the supported values: list, get, create, update, delete.