Pipefy icon

Pipefy

Interact with Pipefy API

Actions32

Overview

This node interacts with the Pipefy API to manage organizations, specifically allowing you to update an existing organization's details. The "Update Organization" operation lets you change the name of an organization by specifying its ID and the new name.

Common scenarios where this node is useful include:

  • Automating updates to organization names in Pipefy when changes occur in your CRM or ERP systems.
  • Synchronizing organizational data across multiple platforms.
  • Bulk updating organization names based on external triggers or workflows.

For example, if your company rebrands or merges departments, you can use this node to automatically update the organization names in Pipefy without manual intervention.

Properties

Name Meaning
Organization ID The unique identifier of the organization to update. This is required to specify which organization will be modified.
Organization Name The new name to assign to the organization. This is a required field representing the updated organization name.

Output

The node outputs a JSON object representing the updated organization. The structure includes:

  • id: The organization's unique identifier.
  • name: The updated name of the organization.
  • updated_at: Timestamp indicating when the organization was last updated.

Example output JSON:

{
  "id": 123,
  "name": "New Organization Name",
  "updated_at": "2024-06-01T12:34:56Z"
}

Dependencies

  • Requires an active connection to the Pipefy API.
  • Needs an API authentication token configured in n8n credentials for the Pipefy service.
  • The node sends GraphQL requests to https://api.pipefy.com/graphql.

Troubleshooting

  • Invalid Organization ID: If the provided organization ID does not exist or is incorrect, the API may return an error. Verify the ID before running the node.
  • Permission Errors: Ensure that the API key used has sufficient permissions to update organizations.
  • Network Issues: Connectivity problems with the Pipefy API endpoint can cause request failures.
  • Malformed Input: The organization name must be a valid string; empty or invalid values might cause errors.

If the node throws an error, check the error message returned from the API for details. Enabling "Continue On Fail" in the node settings can help handle errors gracefully in workflows.

Links and References

Discussion