N8N Tools - Pipefy Database icon

N8N Tools - Pipefy Database

Manage Pipefy database tables and records with advanced data operations
Join our community

Actions15

Overview

This node allows you to interact with Pipefy database tables and their records through various operations. Specifically, for the Table Record - Get operation, it retrieves a single table record by its unique ID. This is useful when you need to fetch detailed information about a specific record stored in a Pipefy table.

Common scenarios include:

  • Fetching a particular record's data to use in subsequent workflow steps.
  • Validating or processing data from a known record.
  • Integrating Pipefy record data into other systems or reports.

For example, you might use this node to get a customer record by ID and then send a personalized email based on that data.

Properties

Name Meaning
Table Record ID The unique identifier of the table record to retrieve. This is required to specify which record to fetch.

Output

The output JSON contains the full details of the requested table record as returned by the Pipefy API. This typically includes fields such as the record's ID, title, field values, creation date, and any other metadata associated with the record.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "record_123",
  "title": "Sample Record",
  "fieldValues": [
    {
      "fieldId": "field_1",
      "fieldValue": "Value 1"
    },
    {
      "fieldId": "field_2",
      "fieldValue": "Value 2"
    }
  ],
  "createdAt": "2024-01-01T12:00:00Z",
  // ... other record metadata
}

Dependencies

  • Requires an API key credential for authenticating with the Pipefy service.
  • Requires a second API authentication token credential specific to Pipefy.
  • The node uses internal utility functions to make GraphQL requests to Pipefy's API endpoints.

Troubleshooting

  • Missing or invalid Table Record ID: The node requires a valid record ID. If omitted or incorrect, the node will throw an error indicating the missing or invalid parameter.
  • API authentication errors: Ensure that the provided API credentials are correct and have sufficient permissions to access the specified record.
  • Record not found: If the record ID does not exist or has been deleted, the API may return an error or empty response.
  • Invalid JSON or malformed input: Although not applicable for this operation specifically, other operations involving JSON input require valid JSON formatting.

To resolve these issues:

  • Double-check the Table Record ID value.
  • Verify API credentials and permissions.
  • Confirm the record exists in the Pipefy database.

Links and References

Discussion