pipefy/ai-toolkit

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.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/pipefy/ai-toolkit --skill pipefy-relations

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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). 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.

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).
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).

  1. Create the card relation:

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

  1. 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")

  1. 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.
  • 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.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
pipefy
커뮤니티

pipefy-ai-agents

Use this skill when the user wants to create, read, update, delete, or troubleshoot AI agents (conversational agents with behaviors). Includes pre-flight validation and pipe-scoped knowledge bases (list, plain text/document/data lookup CRUD, access probe) attached via dataSourceIds. For traditional automations and AI automations, see pipefy-automations.

1시간 설치 수
3
GitHub Stars
50
업데이트
10월 20일
pipefy
커뮤니티

pipefy-api-fallback

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.

1시간 설치 수
3
GitHub Stars
50
업데이트
10월 20일
pipefy
커뮤니티

pipefy-attachments

Use this skill when the user wants to upload a file to a Pipefy card or table-record attachment field. Covers local and downloaded file sources, plus a presigned-URL handshake for uploading files directly.

1시간 설치 수
3
GitHub Stars
50
업데이트
10월 20일
pipefy
커뮤니티

pipefy-automations

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.

1시간 설치 수
3
GitHub Stars
50
업데이트
10월 20일