# Pipefy MCP for AI Agents AI Agent Connect > Pipefy MCP lets you manage your organization's workflows directly through your AI agent. Create cards, move them between phases, update custom fields, and search for specific items without ever leaving your chat interface. It turns your AI into a dedicated process manager for all your Pipefy pipes, making it easy to keep tasks moving without manual dashboard navigation. ## Overview - **Category:** project-management - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_0jLK89rkHO1lUYBbfrE97LkZ5Zz4CLCz35Qe76YH/ai-agent-connect - **Tags:** process-management, workflow-automation, task-tracking, business-process-management, data-entry ## Description This Pipefy MCP lets you manage your organization's workflows directly through your AI agent. Managing a complex process usually means constant tab switching and clicking through endless dashboards to move a single task forward. This setup changes that by letting your AI handle the heavy lifting for you. You can tell your agent to find a specific request, update its priority, or move it to the next stage of review without you having to log into Pipefy at all. It is about moving from manual data entry to just giving directions. Whether you are triaging new support tickets or moving a purchase request through the approval chain, your agent handles the repetitive steps. By connecting this to the Vinkius catalog, you get a way to keep your project management moving while you focus on the actual work that needs doing. Your agent acts as a dedicated process manager that understands your pipes, phases, and custom fields. You can check your organization's structure, verify your profile, and list all available processes in one go. It removes the friction of navigating a complex UI and replaces it with a simple conversation. You get a faster way to keep your team on track and your data accurate. ## Tools ### clone_card Create a duplicate of an existing card in the same pipe. This is useful for using an existing card as a template for new items. ### create_card Add a new card to a specific Pipefy pipe with custom field values. This helps you log new requests without manual data entry. ### delete_card Permanently remove a card and all its associated data from a pipe. Use this to clean up test cards or errors. ### get_card Pull the full details of a specific card to review its data. This is helpful before you update fields or move it to a new phase. ### get_organization View the structure of your organization. It helps you understand team membership and discover available pipes. ### get_phase Inspect a specific phase to see what fields are required at that step. This helps you understand the workflow requirements. ### get_pipe Retrieve the structure of a specific pipe. It shows all phases, names, and custom fields defined for that process. ### get_user_profile Check your authenticated profile to verify your API access. It also shows which organizations and pipes you can see. ### list_cards See all cards in a pipe with an optional filter for a specific phase. Use this to monitor progress and find cards needing attention. ### list_phases Get a list of all stages in a pipe. This helps you identify phase IDs for filtering cards or moving them through the workflow. ### list_pipes Discover all available pipes within your organization. This is the first step to finding where your cards live. ### move_card_to_phase Move a card to a different step in the workflow. This is the primary way to advance items from one stage to the next. ### search_cards_by_field Find specific cards by searching for text within a field like email, name, or ID. It uses a contains operator for flexible matching. ### update_card_field Change a specific piece of information on a card. This is useful for updating priority, contact info, or descriptions as requests evolve. ## Prompt Examples **Prompt:** ``` Show me all the cards in the IT Support pipe that are currently stuck in 'Waiting for User'. ``` **Response:** ``` I've checked the IT Support pipe for you. There are currently **3 cards** in the 'Waiting for User' phase: | Card ID | Title | Days Waiting | | :--- | :--- | :--- | | #12345 | Monitor not displaying | 5 days | | #12389 | Keyboard replacement | 2 days | | #12401 | VPN access issue | 1 day | Would you like me to send a follow-up or move any of these to a different phase? ``` **Prompt:** ``` Create a new card in the HR Onboarding pipe for a new hire named Sarah Jenkins. Set her role to 'Engineer' and her start date to next Monday. ``` **Response:** ``` I've created the new onboarding card for you: - **Card ID**: 88291 - **Title**: HR Onboarding - Sarah Jenkins - **Phase**: New Requests - **Fields**: Role: Engineer, Start Date: Next Monday The card is now ready for the HR team to review. Should I move it to the 'Pending Approval' phase now? ``` **Prompt:** ``` Find the card for customer john@example.com and move it to the 'Resolved' phase. ``` **Response:** ``` I found the card for **john@example.com** in the Support pipe. - **Current Title**: VPN access issue - **Current Phase**: In Progress I have successfully moved it to the **Resolved** phase. Is there anything else you need help with for this request? ``` ## Capabilities ### Create new cards Add new items to specific pipes with pre-filled field values. ### Move cards between phases Advance tasks through different stages of your workflow. ### Update card fields Change specific data points on existing cards as information evolves. ### Search cards by field Find specific records using unique identifiers like email or IDs. ### Clone existing cards Duplicate records to create new items from a template. ### View pipe structures Inspect the phases and fields of all pipes in your organization. ### Fetch user profiles Verify your access and see which organizations you belong to. ## Use Cases ### Support Triage A support lead asks the agent to find all cards with a specific email and move them to the 'In Progress' phase. ### Purchase Requests A manager tells the agent to clone a 'Software Request' card and fill in the new user's details and justification. ### Project Tracking An ops person asks the agent to list all cards in the 'Design' pipe that are currently in the 'Review' phase. ### Data Cleanup A user asks the agent to delete all test cards created in the 'Bug Tracking' pipe that are no longer needed. ## Benefits - Skip the dashboard: Use move_card_to_phase to advance tasks without opening a browser tab. - Faster data entry: Use create_card to quickly add new requests with all the necessary fields filled out. - Easy template usage: Use clone_card to duplicate existing requests instead of typing out repetitive details. - Precise lookups: Use search_cards_by_field to find specific tickets by email or ID in seconds. - Dynamic updates: Use update_card_field to keep your project data current as things change in real-time. - Better oversight: Use list_pipes and get_organization to get a high-level view of your entire process. ## How It Works The bottom line is you stop clicking through dashboards and start managing your workflows with plain text. 1. Subscribe to the Pipefy MCP and grab your API token from your Pipefy profile settings. 2. Add your credentials to your AI client to establish the connection. 3. Start asking your agent to create cards, move them through phases, or search for specific records. ## Frequently Asked Questions **Can the Pipefy MCP help me manage my team's tasks?** Yes, it lets you manage cards, move them between phases, and update fields using natural language. This makes it much faster to keep your team's tasks moving without manually clicking through the dashboard. **How does the Pipefy MCP handle moving cards between different stages?** You can simply tell your agent which card to move and which phase it should go to. The Connector handles the transition automatically while keeping all your existing field data intact. **Can I use the Pipefy MCP to find specific requests by email?** Yes, you can search for cards using specific field values like email addresses. This is great for quickly locating customer requests in a high-volume pipe. **Does the Pipefy MCP support cloning cards for recurring work?** It does. You can ask your agent to clone an existing card to create a duplicate. This is a great way to use a card as a template for repeating processes. **Can I use the Pipefy MCP to update specific fields on a card?** Absolutely. You can tell your agent to change specific pieces of information, such as the priority level, status, or contact details on any card in your pipes. **How do I connect the Pipefy MCP to my AI client?** Once you subscribe, you just need to provide your Pipefy API token. Your AI client will then be able to see your pipes and perform actions on your behalf. **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`. **How do I move a card from one phase to another in a pipe?** Use the `move_card_to_phase` tool 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. **Can I search for cards by a specific field value like email or customer name?** Yes! Use the `search_cards_by_field` tool 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. **How do I create a new card with custom field values?** Use the `create_card` tool 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.