Actions11
Overview
The node allows updating an existing Pipe in Pipefy, a workflow and process management platform. It is useful for modifying pipe attributes such as the name, description, color theme, and permissions after the pipe has been created. This can help keep your workflows organized and up to date as project requirements evolve.
Practical examples:
- Renaming a pipe to reflect a new project phase.
- Changing the pipe’s color to visually categorize it.
- Updating the description to provide more context or instructions.
- Adjusting permissions to allow anyone to create cards or making the pipe public.
Properties
| Name | Meaning |
|---|---|
| Pipe ID | The unique identifier of the pipe to update (required). |
| Pipe Name | New name for the pipe. |
| Additional Fields | Optional extra settings: |
| - Description | Text description of the pipe. |
| - Color | Color theme for the pipe. Options: Blue, Red, Green, Yellow, Purple, Orange, Pink, Gray. |
| - Anyone Can Create Cards | Boolean flag indicating if anyone can create cards in this pipe. |
| - Public | Boolean flag indicating if the pipe is public. |
Output
The output JSON contains the updated pipe object with its current properties after the update operation. This includes fields like the pipe's ID, name, description, color, permissions, and other metadata reflecting the latest state.
Example output structure (simplified):
{
"id": "string",
"name": "string",
"description": "string",
"color": "string",
"anyoneCanCreateCard": true,
"public": false,
...
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Pipefy API.
- Requires an additional API token credential for the n8n Tools API used internally.
- The node uses GraphQL queries/mutations to interact with Pipefy’s API.
- Proper configuration of these credentials in n8n is necessary for successful execution.
Troubleshooting
- Missing Required Fields: Errors will occur if the Pipe ID or Pipe Name (when updating) are not provided. Ensure these fields are filled.
- Invalid Pipe ID: If the Pipe ID does not exist or is incorrect, the API will return an error. Verify the ID before running.
- Permission Issues: Insufficient permissions on the Pipefy account or API token may cause failures. Confirm that the API credentials have rights to update pipes.
- API Rate Limits: Frequent requests might hit rate limits imposed by Pipefy. Implement retry logic or reduce request frequency if needed.
- Network/Connectivity Problems: Ensure stable internet connection and that the Pipefy API endpoint is reachable.
Common error messages typically indicate missing parameters or authorization failures. Review the error message details and verify input parameters and credentials accordingly.