Integration
Connect Pipefy to DistrictAPI
When something happens in Pipefy, your agent does the next thing in DistrictAPI. 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 Pipefy and DistrictAPI 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 Pipefy can start in DistrictAPI
When Moved Card in Pipefy
then Batch lookup districts in DistrictAPI
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 DistrictAPI
Triggers and actions 6 triggers · 19 actions
- 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.
- Batch lookup districts
Looks up several school districts at once by their NCES LEA IDs and returns the full district profile for each one.
- Find districts by name, state or county
Returns the school districts matching the name, state or county you supply.
- Get district
Returns the full profile of one school district, including its address, grades served, enrollment, finances and boundary.
- Get school
Returns the full profile of one school, including its address, grades served, enrollment and parent district.
- Get school's district
Returns the full profile of the school district a given school belongs to.
- List districts
Returns the school districts serving a street address, a pair of coordinates, or a given NCES LEA ID.
- List schools
Returns the schools near a street address or a pair of coordinates, within the radius you choose.
- List schools by district
Returns the open schools inside a given school district, optionally limited to one school type or to charter schools.
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 Pipefy
Pipefy to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Pipefy to Spaceflight NewsSpaceflight News API aggregates news coverage of spaceflight and the space industry from many publishers.
Pipefy to SparrowDeskSparrowDesk is an AI-first helpdesk that unifies customer support across email & chat while automating...
Pipefy to TimingTiming is an automatic time tracking app for macOS.
Pipefy to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Pipefy to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
More into DistrictAPI
Arxiv to DistrictAPIOpen-access repository API for searching and retrieving scholarly preprints in physics, math, CS, and...
HubSpot to DistrictAPIHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to DistrictAPIGoogle Sheets
Gmail to DistrictAPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Pipefy and DistrictAPI, 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 DistrictAPI when something happens in Pipefy?
Any of DistrictAPI's 8 actions, including Batch lookup districts, Find districts by name, state or county, Get district and Get school. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from DistrictAPI to Pipefy?
DistrictAPI has no triggers in the catalog today, so automations start in Pipefy. If you need the other direction, ask: your agent reads DistrictAPI's API documentation and adds it.
Do I have to build a connector for Pipefy or DistrictAPI?
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.