Dalil AI icon

Dalil AI

Consume Dalil AI API

Pipeline → Update

AI-generated

Overview

This node operation updates a record within a specified pipeline in the Dalil AI system. It allows users to select a pipeline and a specific record within that pipeline to update various fields, including custom properties unique to the pipeline. The node supports specifying the depth of nested related objects to include in the response, enabling detailed data retrieval.

Use Case Examples

  1. Updating the status or stage of a sales opportunity within a Sales Pipeline.
  2. Modifying custom fields such as dates, amounts, or statuses for a recruitment process record.
  3. Adjusting nested related objects data by setting the depth parameter to include related entities.

Properties

Name Meaning
Select Pipeline Name or ID Choose which pipeline contains the record to update, either by selecting from a list or specifying an ID via expression.
Record Name or ID Select the specific pipeline record to update, either from a list or by specifying an ID via expression.
Update Fields Fields to update on the selected pipeline record, including pipeline-specific custom properties such as stages, statuses, amounts, dates, and other custom fields.
Depth Name or ID Level of nested related objects to include in the response: 0 for record only, 1 for record plus direct relations, 2 for record plus relations and their relations.

Output

JSON

  • json - The updated pipeline record data returned from the Dalil AI API, including any nested related objects as specified by the depth parameter.

Dependencies

  • Dalil AI API with appropriate API key credentials

Troubleshooting

  • Invalid pipeline selection error if the selected pipeline parameter is not a valid JSON string representing a pipeline.
  • Errors processing custom properties if the property metadata is invalid or the value format does not match the expected field type.
  • API request failures due to network issues or incorrect API credentials.
  • Ensure the depth parameter is set correctly to avoid unexpected data retrieval results.

Discussion