---
title: "Connect Pipefy and Trengo - APIANT.ai"
description: "When \"Moved Card\" fires in Pipefy, your agent runs \"Add internal note to ticket\" in Trengo, or \"New Internal Note\" in Trengo to \"Create Record\" in Pipefy."
canonical: "https://apiant.ai/connect/pipefy-to-trengo"
---

# Connect Pipefy and Trengo

When **Moved Card** fires in [Pipefy](https://apiant.ai/connections/pipefy), your agent runs **Add internal note to ticket** in [Trengo](https://apiant.ai/connections/trengo), or **New Internal Note** in Trengo to **Create Record** in Pipefy. Describe the whole flow and it is built, tested on every scenario and kept running.

Pipefy **6** triggers Pipefy **11** actions Trengo **3** triggers Trengo **15** actions

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

## What do you want Pipefy and Trengo to do together?

Give your AI client this address.

`https://mcp.apiant.ai`

One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

### Set it up in your client

### Claude Code

Run this in the directory you want to work in.

`claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai`

Start Claude Code there, approve the server, and sign in in the browser page it opens.

[Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code)

### Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

### Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

[Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp)

Example flows

## What Pipefy and Trengo can do together

### From Pipefy to Trengo

- When **Moved Card** in Pipefy then **Add internal note to ticket** in Trengo
- When **New Card** in Pipefy then **Add ticket** in Trengo

### From Trengo to Pipefy

- When **New Internal Note** in Trengo then **Create Record** in Pipefy
- When **New Outbound Message** in Trengo then **Update Database Record** in Pipefy

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Pipefy and Trengo

## Triggers and actions 9 triggers · 26 actions

- Trigger

**Done Card**

Triggers when a card is done.

- Trigger

**Moved Card**

Triggers when a card is moved.

- Trigger

**New Card**

Triggers when a new card is created.

- Trigger

**New Database Record**

Triggers when a new record is created.

- Trigger

**Updated Card Field**

Triggers when a card field is updated.

- Trigger

**Updated Record Field**

Triggers when a record field is updated.

- Action

**Create Card**

Creates a card in a Pipefy pipe, filling in its start form fields.

- Action

**Create Record**

Creates a new table record.

- Action

**Delete Card**

Permanently deletes a card from its pipe.

- Action

**Delete Database Record**

Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.

- Action

**Find Card**

Returns the cards in a pipe whose chosen field matches the specified value.

- Action

**Find Database Records**

Find a database records by title.

- Action

**Get Card**

Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.

- Action

**Get Database Record**

Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.

- Action

**Move Card**

Moves a Pipefy card to another phase of its pipe.

- Action

**Update Card Field**

Sets a new value on one field of an existing Pipefy card.

- Action

**Update Database Record**

Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.

- Trigger

**New Internal Note**

Fires when an internal note is added to a Trengo ticket.

- Trigger

**New Outbound Message**

Triggers when an outbound message is created.

- Trigger

**Ticket Label Added**

Triggers when a label is added to a conversation.

- Action

**Add internal note to ticket**

Adds an internal note (visible only to agents) to a Trengo ticket.

- Action

**Add ticket**

Create a new support ticket.

- Action

**Add ticket label**

Attaches an existing label to a Trengo ticket.

- Action

**Create a Contact**

Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.

- Action

**Create webhook**

Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.

- Action

**Delete contact**

Delete a contact by id.

- Action

**Delete ticket**

Delete a ticket by id.

- Action

**Find a Contact**

Returns the Trengo contacts that match the search term.

- Action

**Get contact**

Retrieve a single Trengo contact by its id.

- Action

**Get webhook**

Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.

- Action

**List contacts**

List all contacts.

- Action

**List labels**

Lists the ticket labels defined in the Trengo account (first page).

- Action

**List tickets**

Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.

- Action

**Send a Message**

Sends a reply message on an existing Trengo ticket, over the ticket's own channel.

- Action

**Update contact**

Update an existing contact by id.

## Each app on its own

- [ **Pipefy** The easy button for processes and workflows Easily organize and run all your processes in one place, leaving...](https://apiant.ai/connections/pipefy)
- [ **Trengo** Trengo is a team collaboration tool to manage conversations from channels such as web chat, email and...](https://apiant.ai/connections/trengo)

Reviews

## What our customers say

## More from Pipefy

- [ **Pipefy to Trello** Trello is a visual collaboration tool that organizes projects into boards, lists, and cards.](https://apiant.ai/connect/pipefy-to-trello)
- [ **Pipefy to Hyrule Compendium** Hyrule Compendium is an open-source REST service exposing data on every interactive item in The Legend of...](https://apiant.ai/connect/pipefy-to-hyrule-compendium)
- [ **Pipefy to Spaceflight News** Spaceflight News API aggregates news coverage of spaceflight and the space industry from many publishers.](https://apiant.ai/connect/pipefy-to-spaceflight-news)
- [ **Pipefy to SparrowDesk** SparrowDesk is an AI-first helpdesk that unifies customer support across email & chat while automating...](https://apiant.ai/connect/pipefy-to-sparrowdesk)
- [ **Pipefy to Timing** Timing is an automatic time tracking app for macOS.](https://apiant.ai/connect/pipefy-to-timing)
- [ **Pipefy to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/pipefy-to-salesforce)

## More into Trengo

- [ **OpenAI to Trengo** OpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...](https://apiant.ai/connect/openai-to-trengo)
- [ **CloudConvert to Trengo** CloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...](https://apiant.ai/connect/cloudconvert-to-trengo)
- [ **elmah.io to Trengo** Cloud logging for.NET web applications using ELMAH.](https://apiant.ai/connect/elmah-io-to-trengo)
- [ **Postman to Trengo** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/postman-to-trengo)
- [ **HubSpot to Trengo** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-trengo)
- [ **Salesforce to Trengo** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-trengo)

Questions

## Pipefy and Trengo, answered

###

### What can start an automation from Pipefy?

Any of Pipefy's 6 triggers in the catalog, including Moved Card, New Card, New Database Record and Updated Card Field. Describe the moment in plain language and your agent picks the right one.

###

### What can your agent do in Trengo when something happens in Pipefy?

Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.

###

### Can it also run from Trengo to Pipefy?

Yes. When something happens in Trengo, your agent can act in Pipefy too. This page covers both directions: Trengo's triggers and Pipefy's actions are listed here as well.

###

### Do I have to build a connector for Pipefy or Trengo?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

###

### Can my AI client use Pipefy and Trengo without building an automation?

Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.

###

### What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

###

### Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.
