Integration
Connect Escrow and Pipefy
When something happens in Escrow or Pipefy, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Escrow and Pipefy to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)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)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)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)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)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)Example flows
What Escrow and Pipefy can do together
From Escrow to Pipefy
When Transaction updated (instant) in Escrow
then Create Card in Pipefy
From Pipefy to Escrow
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 Escrow and Pipefy
Triggers and actions 7 triggers · 17 actions
- Transaction updated (instant)
Fires when Escrow.com posts a webhook update for a transaction the account is party to (e.g. status/state change during the escrow lifecycle).
- Add customer
Create a new customer record on Escrow.com to be used as a party (buyer/seller/broker) in a transaction.
- Add transaction
Create a new escrow transaction with parties, items, and payment schedule.
- Cancel transaction
Cancel an escrow transaction that has not yet completed.
- Get transaction
Fetch the current details and status of an escrow transaction by ID.
- List partner transactions
List transactions where the caller is acting as the broker/partner rather than a direct party.
- Update customer
Update details on an existing Escrow.com customer record.
- Done Card
Triggers when a card is done.
- Moved Card
Triggers when a card is moved.
- New Card
Triggers when a new card is created.
- New Database Record
Triggers when a new record is created.
- Updated Card Field
Triggers when a card field is updated.
- Updated Record Field
Triggers when a record field is updated.
- Create Card
Creates a card in a Pipefy pipe, filling in its start form fields.
- Create Record
Creates a new table record.
- Delete Card
Permanently deletes a card from its pipe.
- Delete Database Record
Delete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
- Find Card
Returns the cards in a pipe whose chosen field matches the specified value.
- Find Database Records
Find a database records by title.
- Get Card
Retrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
- Get Database Record
Fetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
- Move Card
Moves a Pipefy card to another phase of its pipe.
- Update Card Field
Sets a new value on one field of an existing Pipefy card.
- Update Database Record
Update a database table record's title/fields via the GraphQL `updateTableRecord(input: {id, title})` mutation.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Escrow
Escrow to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Escrow to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Escrow to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Escrow to Google SheetsGoogle Sheets
Escrow to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Escrow to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Pipefy
Google Calendar to PipefyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Mailchimp to PipefyMailchimp marketing automation and email platform.
Questions
Escrow and Pipefy, answered
What can start an automation from Escrow?
Any of Escrow's 1 trigger in the catalog, including Transaction updated (instant). Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefy when something happens in Escrow?
Any of Pipefy's 11 actions, including Create Card, Create Record, Update Card Field and Update Database Record. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Pipefy to Escrow?
Yes. When something happens in Pipefy, your agent can act in Escrow too. This page covers both directions: Pipefy's triggers and Escrow's actions are listed here as well.
Do I have to build a connector for Escrow or Pipefy?
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.
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.