pipefy-attachments

Attachments

Upload one file at a time to a card or table-record attachment field. The upload goes through Pipefy's presigned URL flow (request URL, S3 PUT, then field update). 3 MCP tools, 2 CLI commands.

---

When to use

• The user says "attach this file to card X" or "upload to the documents field on record Y".
• Pick the source by where the bytes actually are (see Trust model):
  • The file is on a disk the MCP server can read → file_path.
  • The file is reachable at an HTTPS URL → file_url.
  • The server can't read the file (a local file on the hosted profile), or it's larger than the 100 MiB in-tool cap → the presigned handshake (create_attachment_presigned_url; see "Uploading a file the server can't read" below), where the client does the upload.
  • The agent generated bytes in a sandbox the server cannot read → write them to a path the server can read and use file_path, or host them at a URL and use file_url.

Do not use this skill for:

• Reading or listing existing attachments. There is no list/download tool in this skill scope. Cards and table records expose their attachments through the regular card/record fetch tools.
• Bulk uploads. One file per call; iterate at the agent layer.

Prerequisites

• A Pipefy organization_id. Find it via get_organization or get_pipe.
• A target card_id or table_record_id.
• The attachment field's slug (the human-readable id like document_upload, not the field's uuid). Find it on the card or table record fetch tools.
• Exactly one file source: a file_path the MCP server can read, or a file_url the server can download.

Tools needed

Tool (MCP)	CLI equivalent	Read-only
upload_attachment_to_card	pipefy attachment upload --card <id>	No
upload_attachment_to_table_record	pipefy attachment upload --record <id>	No
create_attachment_presigned_url	pipefy attachment presign	No