Integration
Connect Fluent Support and PyPI
When New Customer fires in Fluent Support, your agent runs Get package in PyPI, or New package in PyPI to Add Tag to Ticket in Fluent Support. 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 Fluent Support and PyPI 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 Fluent Support and PyPI can do together
From Fluent Support to PyPI
When New Customer in Fluent Support
then Get package in PyPI
When New Ticket in Fluent Support
then Get release in PyPI
From PyPI to Fluent Support
When New package in PyPI
then Add Tag to Ticket in Fluent Support
When New release in PyPI
then Create Customer in Fluent Support
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 Fluent Support and PyPI
Triggers and actions 4 triggers · 12 actions
Trigger
New CustomerTriggers when a new customer is added in Fluent Support.
Trigger
New TicketTriggers when a new support ticket is created in Fluent Support.
Action
Add Tag to TicketAdds an existing tag to a Fluent Support ticket.
Action
Close TicketCloses a Fluent Support ticket.
Action
Create CustomerCreates a new customer in Fluent Support with their name, email, contact details and an optional note.
Action
Create TicketCreates a new support ticket in Fluent Support for an existing customer.
Action
Get TicketReturns a Fluent Support ticket with its customer, responses and details.
Action
List CustomersReturns the customers in your Fluent Support help desk, optionally filtered by a search term.
Action
List TicketsReturns support tickets from Fluent Support, optionally matching a search term.
Action
Reopen TicketReopens a closed Fluent Support ticket.
Action
Reply to TicketAdds an agent reply or internal note to a Fluent Support ticket, optionally closing the ticket.
Action
Update TicketUpdates one property of a ticket — its priority, customer priority, assigned agent or product.
Trigger
New packageFires when a new package is published to PyPI, via the site-wide newest-packages RSS feed (/rss/packages.xml).
Trigger
New releaseFires when a watched PyPI package publishes a new release, via that package's release RSS feed (/rss/project/{name}/releases.xml).
Action
Get packageLook up a PyPI package's latest metadata, release list, and project URLs.
Action
Get releaseLook up metadata for one specific version of a PyPI package, including its files and known vulnerabilities.
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 Fluent Support
Fluent Support to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Fluent Support to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Fluent Support to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Fluent Support to Google SheetsGoogle Sheets
Fluent Support to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Fluent Support to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into PyPI
HubSpot to PyPIHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to PyPIGoogle Sheets
Gmail to PyPIGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to PyPIGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to PyPIGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to PyPIMailchimp marketing automation and email platform.
Questions
Fluent Support and PyPI, answered
What can start an automation from Fluent Support?
Any of Fluent Support's 2 triggers in the catalog, including New Customer and New Ticket. Describe the moment in plain language and your agent picks the right one.
What can your agent do in PyPI when something happens in Fluent Support?
Any of PyPI's 2 actions, including Get package and Get release. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from PyPI to Fluent Support?
Yes. When something happens in PyPI, your agent can act in Fluent Support too. This page covers both directions: PyPI's triggers and Fluent Support's actions are listed here as well.
Do I have to build a connector for Fluent Support or PyPI?
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.