# Pipefy integrations: cards and pipes

> Create a card, create a pipe and create a table record in Pipefy, and start a workflow when Pipefy sends “Card created”.

**Canonical page:** https://tray.ai/connectors/pipefy-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Pipefy is a process management tool where teams run workflows such as purchasing, hiring and onboarding as cards that move through phases of a pipe. Tray.ai connects to Pipefy through the HTTP Connector, so your workflows can call the Pipefy API alongside the rest of your stack.

## Use cases

### Cards

Read, create, update, and delete cards in Pipefy from any Tray.ai workflow. The Pipefy API covers calls such as get a card and list cards.

- Get a card
- List cards
- Create a card

### Pipes

Read, create, update, and delete pipes in Pipefy from any Tray.ai workflow. The Pipefy API covers calls such as get a pipe and create a pipe.

- Get a pipe
- Create a pipe
- Update a pipe

### Table records

Read, create, update, and delete table records in Pipefy from any Tray.ai workflow. The Pipefy API covers calls such as list table records and create a table record.

- List table records
- Create a table record
- Update a table record

### Webhooks

Read, create, update, and delete webhooks in Pipefy from any Tray.ai workflow. The Pipefy API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

### Pipefy events

Start a Tray.ai workflow the moment something happens in Pipefy. Pipefy sends events such as card created and card moved to a Tray.ai webhook trigger.

- Card created
- Card moved
- Card field updated

## Challenges Tray.ai solves

### Keeping Pipefy credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Pipefy credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Pipefy API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Pipefy API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Pipefy?

Yes. Tray.ai connects to Pipefy through the HTTP Connector, which calls the Pipefy API directly. Any call the Pipefy API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Pipefy?

The Pipefy API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Pipefy connector?

Pipefy runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Pipefy connector from the Pipefy API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/