This release is a pre-release and may not be stable for production use.
pipefy
Vendor API SDK for Pipefy's GraphQL API: the shared library consumed by pipefy-mcp-server and pipefy-cli (not a generic “shared utils” layer). It owns HTTP/GraphQL transport, service classes, query constants, Pydantic models, shared settings, exceptions, and utilities.
Status
Workspace-internal in v0.1; publishing pipefy to PyPI is gated separately from CLI/MCP (see RELEASE.md Trusted Publishing notes).
Usage (within the monorepo)
from pipefy_sdk import PipefyClient
client = PipefyClient(...)
card = await client.get_card(card_id="12345")
Generated GraphQL input models
pipefy_sdk/graphql_inputs/ mirrors the Pipefy GraphQL input objects the SDK writes to. _generated.py and __init__.py are written by scripts/generate_graphql_inputs.py and are not edited by hand; _base.py holds the parts that needed a decision rather than a mapping.
# After an API change, with Pipefy credentials (`pipefy auth login`):
uv run python scripts/generate_graphql_inputs.py snapshot # rewrite schema/input_types.json
uv run python scripts/generate_graphql_inputs.py # rewrite the models
# What CI runs, no credentials needed:
uv run python scripts/generate_graphql_inputs.py check
check catches a hand-edit of a generated file, or a snapshot committed without regenerating. It cannot see the API itself move, because CI has no Pipefy credentials — that is test_input_types_snapshot_matches_live, which is marked integration.
The snapshot includes deprecated input fields and their deprecation reasons. Generated models accept these fields and mark them with Field(deprecated=...). This preserves API compatibility while exposing deprecation metadata to callers.
To migrate another **attrs method, add its input type to ROOT_INPUT_TYPES in the script and regenerate; the transitive closure is resolved from there.
Development
From the repository root:
uv sync # installs all workspace members
uv run pytest packages/sdk/tests # SDK unit tests in isolation
uv run ruff check packages/sdk/src # lint
See the root README.md, docs/config.md for PIPEFY_* environment variables and config.toml schema, and docs/sdk/README.md for SDK-oriented notes.
Metadata
Release files for pipefy 0.5.8b1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pipefy-0.5.8b1-py3-none-any.whl | Python 3 | none | any | Details for pipefy-0.5.8b1-py3-none-any.whl |
Release files / pipefy-0.5.8b1-py3-none-any.whl
| Download URL | pipefy-0.5.8b1-py3-none-any.whl |
|---|---|
| Size | 365.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1f9bb972b50abeb314430bf8c8cd6d451282a0e534d27b078891f3fcb6d9913
|
|
BLAKE2b-256 checksum How to use checksums |
a6336b6c0b847c4b1aaf590100f17b715575c5c8865a1c15bd1332e1784a6a3a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logSecurity for pipefy 0.5.8b1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
1 file in this release has been uploaded with provenance metadata.
Attestation for pipefy-0.5.8b1-py3-none-any.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.