👤 For customers who want to understand and use Pipefy Copilot
🔐 Available to companies participating in the closed beta
🎯 To clarify access, capabilities, approvals, credits, and support
Available from November 18, 2026 for companies participating in the closed beta.
For practical examples of improving an existing process or creating a new one, read Getting started with Copilot in Pipefy.
Find your question:
1. Overview
What is Pipefy Copilot?
It is Pipefy’s agentic process specialist, which lets you create, optimize, run, and get insights into your pipes through conversation. At your request, Pipefy Copilot can configure and build:
- Processes, including the detailed phases they need;
- Card fields and field visibility rules;
- Deterministic automations and AI Agents, including their identity, knowledge bases, and behaviors;
- Data tables;
- Reports and interfaces.
How is Pipefy Copilot different from Pipefy Builder?
Pipefy Builder is an AI tool that lets you create basic pipes through conversation. It provides a starting structure for a new pipe, while detailed settings need to be configured manually. Pipefy Copilot goes beyond that basic structure: it can configure multiple elements in your new pipes to match your process needs. It also has access to a broader set of tools, capabilities, and context than Pipefy Builder. This lets you optimize pipes after creating them, perform actions in your pipes, and quickly access process information and data.
Does Pipefy Copilot replace the settings screens?
No. Everything Pipefy Copilot does can be reviewed and adjusted through the existing screens. No Pipefy feature depends on Pipefy Copilot to work.
What does “closed beta” mean?
It means the product is still being developed but is available for Pipefy customers to test. While the product is under evaluation, stability, availability, and response times may vary, and features may be adjusted or changed.
2. Access and participation
Who can use Pipefy Copilot during the closed beta?
Pipefy Copilot is available to a selected group of customers from November 18, 2026 and will be rolled out gradually. If your company is included, you or your Pipefy administrator will receive a notification inside the product.
How do I enable it?
For selected customers, Pipefy Copilot is already enabled. No additional configuration is needed.
My company has not received an invitation. Can I request access?
Yes, you can request early access to Pipefy Copilot. If your company has a CSM, contact them directly. Otherwise, submit your request through our support channels.
Can I disable Pipefy Copilot if I do not want to use it?
An administrator can turn off Pipefy Copilot for the entire company in the administration panel. Using it is optional. Although its icon is available in the platform, Pipefy Copilot only acts when you start a conversation and approve a plan. Your company loses no platform capabilities by choosing not to use it.
How much does it cost?
Pipefy Copilot is free and unlimited during the closed beta. If conditions change after the closed beta, they will be clearly communicated in advance.
A note on AI credits. Using Pipefy Copilot does not consume credits. However, the AI Agents and AI automations you create with its help work like any other AI Agent or AI automation in your company: once they start running tasks, they consume credits according to your plan. Like any AI, Pipefy Copilot can make mistakes, and its work needs to be reviewed.
3. Where can I find Pipefy Copilot?
On Home. When you open Pipefy, look for the icon next to your profile photo in the top right corner. Click it to open the Pipefy Copilot chat and start a conversation.
Inside a pipe. When you open a pipe, a floating icon is also available in the bottom right corner. You use it in the same way as on Home, but Pipefy Copilot is already working in the context of that pipe and can help with the process on your screen.
In Interfaces. When you open the Interfaces section, you will also see the Pipefy Copilot icon. Here, it is particularly suited to helping you create new interfaces.
4. What can Pipefy Copilot do?
First, remember that Pipefy Copilot acts with your permissions. It can only do what your account is allowed to do in Pipefy. For example, if you are not a pipe administrator, it will not change that pipe’s structure.
4.1 Processes (pipes)
| You can ask | Example |
|---|---|
| Create a complete process at once, with phases, start form fields, and labels | "Create a purchase request process with the phases Request, Manager approval, Finance approval, Purchasing, and Completed." |
| Duplicate an existing process | "Make a copy of the Onboarding pipe for the Rio office." |
| Change a process’s settings | "Rename the pipe to Purchasing 2027." |
| Delete a process | "Delete the test pipe we created." |
| Find processes | "Which pipes do we have for contracts?" |
| Understand a process’s structure | "What are the phases and fields in the Recruitment pipe?" |
4.2 Phases
| You can ask | Example |
|---|---|
| Create a phase, including between two existing phases | "Create a Legal review phase between Negotiation and Signature." |
| Rename a phase and adjust settings such as deadlines and descriptions | "Rename Triage to Initial review and set a deadline of 2 days." |
| Delete a phase | "Delete the On hold phase from the Purchasing pipe." |
| Find out which phases a card can move to | "Where can cards in the Approval phase move?" |
4.3 Fields
| You can ask | Example |
|---|---|
| Create fields in the start form or a phase, including text, number, date, selection, attachment, assignee, connection, and other Pipefy field types | "Add a date field called Required by and a selection field called Cost center to the start form, with the options Sales, Marketing, and IT." |
| Create a connection field linking to another pipe or a table | "Add a field that connects the request to its supplier in the Suppliers table." |
| Change a field’s name, required status, options, and description | "Make Cost center required and add the Finance option." |
| Delete a field | "Delete the Old notes field from the Purchasing phase." |
4.4 Field visibility rules (conditionals)
| You can ask | Example |
|---|---|
| Show or hide fields based on other field values | "Show the Justification field only when the amount is above R$ 10,000." |
| View, change, and delete existing rules | "Which field visibility rules exist in the Purchasing pipe’s start form?" |
4.5 Labels
| You can ask | Example |
|---|---|
| Create, rename, change the color of, and delete pipe labels | "Create a red Urgent label in the Purchasing pipe." |
| Apply or remove labels on a specific card | "Add the Urgent label to card 123 and remove Low priority." |
4.6 Cards
| You can ask | Example |
|---|---|
| Create a card in the start form or directly in a phase | "Create a purchase card for 10 laptops for the Sales team." |
| Fill in phase fields | "Fill in the finance opinion on card 123 with: approved." |
| Update a card’s title, assignees, labels, and due date | "Assign Ana and set the due date to Friday." |
| Move a card to another phase | "Move card 123 to Finance approval." |
| Add, edit, or delete comments | "Comment on card 123: waiting for the second supplier’s quote." |
| Connect cards across processes | "Link this request to contract 456." |
| Delete a card | "Delete card 789, which was created as a duplicate." |
4.7 Finding and analyzing cards
| You can ask | Example |
|---|---|
| Find and filter cards by phase, labels, assignees, and creator | "Which cards labeled Urgent are assigned to Ana in Approval?" |
| Find and filter cards by creation date, due date, and other dates | "Which of Ana’s cards are due this week?" |
| Find and filter cards by title and field values | "List the candidates who entered in October and have not passed triage yet." |
| Count cards | "How many requests above R$ 5,000 are in Approval?" |
4.8 Connections between processes
| You can ask | Example |
|---|---|
| Create, change, and delete parent and child pipe connections, including automatic field filling | "Connect Purchasing to Payments, with Purchasing as the parent, and copy the amount and supplier to the payment card." |
| Link cards through these connections | "Link request 123 to payment 456." |
| View the cards connected to a card | "Which payments are linked to request 123?" |
4.9 Data tables
| You can ask | Example |
|---|---|
| Create a table with its columns | "Create a Suppliers table with CNPJ (Brazilian company tax ID), legal name, contact, and category." |
| Change or delete tables and columns | "Add a Phone column to the Suppliers table." |
| Create, edit, find, and delete records | "Register supplier X." / "Which suppliers are in the IT category?" |
| Attach a file to a record | "Attach the contract at this link to supplier X’s record: https://exemplo.com/contrato.pdf" |
4.10 Automations
| You can ask | Example |
|---|---|
| Create rules with conditions that follow “when X happens, do Y” | "When a card reaches Approved and the amount is above R$ 10,000, move it to Executive approval." |
| Create rules that generate tasks for people | "When a card enters Purchasing, send a task to the Procurement team." |
| List, explain, change, enable, disable, and delete rules | "Which automations exist in this pipe, and what does each one do?" |
| Copy values between fields or record dates automatically | "When the card is created, fill in Entry date with today’s date." |
Note: new automations created by Pipefy Copilot are enabled. Existing automations changed at your request are switched off so you can review them before using them.
4.11 AI automations
| You can ask | Example |
|---|---|
| Create rules in which AI fills in one or more card fields based on an instruction | "When a card is created, use AI to summarize its description in the Summary field." |
| Validate the instruction before creating the automation | "Before creating it, check whether this instruction works: classify the request as Urgent or Normal based on its description." |
| Change, enable, disable, and delete AI automations | "Disable the AI automation that summarizes the description." |
4.12 AI Agents
| You can ask | Example |
|---|---|
| Create a complete AI Agent, with general instructions and 1 to 5 behaviors, each with a trigger, instructions, and actions | "Create an agent that reads the attached quote when a purchase card is created, fills in the amount and supplier, and moves the card to Approval." |
| Use behavior triggers such as card created, card moved into a phase, card left a phase, field updated, deadline alert (late, overdue, expired), email received on a card, all child cards in a phase, HTTP request response, or manual trigger | "When the card is late, have the agent notify the assignee by email." |
| Give an agent actions to move a card, fill in fields with AI, create a card, create a connected card, create a table record, send an email using a template, request human validation, and use a tool from a connected MCP server | "If the amount exceeds R$ 50,000, the agent must request human validation before moving the card." |
| Give an agent knowledge bases consisting of reference texts (up to 3,500 characters each) and data lookups in another pipe | "Use our purchasing policy as the agent’s knowledge base." |
| Enable extra capabilities: advanced document reading (OCR), calculations, web search, and web page reading | "Enable advanced document reading so the agent can read scanned invoices." |
| Validate behaviors before saving to identify problems with fields, phases, and permissions | "Check whether the triage agent has any configuration problems." |
| Enable, disable, change, and delete agents | "Disable the triage agent." |
4.13 Card emails
| You can ask | Example |
|---|---|
| Send email from a card’s inbox when it is enabled in the pipe | "Email the supplier on card 123 to request the invoice." |
| Send email using an existing template, populated with card data | "Send the Order confirmation template to the requester on card 123." |
| Read emails sent and received on a card | "Has the supplier replied to the email on card 123?" |
4.14 Webhooks
| You can ask | Example |
|---|---|
| Create webhooks that notify another system when something happens in a pipe, such as a card being created or moved | "Create a webhook that notifies https://erp.exemplo.com/pipefy whenever a card is moved." |
| List, change, and delete webhooks | "Which webhooks exist in the Purchasing pipe?" |
4.15 Reports
| You can ask | Example |
|---|---|
| Create pipe reports with columns, filters, and formulas | "Create a report of requests approved this month, with amount, requester, and supplier." |
| Create company reports combining multiple pipes | "Create a report of open cards in Purchasing and Payments, with phase and assignee." |
| Change and delete reports | "Add the Cost center column to the approved requests report." |
| Export reports to a file | "Export the approved requests report." |
| Export a pipe’s log | "Export the Purchasing pipe’s log." |
4.16 Monitoring: logs, usage, and credits
| You can ask | Example |
|---|---|
| AI Agents: view execution history, filter by success or failure, and review each execution step | "Why did the triage agent fail yesterday?" |
| Automations: view execution history by pipe or rule, plus success rate, failures, average duration, and last execution metrics | "What is the success rate of automations in the Purchasing pipe this week?" |
| Company usage: automation executions and agent usage over a period | "How many automations ran in the company in October?" |
| AI credits: limit, total consumption, and consumption by feature for the current month, previous month, or last 3 months | "How many AI credits have we used this month, and on what?" |
| Export: automation execution history as a file | "Export the execution history for Purchasing automations." |
4.17 Interfaces
| You can ask | Example |
|---|---|
| Create the company’s portal and change its name, visibility, and appearance | |
| Create and organize portal pages with text, tables, forms, buttons, links, videos, images, and other elements | |
| Create subportals | |
| Publish or unpublish the portal | |
| HTML interfaces: create custom pages showing live pipe and table data, and define the actions available on the page |
4.18 Advanced automations and integrations (iPaaS)
Coming soon.
4.19 Designing, analyzing, and improving processes
| You can ask | Example |
|---|---|
| Design a process before building it: starting point and end states, steps and owners, decision rules with exact thresholds, exceptions, and required data | "Help me design the reimbursement process. I do not know who approves." |
| Analyze an existing process: manual steps that could be automated, bottlenecks, opportunities for an AI Agent, missing field rules, and related processes | "What could we improve in the Purchasing pipe?" |
| Assess whether an automation is worthwhile: time saved and where to start | "Is it worth using an agent for triage?" |
4.20 Company information
| You can ask | Example |
|---|---|
| Check the company’s plan, number of members, and number of pipes | "How many members and pipes does our company have?" |
5. How Pipefy Copilot carries out actions
Does Pipefy Copilot change anything without telling me?
No. Before making any changes, it shows a plan in business language explaining what will change and where. Nothing changes until you approve.
How does approval work?
- You make a request.
- Pipefy Copilot reads what it needs and responds with a plan.
- You approve or reject the plan.
- If you approve, it asks for final confirmation to publish. Until then, nothing changes in the pipe. Deletions and emails require their own confirmation.
- When you publish, changes are applied in the order shown in the plan.
- If you reject it, nothing changes. Adjust your request and ask for a new plan.
- An individual change outside a plan is applied as soon as you approve it.
Do queries require approval?
No. Reading information never requires confirmation.
What about deletions?
Deletions always require specific confirmation, and Pipefy Copilot describes what will be deleted. Before confirming, check whether the item is used by automations, field rules, or reports: deletion cannot be undone.
What about actions outside Pipefy, such as sending email?
Before sending, Pipefy Copilot shows the message exactly as it will be sent. Once sent, it cannot be undone.
Do automations and agents start running as soon as they are created?
Automations and agents created by Pipefy Copilot start running when you publish the plan. In some cases, such as when a pipe already contains cards a rule would affect, it leaves the item disabled and flags this in the summary. Changing an existing automation or agent preserves its current state: if it was enabled, the new version takes effect after publication. To test it first, ask Pipefy Copilot to leave the item disabled and use a test card.
What happens if part of a plan fails?
Pipefy Copilot reports what was applied, what was not, and what to do next. For example, if the pipe was created but one phase failed, it tells you which phases already exist. Check the process after a partial failure.
Can I undo a Pipefy Copilot action?
There is no undo button yet. Pipes also have no draft mode: changes take effect when you publish the plan. In interfaces, changes remain in draft until you click Publish. To reverse a change, ask Pipefy Copilot itself ("remove the phase you created") or adjust it through the interface. Deletions cannot be undone.
6. What can Pipefy Copilot not do?
- Define which phases a card can move to, beyond the sequence created with the phases
- Change access credentials, roles, or pipe or company members when you lack permission to do so
- Reorder a phase that already contains cards
- Create or edit email templates
- Create an AI Agent with a scheduled trigger
- Read or change data in systems outside Pipefy during the conversation
- Work in Teams, Slack, or WhatsApp
- Attach files to cards or records, including through a link
- Read the contents of attached files. It suggests an AI Agent for this task
- Create a knowledge base from documents such as a PDF. Documents are added through the agent’s screen
- Send notifications or suggestions on its own, without a request
- View or change anything you cannot access
7. Answers, suggestions, and conversations
How does Pipefy Copilot respond?
It uses text and, when useful, tables, charts, alerts, and lists. It aims to identify its information sources and explain when it cannot see something, but it can make mistakes: verify important figures in the pipe itself. When it cannot see something, it says so rather than claiming it does not exist.
What are the suggestions at the end of answers?
Every answer ends with a suggested next step based on what Pipefy Copilot has just reviewed.
Which language does it use?
It responds in the language of your latest message among the supported options: Brazilian Portuguese, English, and Spanish.
Does Pipefy Copilot remember the conversation?
Yes, within the same conversation, including when you switch screens, reload the page, or move from Home to a pipe. Use New chat to start fresh. On another browser or device, earlier messages appear after you send your next message.
Can I view older conversations?
Yes. Open the history to view your past conversations.
Can very long conversations cause problems?
Pipefy Copilot automatically summarizes older parts of the conversation. Use New chat for a new subject to help keep answers faster and more precise.
8. How does Pipefy Copilot handle permissions and security?
Pipefy Copilot always acts as you, with your permissions, and never uses higher permissions to complete a task.
If your account lacks permission, it explains this and does not try another route.
Some areas require specific permissions:
- Pipe administrator access to change the structure;
- Advanced Automations enabled for iPaaS;
- AI enabled in the pipe for AI automations.
Each conversation is restricted to the company you are currently working in.
Administrators can enable or disable Pipefy Copilot for the entire company.
9. How does Pipefy Copilot handle data and privacy?
Conversations are stored in Pipefy’s infrastructure and associated with your company and user account. A recent portion is kept in your browser to maintain the conversation across screens.
Retention: Pipefy processes your AI requests through contracted LLM providers. Data may be retained for up to 30 days solely for abuse prevention and technical maintenance, always in anonymized form or under a Zero Data Retention (ZDR) policy when available.
Is data used to train models?
No. Pipefy does not use your company’s data or process content to train public or shared AI models.
10. What performance and limits should I expect?
Response time: simple questions take a few seconds. Requests that read large amounts of data or make several changes may take close to a minute. Pipefy Copilot shows what it is doing while it works.
Large processes: queries work even in pipes with thousands of cards. Questions about the history of many cards take longer. For large, complex processes, review the plan carefully before approving.
Exports, such as reports and automation history, run in the background: Pipefy Copilot tells you when the file is ready or where to find it.
Usage limit: Pipefy Copilot is free and unlimited during the closed beta. Any later changes to these conditions will be communicated broadly and clearly.
Remember: while the product is under evaluation, stability, availability, and response times may vary, and features may be adjusted or changed.
11. Best practices
- Describe the outcome rather than the implementation. "Requests above R$ 10,000 go through finance" works better than "create a conditional field."
- Start with the design for a new process. Ask "help me design" before "create," especially when decisions remain open, such as who approves or which threshold applies.
- Read the plan before approving. Check the pipes, phases, and fields mentioned, and whether automations and agents will be enabled or disabled.
- Test automations and agents before enabling them in production. Use a test card.
- Check the result. Pipefy Copilot is AI and can make mistakes. Always review its work.
- Use one conversation per subject. Avoid mixing subjects in the same conversation.
- Give feedback. Use the support channels to share your feedback and suggestions.
12. Common problems
| Situation | What to do |
|---|---|
| I cannot see Pipefy Copilot | A selected group of customers can use the closed beta. You can request early access through your CSM, if your company has one, or through Pipefy’s support channels. If your company already participates, check with the administrator that AI and Pipefy Copilot are enabled under AI Tools in the administration panel. |
| Pipefy Copilot says it lacks permission | The action requires a permission your account does not have. Contact the pipe or company administrator. |
| Pipefy Copilot said it made a change, but I cannot see it | Check whether you published the plan: changes do not enter the pipe before publication. If you published it, refresh the page and check. If the change is still missing, contact support with the date, time, and request text. |
| The card will not move to the phase I requested | The destination is not allowed by the current phase’s connections, or a required field is missing. Pipefy Copilot tells you which applies. |
| The agent I created does not run | Ask Pipefy Copilot to check the agent’s logs and validate its behaviors. Check that the agent is enabled and that AI credits are available. |
| The AI automation cannot be created | Check whether AI is enabled in the pipe. |
| The answer is taking too long | Split your request or start a new conversation. |
| The conversation disappeared | If you changed browsers or cleared browser data, send a message to restore the conversation. |
| The answer is wrong or made up | Use the thumbs down button and explain what you expected. Do not approve plans you are unsure about. |
13. Feedback and support
Feedback: through Pipefy’s support channels.
Support: access Pipefy’s support channels directly in the platform.
When reporting a problem, include the request text, date and time, pipe involved, expected result, and a screenshot of the conversation.
Beta notice
Pipefy Copilot (beta). Pipefy Copilot is a Beta Solution made available during the evaluation period under clause 8.4 of the Pipefy Solution Terms of Use and Annex V, Pipefy AI Terms of Use. Its use is optional: the feature is available in the platform but only acts when you start a conversation and approve a plan, and no Pipefy feature depends on it. As a product under testing, it may have instability, errors, or inaccurate responses and may be changed or discontinued at any time. Actions you approve are executed immediately and may not be reversible, including deletions, emails, and the configuration of webhooks and integrations. Review the plan before approving and check the result. AI Agents and AI automations created with Copilot consume AI credits when they run, according to your plan.


