Pipefy API Fallback (Tier 3 — Last Resort)

Read the MCP reference or CLI reference for the surface you are using. Load only the relevant reference.

This skill activates only after Tiers 1 and 2 have failed. Call the Pipefy GraphQL API directly, bypassing the toolkit connection.

If a write reports failure, re-read the target before changing tiers or retrying. The mutation may already have applied; follow Ambiguous write failure.

3-tier resolution strategy (always follow in order)

1. Try a dedicated operation (create_card, get_phase_cards, get_phase_allowed_move_targets, update_pipe, etc.). For card/phase seeding and inventory, see pipefy-pipes-and-cards — Seed pipe across phases.
2. Use schema introspection and execute_graphql when a dedicated operation is unavailable or fails unexpectedly. See pipefy-introspection.
3. Use direct HTTP only when the toolkit connection is unavailable or GraphQL execution fails with an infrastructure error.

Do not jump to Tier 3 after a single failure. Follow the tiers in order. Testing a new mutation belongs in Tier 2.