Overview
The Undb node for n8n allows you to interact with the Undb API, specifically to retrieve a single record from a specified table. The "Record: Get" operation fetches detailed information about a specific record by its ID. This is useful in scenarios where you need to look up or process data for a particular entry in your Undb database, such as retrieving user details, order information, or any other entity stored in Undb.
Practical examples:
- Fetching customer details by their unique record ID for further processing.
- Retrieving a specific order's data to send a notification or update another system.
- Looking up configuration or reference data during an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Authentication | Select the authentication method for connecting to Undb. Options: - Api Token - Auth Api Token |
| Table Name or ID | The ID of the table from which to retrieve the record. You can choose from a list or specify an ID using an expression. |
| Record ID | The unique identifier of the record to retrieve. This field is required for the "Get" operation. |
Output
- The output will be a JSON object containing the fields and values of the requested record from the specified table.
- The structure of the output JSON depends on the schema of your Undb table, but typically includes all columns/fields for the given record.
- No binary data is returned; only structured JSON.
Example output:
{
"id": "rec123",
"name": "John Doe",
"email": "john@example.com",
"createdAt": "2024-06-01T12:34:56Z"
}
Dependencies
- Requires access to the Undb API at
https://demo.undb.com. - An API token or Auth API token credential must be configured in n8n, depending on the selected authentication method.
Troubleshooting
- Invalid operation get: If you see an error like
Invalid operation get, ensure that the "Operation" property is set correctly to "Get". - Missing credentials: If authentication fails, verify that the correct credentials (Api Token or Auth Api Token) are set up in n8n and selected in the node.
- Record not found: If the specified Record ID does not exist, the node may return an error or an empty result. Double-check the Record ID and Table ID.
- Table not found: Ensure the Table Name or ID is correct and accessible with your credentials.