N8N Tools - Pipefy Database icon

N8N Tools - Pipefy Database

Manage Pipefy database tables and records with advanced data operations

Overview

This node enables advanced management of Pipefy database tables and their records within n8n workflows. Specifically, the "Table Record" resource with the "Create Multiple" operation allows users to create multiple table records in a single execution. This is particularly useful when you need to batch import or add several entries to a Pipefy table efficiently.

Practical scenarios include:

  • Bulk importing data from CSV or JSON sources into Pipefy tables.
  • Automating the creation of multiple task or project records based on external triggers.
  • Synchronizing data from other systems by creating multiple records at once.

Properties

Name Meaning
Table ID The unique identifier of the Pipefy table where the records will be created.
Records Data A JSON array representing the records to create. Each record must have a title and an array of fields. Each field includes a fieldId (the ID of the table field) and a value (the value to set). Example format:
[
  {
    "title": "Record 1",
    "fields": [
      {"fieldId": "field_1", "value": "value1"}
    ]
  }
]

|

Output

The output is an array of created table records, each represented as a JSON object containing details of the newly created record. The structure corresponds to the Pipefy API's response for created records, typically including the record's ID, title, and field values.

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 Pipefy integration.
  • The node uses internal utility functions to perform GraphQL API requests to Pipefy's database mutations and queries.

Troubleshooting

  • Invalid JSON in Records Data: If the "Records Data" property contains malformed JSON, the node will throw an error stating "Records Data must be valid JSON". To fix this, ensure the JSON syntax is correct and properly formatted.
  • Missing Required Fields: The node validates that "Table ID" and "Records Data" are provided. Omitting these will cause errors indicating the missing required fields.
  • API Errors: Errors returned from the Pipefy API (e.g., invalid table ID, permission issues) will propagate as node errors. Verify that the table ID exists and that the API credentials have sufficient permissions.
  • Field IDs and Values: Ensure that the fieldIds used in the records correspond to actual fields in the target Pipefy table, and that the values conform to expected formats.

Links and References

Discussion