Actions40
- Company Actions
- Note Actions
- Note Relation Actions
- Opportunity Actions
- Person Actions
- Pipeline Actions
- Task Actions
- Task Relation Actions
Overview
The "Pipeline - Update" operation in this node allows users to update a specific record within a selected pipeline. Pipelines represent structured workflows or processes (e.g., sales pipelines, recruitment processes) with unique fields such as stages, statuses, amounts, dates, and custom properties defined by the pipeline template.
This operation is beneficial when you want to programmatically modify details of an existing pipeline record, such as changing its stage, updating status, adjusting amounts, or modifying any custom fields associated with that pipeline.
Practical examples:
- Updating the status of a deal in a sales pipeline after a client meeting.
- Changing the recruitment stage of a candidate in a hiring pipeline.
- Adjusting financial figures or dates related to a project milestone in a project management pipeline.
Properties
| Name | Meaning |
|---|---|
| Select Pipeline Name or ID | Choose which pipeline contains the record to update. Options include pipeline names like "Startup Fundraising", "Sales Pipeline", or "Recruitment Process". You can select from a list or specify an ID using an expression. |
| ID | The UUID string identifying the specific pipeline record to update. |
| Update Fields | Collection of fields to update on the pipeline record. This includes: - Custom Properties: Pipeline-specific fields such as stage, status, amounts, dates, and other custom fields based on the pipeline template. Each property has a name/ID and a value. |
| Depth Name or ID | Level of nested related objects to include in the response: - 0: Only the primary record information - 1: Record plus directly related objects - 2: Record, direct relations, and their related objects. You can choose from the list or specify an ID via expression. |
Output
The output JSON contains the updated pipeline record data returned from the API after the update operation. It reflects the current state of the record including all updated fields and, depending on the depth parameter, may include related nested objects.
If the node supports binary data output for this resource (not indicated here), it would typically represent attachments or files related to the pipeline record, but no binary output is described for this operation.
Dependencies
- Requires an active connection to the Dalil AI API service.
- Requires an API authentication token credential configured in n8n to authorize requests.
- The node uses internal helper functions to parse and process field metadata and values according to the pipeline's schema.
- The pipeline and its custom properties must be retrievable via the API to populate options and validate inputs.
Troubleshooting
- Invalid pipeline selection error: Occurs if the selected pipeline JSON cannot be parsed correctly. Ensure the pipeline is selected properly from the dropdown or the expression returns valid JSON.
- Invalid property metadata error: Happens if a custom property specified for update does not match expected metadata format. Verify that the property name or ID corresponds to an active and valid pipeline field.
- API request errors: Could result from network issues, invalid credentials, or malformed requests. Check API key validity and ensure required fields are provided.
- Unexpected API response structure: Indicates the API response did not contain expected data. This might be due to API changes or temporary service issues.
- To handle errors gracefully, enable "Continue On Fail" in the node settings to allow processing of subsequent items even if one fails.
Links and References
- Dalil AI API Documentation (hypothetical link)
- n8n Expressions Documentation
- Working with Custom Properties in Dalil AI (hypothetical link)
This summary focuses specifically on the "Pipeline" resource and the "Update" operation as requested.