N8N Tools - Pipefy Pipe icon

N8N Tools - Pipefy Pipe

Create, update, delete, and manage Pipefy pipes with advanced workflow features
Join our community

Actions11

Overview

The node allows users to manage phases within Pipefy pipes, specifically enabling the update of an existing phase's details. This includes changing the phase name, description, and settings such as whether it is a "done" phase or if cards can be created directly in it. This operation is useful for workflow automation where phases in a pipe need to be dynamically adjusted based on evolving project requirements or process changes.

Practical examples:

  • Renaming a phase to better reflect its purpose.
  • Marking a phase as a "done" phase to indicate completion.
  • Changing whether new cards can be created directly in that phase, controlling workflow entry points.

Properties

Name Meaning
Phase ID The unique identifier of the phase to update.
Phase Name The new name for the phase (optional; if not provided, the name remains unchanged).
Phase Options A collection of optional settings for the phase:
   Description Text description of the phase.
   Done Phase Boolean indicating if this phase is considered a "done" or completed phase.
   Can Receive Cards Directly Boolean indicating if cards can be created directly in this phase.

Output

The output JSON object represents the updated phase with its current properties after the update operation. It typically includes fields such as the phase ID, name, description, done status, and card creation permission.

Example structure (simplified):

{
  "id": "string",
  "name": "string",
  "description": "string",
  "done": true,
  "canReceiveCardDirectly": true
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Pipefy API.
  • The node uses internal utility functions to perform GraphQL requests to Pipefy's API endpoints.
  • Proper configuration of credentials and network access to Pipefy's API is necessary.

Troubleshooting

  • Missing Required Fields: Errors will occur if the Phase ID is not provided since it is mandatory for identifying which phase to update.
  • Invalid Phase ID: If the provided Phase ID does not exist or is incorrect, the API will return an error indicating the phase could not be found.
  • Permission Issues: Insufficient permissions on the Pipefy account or API token may cause authorization errors.
  • API Request Failures: Network issues or invalid API credentials will result in request failures.

To resolve these:

  • Ensure all required fields are filled correctly.
  • Verify the Phase ID exists in the target pipe.
  • Confirm the API key has sufficient permissions.
  • Check network connectivity and API endpoint accessibility.

Links and References

Discussion