Pipefy review

Pipefy is a no-code platform for building workflows and coordinating business processes. Rather than handling only task tracking, it combines forms, portals, apps, messaging, analytics and integrations so teams can route work between people and systems. The product also includes AI agents, which users can build with visual tools or natural-language prompts, plus pre-built agents intended to orchestrate workflows and connect external systems.

Automation combines native tools with iPaaS connections. Pipefy also brings WhatsApp, Teams and Slack conversations into workflows, and offers secure portals with controlled access for different audiences. Usage monitoring is designed to help teams track consumption and credits.

That breadth may suit teams replacing a mix of intake forms, approval flows and system handoffs. It also means buyers should pin down which capabilities are included in their chosen plan: the available plan details list firm usage caps, but do not map every feature to each tier.

Pipefy’s appeal is the range of process pieces it puts under one roof. Teams can collect requests through forms or portals, route work through visual workflows, automate handoffs and bring external conversations into the process. That can reduce the need to stitch together separate tools for intake, approvals and status updates—assuming the plan and integrations cover the use case.

The AI-agent options add another layer: the product description includes both pre-built agents and ways to create agents with visual tools or natural-language prompts. Usage monitoring is also useful in principle for teams that need to keep an eye on consumption, though the published plan details do not say how credit allowances or overages are priced.

There is a free entry point. Starter costs $0 and allows up to 10 users, 5 processes, 50 cards per month, 15 automation jobs per month and 2GB of storage. That gives a small team room to map a basic workflow before committing to an undisclosed paid price. A Reddit discussion about Zapier also suggests a moved-card trigger can be followed by a check for the desired stage, though one commenter was unsure where to configure that filter.

The biggest buying problem is price visibility. Business is billed per user, but its monthly and annual prices are not published. Enterprise requires contacting sales, and prices for Business custom integrations, Enterprise workflow and professional services, and overages are also not published. Teams comparing a migration against their current stack cannot calculate the full bill from the available figures.

Starter’s caps are concrete: 5 processes, 50 cards and 15 automation jobs per month, plus 10 users and 2GB of storage. Business removes user and process limits, but still caps guest users at 100, interfaces at 20, automation jobs at 300 per month and API calls at 500 per month. Enterprise lists 100 interfaces, 2,000 automation jobs and 10,000 API calls per month; database records and storage are custom.

That makes the free tier a useful starting point, not proof that a growing workflow will stay inexpensive. Buyers should ask for written pricing that covers usage, integrations and services before switching.

Pipefy’s Starter plan is free, but capped at 10 users, 5 processes, 50 cards a month, 15 automation jobs a month and 2GB of storage. That may suit a small team testing basic workflows; teams that hit those limits need to consider a paid tier.

Business is billed per user, but Pipefy does not publish monthly or annual prices. It includes unlimited users and processes, up to 100 guest users, 20 interfaces, 300 automation jobs a month and 500 API calls a month. Enterprise pricing is also contact-sales, with 100 interfaces, 2,000 automation jobs and 10,000 API calls listed. The move from Starter to paid plans is therefore a capacity jump, but its dollar cost is not possible to calculate from published prices.

Watch for extras: Business custom integrations and Enterprise workflow and professional services cost extra, with prices not published. Overage costs are also unpublished. Get a quote that spells out billing, add-ons and usage charges before budgeting.

The published material does not specify migration tools, data-export formats or migration services, so we can’t verify how easily existing processes or records move in or out. Before switching, map the workflows, forms, portals, integrations and messaging your team depends on; Pipefy brings those capabilities together, and rebuilding or reconnecting them may affect the effort. Treat that as a planning risk, not a confirmed migration requirement.

Lock-in is also hard to assess without export and contract details. Ask Pipefy what you can export, in what format, and whether cards, attachments, automation rules and integration settings are included. Confirm how guest access, API calls and automation usage are counted on the proposed plan.

The published material includes no Reddit posts, so we can’t attribute reasons for leaving to Reddit users. For a credible switching decision, request export and termination terms in writing, and price the destination platform against your actual process and usage needs.