YOOV Lancode icon

YOOV Lancode

Interact with Lancode API
Join our community

Actions9

Overview

The YOOV Lancode node for n8n allows you to interact with the YOOV Lancode API, specifically to update an existing item (row) in a worksheet. The "Item - Update" operation is used when you need to modify the data of a specific row within a worksheet, such as updating text, numbers, dates, selections, members, or JSON fields.

Common scenarios:

  • Automating updates to records in a YOOV Lancode worksheet based on triggers from other systems.
  • Bulk-updating worksheet items as part of a workflow.
  • Integrating external data sources and synchronizing changes into YOOV Lancode.

Practical example:
If you have a CRM system and want to update customer information in a YOOV Lancode worksheet whenever a change occurs in your CRM, you can use this node to map and update the relevant fields automatically.

Properties

Name Meaning
Worksheet ID The unique identifier of the worksheet containing the item (row) you wish to update. Required to specify which worksheet to operate on.
Row ID The unique identifier of the row (item) to update within the worksheet.
Text Fields One or more text-based fields to update. For each, specify:
- Field Name or ID: Select or enter the field.
- Value: The new text value.
Number Fields One or more numeric fields to update. For each, specify:
- Field Name or ID: Select or enter the field.
- Value: The new number value.
Date/Time Fields One or more date/time fields to update. For each, specify:
- Field Name or ID: Select or enter the field.
- Value: The new date/time value.
List Fields One or more list (selection) fields to update. For each, specify:
- Field Name or ID: Select or enter the field.
- Value Name or ID: The new selection value.
Member Fields One or more member fields to update. For each, specify:
- Field Name or ID: Select or enter the field.
- Value: Can be a single value or an array of IDs (e.g., ["id1", "id2"]).
JSON Fields One or more JSON fields to update. For each, specify:
- Field Name or ID: Enter the field.
- Value Name or ID: The new JSON value.
Use Raw Output If enabled, returns the raw response from the API instead of a simplified version.

Output

  • The output is a JSON object representing the updated item (row) in the worksheet.
  • The structure of the output will reflect the fields present in the worksheet and their updated values.
  • If "Use Raw Output" is enabled, the output will match the raw API response format.
  • In case of errors and if "Continue On Fail" is enabled, the output will include an error property with the error message.

Example output:

{
  "id": "row_123",
  "fieldA": "Updated Value",
  "fieldB": 42,
  "fieldC": "2024-06-01T12:00:00Z"
}

Dependencies

  • External Service: Requires access to the YOOV Lancode API.
  • API Credentials: You must configure the lancodeApi credential in n8n, including the API hostname and authentication details.
  • n8n Configuration: No special environment variables are required beyond standard credential setup.

Troubleshooting

Common issues:

  • Missing or incorrect Worksheet ID / Row ID: Ensure both are provided and valid; otherwise, the node will not perform the update.
  • Field mapping errors: If a field name or ID does not exist in the worksheet, the update may fail.
  • Invalid data types: Supplying a string where a number is expected, or vice versa, can cause errors.
  • Authentication errors: Invalid or missing credentials will prevent the node from connecting to the YOOV Lancode API.

Error messages:

  • "Cannot find worksheet": Check that the Worksheet ID is correct and accessible.
  • "Row not found": Verify the Row ID exists in the specified worksheet.
  • "Field validation failed": Ensure all field values match the expected data types and formats.
  • "Authentication failed": Recheck your API credentials in n8n.

How to resolve:

  • Double-check all IDs and field mappings.
  • Use the "Load Options" feature to select valid fields.
  • Review the API credentials configuration in n8n.

Links and References

Discussion