N8N Tools - Pipefy Database icon

N8N Tools - Pipefy Database

Manage Pipefy database tables and records with advanced data operations

Overview

This node interacts with Pipefy database tables and their records, enabling advanced data operations such as creating, updating, retrieving, and deleting tables and table records. Specifically, the "Table Record - Get Many" operation fetches multiple records from a specified table, optionally filtered by a search title and limited in number.

Common scenarios where this node is beneficial include:

  • Retrieving a batch of records from a Pipefy table for reporting or further processing.
  • Searching records by title to find relevant entries quickly.
  • Limiting the number of returned records to optimize performance or meet API constraints.

Practical example:

  • A user wants to get up to 20 customer support tickets from a Pipefy table whose titles contain "urgent" to prioritize handling them.

Properties

Name Meaning
Table ID The unique identifier of the Pipefy table from which to retrieve records.
Limit Maximum number of records to return (between 1 and 50).
Search Title Optional string to filter records by matching their title.

Output

The output is an array of JSON objects representing the retrieved table records. Each record object contains all the fields and metadata associated with that record in the Pipefy table.

Example structure of each record in json output:

{
  "id": "record_id",
  "title": "Record Title",
  "fieldValues": [
    {
      "fieldId": "field_1",
      "fieldValue": "value1"
    },
    {
      "fieldId": "field_2",
      "fieldValue": "value2"
    }
  ],
  // ... other metadata fields
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Pipefy API.
  • Requires a second API authentication token credential specific to the Pipefy integration.
  • The node uses internal utility functions to perform GraphQL queries/mutations against the Pipefy API.

Troubleshooting

  • Common issues:

    • Missing or invalid Table ID will cause validation errors.
    • Providing an invalid JSON format in other operations (not applicable here) can cause parsing errors.
    • Exceeding the maximum limit (50) will be rejected; ensure the limit is within allowed range.
    • Network or authentication failures may result in API request errors.
  • Error messages:

    • "Table ID" is required β€” Ensure the Table ID property is set and valid.
    • "The operation "getRecords" is not supported for resource "tableRecord" β€” This indicates a misconfiguration; verify the selected resource and operation.
    • "Records Data must be valid JSON" β€” Not applicable here but common in create/update multiple records operations.

Resolving these typically involves verifying input parameters, credentials, and network connectivity.

Links and References

Discussion