pipefy-database-tables
Use this skill when the user wants to work with Pipefy Database Tables — creating/reading/updating/deleting tables, records (rows), or table fields (schema columns).
- Installs
- 678
- Last 24h
- +10
- Trending rank
- #8656
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-database-tables- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pipefy-database-tables automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Database Tables
MCP clients: read references/mcp.md. CLI users: read references/cli.md. Examples below describe shared operation arguments.
Tables, records (rows), schema columns (table fields), and attachments for Pipefy Database Tables.
Cross-cutting patterns
- Use
introspect_typeon inputs such asCreateTableFieldInput/UpdateTableFieldInput. - Pagination:
get_table_recordsandfind_recordssupportfirst/after; default page size is 50. find_recordsover paginatedget_table_recordswhen you know the field value. One call withfield_idandfield_valuebeats N pages ofget_table_records.
Table operations
| Operation | Read-only | Purpose |
|---|---|---|
get_tables | Yes | Load database tables by their IDs. |
search_tables | Yes | Search tables by name. |
get_table | Yes | Table metadata and field schema. |
create_table | No | Create a new database table. |
update_table | No | Rename or change settings. |
delete_table | No | Destructive; review and approve first. |
Table field (schema column) operations
| Operation | Purpose |
|---|---|
create_table_field | Add a column to a table schema. |
update_table_field | Rename or change column description, required status, or options. |
delete_table_field | Destructive; review and approve first. Requires table_id. |
Record operations
| Operation | Read-only | Purpose |
|---|---|---|
get_table_records | Yes | Paginated list of all records in a table. |
find_records | Yes | Filter records by field_id and field_value — preferred over paginating get_table_records. |
get_table_record | Yes | Single record with all populated field values. |
create_table_record | No | Add a row to a table. |
update_table_record | No | Update a row's title, due_date or status_id. It accepts no other keys. |
set_table_record_field_value | No | Set one field value on a row. Use it for every table field. |
delete_table_record | No | Destructive; review and approve first. |
Steps — find and update a record
-
Get table ID (if not known):
Operation:
search_tables(table_name="Customers")and select the table ID from the results. -
Find the record (use
find_records, not pagination):Operation:
find_records(table_id=456, field_id="email", field_value="user@example.com") -
Update one field (targeted):
Operation:
set_table_record_field_value(record_id=789, field_id="status", value="Active")Update record metadata (such as title, due date, or status):
Operation:
update_table_record(record_id=789, fields={"title":"Updated title"})
Review destructive changes
Before deletion, show the affected data and obtain explicit approval. Preview content per operation:
delete_table— show table name and field count.get_tabledoes not return a record count; obtain one through schema-checked GraphQL or by paging through all records if practical. State clearly when the count is unknown. Deleting a table destroys all rows and schema.delete_table_record— show record title and key field values so the user can identify which row will vanish.delete_table_field— show field name and type; warn explicitly that all column data will be permanently lost.
Never delete without first reviewing the affected data.
Success criteria
get_table_recordsreturns the created/updated records with correct field values.- Schema changes reflect immediately in
get_table.
Failure modes
get_table_record/get_table_recordsomit empty fields. Records only return populated fields, so you cannot tell "field unset" from "field doesn't exist" without callingget_tablefor the full schema.create_table_recordtitle silently overridden. When the first table field is a start-form-style label column, Pipefy uses that field's value as the recordtitle, ignoring thetitleparameter. Don't rely ontitleif the first field auto-populates a label-like column.create_table_fieldrejects type: callintrospect_type(type_name="CreateTableFieldInput")for valid field types.find_recordsreturns empty: check thatfield_idmatches a field's ID (not label) fromget_table.- Pagination cursor expired: re-fetch from the beginning; cursors are short-lived.
See also
pipefy-relations— connect tables to pipes (and the table-relation ID namespace gotcha).pipefy-introspection— discover field input schemas.
FAQ
What does the pipefy-database-tables skill do?
Use this skill when the user wants to work with Pipefy Database Tables — creating/reading/updating/deleting tables, records (rows), or table fields (schema columns).
How do I install pipefy-database-tables?
Run npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-database-tables in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pipefy-database-tables/ (personal) or .claude/skills/pipefy-database-tables/ (project).
Which AI agents can use pipefy-database-tables?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pipefy-database-tables safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pipefy-database-tables?
It is published by pipefy in pipefy/ai-toolkit. It has 678 recorded installs.
More from pipefy/ai-toolkit
pipefy-observability
pipefy/ai-toolkit
Use this skill when the user wants to check AI agent logs, automation execution logs, org-level usage stats, AI credit consumption, or export automation job history.
pipefy-automations
pipefy/ai-toolkit
Use this skill when the user wants to create, read, update, or delete traditional automations (if/then rules) or AI automations (prompt-driven). For AI agents (conversational), see pipefy-ai-agents.
pipefy-pipes-and-cards
pipefy/ai-toolkit
Use this skill when the user wants to read, create, update, or delete pipes, phases, phase fields, labels, cards, comments, or field conditions. Use the seed-pipe-across-phases workflow when populating empty phases for demos or QA.
pipefy-portal-setup
pipefy/ai-toolkit
Use this skill when the user wants to list, create, or configure Pipefy portals (main hub, pages, page elements, sub-portals, publish/unpublish). Uses Interfaces and internalapi. Not for pipes/cards.
pipefy-introspection
pipefy/ai-toolkit
Use this skill when you need to discover GraphQL type shapes, mutation signatures, enum values, or execute arbitrary GraphQL as a fallback. This is the first fallback tier (Tier 2) when dedicated operations fail or don't exist for an operation.
pipefy-api-fallback
pipefy/ai-toolkit
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow the 3-tier resolution strategy before reaching this point.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.