Skip to content

feat: add Pipefy adapter (fixes #982) - #1373

Open
juliasadler wants to merge 1 commit into
HelpCode-ai:mainfrom
juliasadler:feat/pipefy-adapter
Open

juliasadler wants to merge 1 commit into
HelpCode-ai:mainfrom
juliasadler:feat/pipefy-adapter

Conversation

@juliasadler

Copy link
Copy Markdown

Summary

Adds a read-only Pipefy adapter (work management platform) as a single JSON file, claiming one of the free targets from the claim-pool in #982. Pipefy was verified free: no adapter in packages/backend/src/adapters/, not in the claim table, no open PR.

Note: I first claimed onOffice in the thread, then released it — digging into the onOffice API docs showed its HMAC v2 signs timestamp+token+resourcetype+actionid and puts the signature inside the JSON body per action, which the adapter HMAC engine (header/query placement only) cannot express. Pipefy fits the existing engine cleanly (GraphQL + bearer token).

Changes

  • packages/backend/src/adapters/intl/pipefy.json — new adapter, 6 read-only GraphQL tools:
    • pipefy_list_organizations (probe — lightest documented query, doubles as auth check)
    • pipefy_list_pipes, pipefy_get_pipe, pipefy_list_cards (paginated via first/after, cap 50), pipefy_get_card, pipefy_get_phase
    • authType: BEARER_TOKEN → Authorization: Bearer <token> via PIPEFY_API_TOKEN (PAT from app.pipefy.com/tokens or a Service Account token)
  • packages/backend/src/adapters/intl/pipefy.live.spec.ts — static conformance spec (auth, probe, pagination cap, variable mapping) + opt-in live block gated behind RUN_PIPEFY_LIVE=1
  • packages/backend/src/adapters/catalog.ts — regenerated (node scripts/regenerate-catalog.mjs)
  • Count files 680 → 681 (node scripts/adapter-count.mjs --check): README.md, README.de.md, README.ja.md, README.zh-CN.md, glama.json, CITATION.cff, server.json, package.json
  • llms.txt, llms-full.txt — regenerated
  • packages/frontend/public/logos/connectors/pipefy.svg — logo

Type

  • New feature

Testing

  • node scripts/validate-adapters.mjs --warn — exit 0, zero new warnings for pipefy (4 pre-existing warnings belong to other adapters)
  • node scripts/adapter-count.mjs --check — "OK: every quoted count equals 681 adapters"
  • node scripts/generate-llms-txt.mjs --check — clean
  • New pipefy.live.spec.ts static suite — mirrors the catalog.spec.ts gates for this adapter (slug unique, authType valid, probe runnable with no required params, every GraphQL $var provided via queryParams, no bodyMapping.variables); all pass
  • Live API calls — not run: no Pipefy credentials available in this environment (opt-in block is skipped in CI by design, same as other adapters)

GraphQL shapes were taken from the official Pipefy developer docs (developers.pipefy.com/reference/*); the one header discrepancy in their docs (Authentication vs Authorization) was resolved in favor of Authorization: Bearer, corroborated by their community and a working open-source integration. I did not include the community-sourced me query — the probe uses the documented organizations query instead.

Checklist

  • My code follows the existing code style (copied the intl/monday.json GraphQL patterns)
  • I have tested my changes locally (see Testing above)
  • I have updated documentation (instructions block in the adapter JSON)
  • All existing tests pass — validator + count checker green; full Jest suite runs in CI
  • This PR has a descriptive title

Related Issues

Fixes #982 (claim-pool: Pipefy was a free target; claimed in the thread)

Add a read-only GraphQL adapter for Pipefy (work management platform).

Six tools: list_organizations (probe), list_pipes, get_pipe, list_cards (paginated), get_card, get_phase.

Bearer token auth via PIPEFY_API_TOKEN. Follows the claim-pool in HelpCode-ai#982.
@github-actions

github-actions Bot commented Nov 1, 2026 •

Copy link
Copy Markdown

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@github-actions

github-actions Bot commented Nov 1, 2026

Copy link
Copy Markdown

👋 Welcome, @juliasadler, and thanks for opening your first PR on AnythingMCP!

A few quick pointers:

  • Make sure CI is green before requesting review (Backend, Frontend, Playwright, CodeQL, Trivy).
  • If this is a new adapter, the parametrised catalog.spec.ts test will validate it automatically.
  • Sign off your commits if you can — it's not blocking, just nice to have.

Someone from the core team will look at this within ~48h. If you don't hear back, please ping us in Discussions / Q&A.

⭐ While you wait — if you find AnythingMCP useful, a star helps others discover it.

@juliasadler

Copy link
Copy Markdown
Author

I have read the CLA Document and I hereby sign the CLA

github-actions Bot added a commit that referenced this pull request Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐣 Good first issue: contribute a new MCP adapter

1 participant