Download PDFMarkdown Version
ClaudeChatGPTPerplexityGeminiMicrosoft CopilotRaycastMeta AIGrokZ.aiQwenKimi
DeepSeekMistralCursorVS CodeWindsurfJetBrainsClineLovableVercel AI SDKLangChain

Use Pipefy with your AI.

Connect your account once and let the AI you already use work with it, without building another integration. Manage workflows via Pipefy. list pipes, create cards, move phases, update fields, and track processes directly from any AI agent.

Included with plan

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Complete set · 14 capabilities

The complete Pipefy capability set.

These are the exact actions your AI can choose when you ask it to work with Pipefy.

Capability set01 / 04

01-04

4 capabilities in this set.

Part of 14 available through Pipefy.

  1. 01

    Delete card

    You must provide the card_id. This action cannot be undone. Use this to remove test cards, duplicates, or items that were created in error. Be careful as this will also remove all associated data including comments, attachments, and field values for that card. Delete a card from a pipe

  2. 02

    Get organization

    Use the organization_id to inspect your organization's structure, understand team membership, and discover available pipes for card management. Get details of a Pipefy organization

  3. 03

    Get phase

    Phases represent steps in a pipe's workflow. Use the phase_id obtained from get_pipe or list_phases to inspect phase configuration. This helps understand what fields are required at each step of the workflow. Get details of a specific phase

  4. 04

    Get pipe

    Each pipe represents a workflow or process with multiple phases (steps) and custom fields. Use the pipe_id to get the structure of a pipe before creating cards or managing cards within it. The response includes all phases with their IDs, names, and the custom fields defined for the pipe. Get details of a specific Pipefy pipe (process)

Capability set02 / 04

05-08

4 capabilities in this set.

Part of 14 available through Pipefy.

  1. 05

    Get user profile

    Use this to verify API token access and discover organization IDs needed for other queries. This is also useful for understanding which organizations and pipes the user has access to. Get the authenticated user profile

  2. 06

    Move card to phase

    You must provide the card_id and the target phase_id. This is the primary way to advance workflow items through the pipe's process steps. Common use cases: moving a request from "New" to "In Review", advancing a lead to "Qualified", or progressing a task to "Completed". The card retains all its field values after moving. Move a card to a different phase in the pipe

  3. 07

    Search cards by field

    This is useful for finding cards by email, name, ID, or any custom field content. You must provide the pipe_id, field_id (the field to search in), and search_value (text to find). Results include card title, current phase, status, and all field values for matching cards. The search uses a "contains" operator for flexible matching. Search cards in a pipe by a specific field value

  4. 08

    Clone card

    You must provide the card_id of the card to clone. The new card is created in the same pipe as the original, starting at the first phase. This is useful for creating similar requests, repeating processes, or using an existing card as a template for new items. The cloned card gets a new unique ID but retains all field data. Clone an existing card to create a duplicate

Capability set03 / 04

09-11

3 capabilities in this set.

Part of 14 available through Pipefy.

  1. 09

    Create card

    You must provide the pipe_id and a JSON object containing field values matching the pipe's required fields. Fields are key-value pairs where keys are field IDs and values are the data to store. Optionally specify a phase_id to start the card in a specific phase (defaults to first phase). Example fields: { "name": "John Doe", "email": "john@example.com", "priority": "High" } Create a new card in a Pipefy pipe

  2. 10

    Get card

    Use the card_id obtained from list_cards to inspect full card information. This is useful for reviewing card details before updating fields or moving to another phase. Get detailed information about a specific card

  3. 11

    List cards

    Cards represent individual items flowing through the pipe's workflow phases (e.g., requests, tasks, tickets, leads). You must provide the pipe_id. Optionally filter by phase_id to see cards in a specific phase. Each card includes title, current phase, completion status, due date, and assignees. Use this to monitor workflow progress and identify cards that need attention. List all cards in a pipe with optional phase filter

Capability set04 / 04

12-14

3 capabilities in this set.

Part of 14 available through Pipefy.

  1. 12

    List phases

    Each phase represents a stage that cards flow through in the process. Use this to understand the workflow structure and identify phase IDs for filtering cards or moving cards between phases. The response includes phase names and card counts. List all phases in a pipe

  2. 13

    List pipes

    Each pipe represents a structured workflow with phases, fields, and cards. You must provide the organization_id which can be found in your Pipefy URL or obtained from get_user_profile. Use this to discover all available pipes before managing cards within them. List all pipes in an organization

  3. 14

    Update card field

    You must provide the card_id, the field_id of the field to update, and the new value as a string. This is useful for updating card information as requests progress or details change. Common updates: changing priority, updating contact info, modifying descriptions, or setting dates. Update a specific field value on a card

Observed, not estimated

931ms average. Fast in production.

Pipefy is checked daily against the live service.

Daily averagePeak 1082ms
Aug 20Today
Fastest day
779ms
Slowest day
1082ms
14-day trend
Slowing+16%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 14 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Pipefy, so you can see the experience inside your AI.

It does not authenticate your account with Pipefy. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Pipefy Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_0jLK89rkHO1lUYBbfrE97LkZ5Zz4CLCz35Qe76YH/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Pipefy capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "pipefy-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_0jLK89rkHO1lUYBbfrE97LkZ5Zz4CLCz35Qe76YH/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

FAQ

Questions Pipefy owners ask.

  • 01

    How do I get a Pipefy API token and where do I find it?

    Log in to Pipefy, click on your Profile icon (top-right), go to Profile > API Access, and generate a new token. Alternatively, use Service Accounts for team-based access. Copy the token immediately. it starts with eyJhbG.... Paste it into the API token field below. This token authenticates all GraphQL API requests to https://api.pipefy.com/graphql.

  • 02

    How do I move a card from one phase to another in a pipe?

    Use the move_card_to_phase capability with the card_id (from list_cards or get_card) and the target phase_id (from get_pipe or list_phases). This advances the card through your workflow. For example, moving a card from 'New Requests' to 'In Review' phase. The card retains all its field values after moving. This is the primary way to progress items through your process.

  • 03

    Can I search for cards by a specific field value like email or customer name?

    Yes! Use the search_cards_by_field capability with the pipe_id, field_id (the specific field to search in), and search_value (the text to find). This searches all cards in the pipe where that field contains your search text. It's perfect for finding cards by customer email, name, order number, or any custom field. Results include full card details with all field values.

  • 04

    How do I create a new card with custom field values?

    Use the create_card capability with the pipe_id and a JSON object containing field values. The fields parameter should be a JSON object where keys are field IDs (from get_pipe) and values are the data to store. Example: { "name": "John Doe", "email": "john@example.com", "priority": "High" }. You can also optionally specify a phase_id to start the card in a specific phase instead of the default first phase.

Explore

More in Project Management

Suggestions