Integration
Connect Energos and Pipefy
When New Request fires in Energos, your agent runs Create Record in Pipefy, or Moved Card in Pipefy to Add work order comment in Energos. Describe the whole flow 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 Energos and Pipefy to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne 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.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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Energos and Pipefy can do together
From Energos to Pipefy
When New Request in Energos
then Create Record in Pipefy
When New Work Order in Energos
then Update Database Record in Pipefy
From Pipefy to Energos
When Moved Card in Pipefy
then Add work order comment in Energos
When New Card in Pipefy
then Create Work Order in Energos
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 Energos and Pipefy
Triggers and actions 9 triggers · 30 actions
Trigger
New RequestTriggers when a new maintenance request is submitted in Energos.
Trigger
New Work OrderTriggers when a new work order is created in Energos.
Trigger
Work Order Status ChangeTriggers when a work order in Energos moves to a different status.
Action
Add meter readingLogs a new reading against a meter, recording one or more measured values with an optional note, time and user.
Action
Add partCreates a new part in the Energos inventory, with its stock levels, storage locations and linked assets, teams and vendors.
Action
Add siteCreates a new location / site in Energos.
Action
Add userCreates a new user in your Energos organization with a name, email and role.
Action
Add vendorCreates a vendor in Energos with optional contacts and associated sites and assets.
Action
Add work order commentAdds a comment, with optional text and a single file attachment, to an Energos work order.
Action
Create Work OrderCreates a work order in Energos with a title and optional description, priority, work type, due date, site and asset.
Action
Delete assetDeletes an asset from Energos.
Action
Delete work orderDeletes a work order in Energos.
Action
Get Work OrderReturns one Energos work order by its ID, including status, priority, site and asset.
Action
List assetsReturns all assets in your Energos organization, optionally with their site details.
Action
List partsReturns the parts in your Energos inventory, including stock levels, costs and locations.
Action
List sitesReturns the locations / sites in your Energos organization.
Action
List usersReturns all users in your Energos organization, with their name, email, mobile number and role.
Action
List vendorsReturns the vendors in your Energos organization, optionally with their associated assets and sites expanded.
Action
List work ordersReturns the work orders in your Energos organization, optionally with related assets, sites and assignees expanded.
Action
Update assetUpdates an existing asset's category, basic details, financial and manufacturer information. Only the fields you fill in are changed.
Action
Update siteUpdates an existing location / site's name, address or coordinates. Only the fields you fill in are changed.
Action
Update Work Order StatusChanges the status of an Energos work order (Open, On Hold, In Progress, Done, or a custom status).
Trigger
Done CardTriggers when a card is done.
Trigger
Moved CardTriggers when a card is moved.
Trigger
New CardTriggers when a new card is created.
Trigger
New Database RecordTriggers when a new record is created.
Trigger
Updated Card FieldTriggers when a card field is updated.
Trigger
Updated Record FieldTriggers when a record field is updated.
Action
Create CardCreates a card in a Pipefy pipe, filling in its start form fields.
Action
Create RecordCreates a new table record.
Action
Delete CardPermanently deletes a card from its pipe.
Action
Delete Database RecordDelete a database table record by ID via the GraphQL `deleteTableRecord(input: {id})` mutation.
Action
Find CardReturns the cards in a pipe whose chosen field matches the specified value.
Action
Find Database RecordsFind a database records by title.
Action
Get CardRetrieves a single Pipefy card by its id, including its phase, pipe, assignees, labels, attachments and field values.
Action
Get Database RecordFetch a single database table record by ID via the GraphQL `table_record(id: ID)` query.
Action
Move CardMoves a Pipefy card to another phase of its pipe.
Action
Update Card FieldSets a new value on one field of an existing Pipefy card.
Action
Update Database RecordUpdate 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 Energos
Energos to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Energos to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Energos to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Energos to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Energos to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Energos to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Pipefy
GrowSurf to PipefyGrowSurf is referral software for B2C and B2B tech companies.
HubSpot to PipefyHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PipefyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to PipefyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PipefyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PipefyGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Energos and Pipefy, answered
What can start an automation from Energos?
Any of Energos's 3 triggers in the catalog, including New Request, New Work Order and Work Order Status Change. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Pipefy when something happens in Energos?
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 Energos?
Yes. When something happens in Pipefy, your agent can act in Energos too. This page covers both directions: Pipefy's triggers and Energos's actions are listed here as well.
Do I have to build a connector for Energos 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.
Can my AI client use Energos and Pipefy 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.