Pipefy API

Name: Pipefy API API
Brand: Pipefy API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityTask Managementbearer1 EndpointsREST

For Agents

Manage workflow pipes, cards, phases, and automations through a GraphQL endpoint for business process automation including approvals, onboarding, and service requests.

Quickstart

Get started with Pipefy API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a workflow card in a process pipe"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Pipefy API API.

Create and move cards through workflow phases for process automation

Query pipes and their phases to understand workflow structure

Manage card fields and attachments for work item data

Configure workflow automations and conditional triggers

Track process metrics and card movement through stages

GET STARTED

Start building with Pipefy API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Pipefy API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Pipefy API, keeping it validated and agent-ready. Pipefy API provides workflow and process automation through a GraphQL endpoint. The API enables managing pipes (workflow boards), cards (work items), phases (stages), fields, and automations, allowing teams to build, customize, and operate business processes including approvals, onboarding, procurement, and service requests.

Use Cases

Patterns agents use Pipefy API API for, with concrete tasks.

★ Business Process Automation

Automate approval workflows, procurement requests, and service delivery through Pipefy pipes. The GraphQL API creates cards in the appropriate pipe, moves them through phases as conditions are met, and triggers notifications at each stage. Teams replace email-based approvals with structured, trackable processes.

Create a new card in pipe ID 12345 with title 'Purchase Request' and fields for amount, vendor, and justification

Employee Onboarding Workflow

Manage new hire onboarding through a structured Pipefy pipe with phases for IT setup, HR paperwork, team introductions, and training. The API creates onboarding cards automatically when new employees are added, tracks completion of each phase, and notifies responsible parties at each stage.

Create an onboarding card for new employee 'John Smith' with start date and department fields, then query the phase structure of the onboarding pipe

Service Request Management

Process service requests through configurable pipes with intake forms, approval phases, and completion tracking. Pipefy handles the request lifecycle from submission through fulfillment, with fields capturing request details and phases enforcing the correct processing order.

Query all cards in the 'Pending Approval' phase of the service request pipe and list their titles and creation dates

AI Agent Process Orchestration

AI agents use the Pipefy API through Jentic to create cards, query workflow status, and advance processes without manual intervention. Agents search for workflow operations by intent, load the GraphQL schema, and execute mutations with Jentic handling Bearer token authentication.

Search Jentic for 'create workflow card', load the Pipefy GraphQL endpoint schema, and create a card with custom field values in the target pipe

Key Endpoints

1 endpoints — jentic publishes the only available openapi specification for pipefy api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/graphql

Execute GraphQL queries and mutations for all pipe operations

POST

/graphql

Execute GraphQL queries and mutations for all pipe operations

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Pipefy Bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens so raw personal access tokens never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'create a workflow card') and Jentic returns matching Pipefy GraphQL operations with their schemas, so the agent can construct the right mutation without reading GraphQL docs.

Time to first call

Direct Pipefy integration: 2-3 days for GraphQL schema exploration, auth setup, and mutation building. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Trello API

Trello provides simpler kanban boards without Pipefy's process automation and conditional logic

Use Trello when you need lightweight kanban boards without complex phase automations, conditional fields, or approval workflows.

Alternative

Asana API

Asana offers project and task management with portfolio views and workload tracking

Use Asana when you need project portfolio management, workload balancing, or team-level task tracking rather than structured process automation.

Complementary

n8n API

n8n provides workflow automation between services that can trigger Pipefy card creation and movement

Use n8n when you need to connect Pipefy with external services, trigger card creation from webhooks, or build cross-service automation chains.

FAQs

Specific to using Pipefy API API through Jentic.

Why is there no official OpenAPI spec for Pipefy API?

Pipefy uses a GraphQL API rather than REST, so there is no native OpenAPI specification. Jentic generates and maintains this OpenAPI wrapper so that AI agents and developers can discover Pipefy operations via structured tooling. Get started at https://app.jentic.com/sign-up.

What authentication does the Pipefy API use?

The Pipefy API uses Bearer token authentication. You generate a personal access token or OAuth token in the Pipefy app and pass it in the Authorization header. Through Jentic, this token is stored encrypted in the MAXsystem vault.

Can I create and move cards through workflow phases with the Pipefy API?

Yes. Use the createCard GraphQL mutation to add work items to a pipe, and moveCardToPhase to advance them through stages. You can also update card fields and add comments at each phase transition.

Is the Pipefy API REST or GraphQL?

The Pipefy API is GraphQL, accessed through a single POST /graphql endpoint. All operations (queries and mutations for pipes, cards, phases, fields) go through this endpoint with different GraphQL payloads.

How do I create a workflow card through the Pipefy API using Jentic?

Search Jentic for 'create workflow card', load the /graphql operation schema, and execute a createCard mutation with pipe ID and field values. Jentic handles Bearer token injection and GraphQL request formatting.

Can I query cards by phase or status in Pipefy?

Yes. Use the allCards query with phase_id filter to retrieve cards in a specific phase. You can also filter by assignee, due date, and custom field values to find cards matching specific criteria across your workflow.