skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
pipefy/ai-toolkit804 installs

pipefy-relations

Use this skill when the user wants to link pipes, tables, or cards across workflows — creating or managing pipe relations, table relations, or card relations.

How do I install this agent skill?

npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-relations
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill is safe and does not contain any malicious patterns or security risks. It provides standard instructions for managing workflow relations using the Pipefy platform.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

Connections & Relations

MCP clients: read references/mcp.md. CLI users: read references/cli.md. Examples below describe shared operation arguments.

Link processes and cards across workflows.


Key concepts

  • Pipe relations define parent/child structure between pipes (who connects to whom, constraints, auto-fill). Use get_pipe_relations on a pipe to list relation IDs and metadata.
  • Card relations connect individual cards through an existing pipe relation: pass source_id = the pipe relation's ID (from get_pipe_relations). Default sourceType is PipeRelation; use extra_input (e.g., sourceType: Field) when the API requires a field-based link — see introspect_type on CreateCardRelationInput.
  • Table relations in GraphQL are loaded by table-relation ID, not by database table ID: get_table_relations takes a non-empty list of those IDs.
  • Connector fields are card fields (connection type), not pipe relations for writes. Prefer update_card + field_updates with operation ADD/REMOVE (related card ids, or record ids when the field connects to a database table). An id from any other pipe or table is dropped without an error: ADD keeps the existing links, and update_card_field with no valid id clears them all. Read the links back after a write. update_card_field is replace-all of the full id list; get_card value is display titles only — do not rebuild from it. This skill's get_card_relations still reads connector-field links (with card ids). create_card_relation / delete_card_relation write links through a pipe relation and are incremental — pick the surface that matches the link type. delete_card_relation removes only a link made through a pipe relation, never a connector-field link, and needs permission to edit the parent card.

Tools

OperationRead-onlyPurpose
get_pipe_relationsYesList pipe-to-pipe relations for a pipe.
create_pipe_relationNoCreate a new pipe-to-pipe relation.
update_pipe_relationNoChange relation config (auto-fill, constraints). Flags you leave out keep their current values.
delete_pipe_relationNoDestructive; review and approve first.
get_table_relationsYesLoad table relations by relation ID.
get_card_relationsYesList all card-to-card relations on a card.
create_card_relationNoLink two cards through an existing pipe relation.
delete_card_relationNoDestructive; review and approve first.

Steps — link two cards via an existing pipe relation

  1. Get the pipe relation ID:

    Operation: get_pipe_relations(pipe_id=67890)

    Note the id field on the relation (not the pipe ID).

  2. Create the card relation:

    Operation: create_card_relation(parent_id=<PARENT_CARD_ID>, child_id=<CHILD_CARD_ID>, source_id=<PIPE_RELATION_ID>)

  3. Verify:

    Operation: get_card_relations(card_id=<CHILD_CARD_ID>)


Steps — create a new pipe relation

  1. Create the relation between two pipes:

    Operation: create_pipe_relation(parent_id=111, child_id=222, name="Support Escalation")

  2. Use the relation — cards in the parent pipe can now be linked to cards in the child pipe using create_card_relation.


Success criteria

  • get_pipe_relations returns the new relation with both pipe IDs.
  • get_card_relations shows the linked card ID after create_card_relation.

Failure modes

  • create_card_relation fails with "relation not found": source_id must be the pipe relation ID (from get_pipe_relations), not the pipe ID. These are different values.
  • Table relations return empty: get_table_relations requires table-relation IDs, not table IDs. Get table-relation IDs from the table's connection config.
  • update_pipe_relation and ownFieldMaps: constraint flags you leave out keep their current values, so pass only the ones you change. Leave ownFieldMaps out to keep the auto-fill mappings: sending it replaces the whole list.
  • Deletion: show the affected relation and obtain approval before removing it.

See also

  • pipefy-pipes-and-cards — create the pipes and cards before linking them; connector field updates and update_card_field replace-all live there.
  • docs/mcp/tools/identifiers.md — which args expect slug vs numeric id for field and relation tools.
  • pipefy-introspection — discover CreateCardRelationInput when non-standard sourceType is needed.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/pipefy/ai-toolkit/pipefy-relations">View pipefy-relations on skillZs</a>