Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with a CRM system to perform various operations on different resources, including pipelines. Specifically, the "Update" operation for the "Pipeline" resource allows users to modify an existing pipeline's properties such as its name and the order or membership of statuses within it. This is useful for managing sales or opportunity pipelines dynamically, for example, renaming a pipeline to reflect a new sales strategy or reordering statuses to match updated business processes.
Practical examples:
- Renaming a sales pipeline from "Q2 Sales" to "Mid-Year Sales".
- Reordering opportunity statuses within a pipeline to better reflect the current sales funnel stages.
- Moving statuses between pipelines to reorganize how opportunities are tracked.
Properties
| Name | Meaning |
|---|---|
| Pipeline ID | The unique identifier of the pipeline to update. |
| Update Fields | Collection of fields to update in the pipeline: |
| Name | The new name to assign to the pipeline. |
| Statuses | A JSON array representing opportunity status objects to reorder or move statuses within or between pipelines. Format example: [{"id": "status_id"}] |
Output
The node outputs JSON data representing the result of the update operation on the pipeline. This typically includes the updated pipeline object reflecting changes such as the new name or reordered statuses.
If multiple input items are processed, the output will be an array of results corresponding to each item.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the CRM service.
- The node depends on the CRM's REST API endpoints to perform pipeline updates.
- Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing Pipeline ID: The node requires a valid pipeline identifier; ensure this is correctly provided.
- Malformed JSON in the Statuses field: The statuses must be a properly formatted JSON array; invalid JSON will cause errors.
- Insufficient permissions: The API key used must have rights to update pipelines.
- Network or authentication errors when connecting to the CRM API.
Error messages:
"The resource "pipeline" is not known!": Indicates an incorrect resource parameter; verify that "pipeline" is selected.- API errors returned from the CRM (e.g., 401 Unauthorized, 404 Not Found) should be checked against the API key validity and pipeline existence.
To resolve errors, verify all input parameters, ensure correct JSON formatting, and confirm API credentials and permissions.