Pipefy

Overview

This node interacts with the Pipefy API to manage table records within Pipefy tables. Specifically, for the Table Record - Get operation, it retrieves detailed information about a specific record in a Pipefy table by its record ID.

Common scenarios where this node is beneficial include:

• Fetching detailed data of a particular record in a Pipefy table for further processing or reporting.
• Integrating Pipefy table data into other systems or workflows by retrieving record details dynamically.
• Automating workflows that depend on the current state or content of a specific table record.

For example, you might use this node to get the details of a customer record stored in a Pipefy table and then use that data to trigger notifications or update another database.

Properties

Output

The output JSON object contains the details of the requested table record with the following structure:

• id: The unique identifier of the table record.
• title: The title of the record.
• fields: An array of fields associated with the record, each containing:
  • name: The name of the field.
  • value: The value of the field (string).
  • array_value: If the field holds multiple values (e.g., checklist), this contains an array of those values.
• created_at: Timestamp when the record was created.
• updated_at: Timestamp when the record was last updated.

Example output snippet:

{
  "id": "12345",
  "title": "Record Title",
  "fields": [
    {
      "name": "Field Name",
      "value": "Field Value",
      "array_value": ["Value1", "Value2"]
    }
  ],
  "created_at": "2023-01-01T12:00:00Z",
  "updated_at": "2023-01-02T12:00:00Z"
}

The node does not output binary data for this operation.

Dependencies

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

Troubleshooting

• Invalid Record ID: If the provided Record ID does not exist or is incorrect, the API will likely return an error or empty result. Verify the Record ID is correct.
• Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
• Network Issues: Connectivity problems can cause request failures; check network access to the Pipefy API.
• API Rate Limits: Excessive requests may hit rate limits imposed by Pipefy; consider adding delays or handling retries.
• Malformed Queries: Since the node constructs GraphQL queries dynamically, ensure input parameters like Record ID are correctly formatted (numeric IDs expected as numbers, not strings).

If errors occur, enabling "Continue On Fail" in the node settings allows the workflow to proceed while capturing error messages in the output JSON under an error property.

Links and References

• Pipefy API Documentation
• GraphQL Basics
• n8n Documentation on Credentials