Pipefy

Overview

This node interacts with the Pipefy API to manage organizations and other resources. Specifically, for the Organization - Get operation, it retrieves detailed information about a specific organization by its ID. This includes the organization's name, industry, members (with their user details and roles), and timestamps of creation and last update.

This operation is useful when you need to fetch up-to-date organizational data within an automation workflow, such as syncing organization info to a CRM, auditing membership, or triggering actions based on organization attributes.

Example use case:
You want to automatically retrieve an organization's details whenever a related event occurs, then use that data to update records in another system or send notifications to team members.

Properties

Output

The output JSON object contains the following fields representing the organization:

• id: The organization's unique identifier.
• name: The name of the organization.
• industry: The industry category of the organization.
• members: An array of member objects, each containing:
  • user: Object with user details:
    • id: User's unique identifier.
    • name: User's full name.
    • email: User's email address.
  • role_name: The role assigned to the user within the organization.
• created_at: Timestamp when the organization was created.
• updated_at: Timestamp when the organization was last updated.

The output structure provides comprehensive details about the organization and its members.

Dependencies

• Requires an active connection to the Pipefy API via an API key credential configured in n8n.
• The node sends GraphQL queries to the Pipefy API endpoint at https://api.pipefy.com/graphql.
• Proper permissions on the API key are necessary to read organization data.

Troubleshooting

• Common issues:

  • Invalid or missing Organization ID will cause the query to fail.
  • Insufficient API permissions may result in authorization errors.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • Errors returned from the Pipefy API typically include descriptive messages indicating the problem (e.g., "Organization not found" or "Unauthorized").
  • If the node throws an error, verify the Organization ID parameter and API credentials.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully within workflows.

Links and References

• Pipefy API Documentation – Official API docs for understanding available queries and mutations.
• GraphQL Basics – Introduction to GraphQL queries used by this node.