Integration
Connect Quipu and Request Tracker (RT)
When New Contact fires in Quipu, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Create Contact in Quipu. 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 Quipu and Request Tracker (RT) 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 Quipu and Request Tracker (RT) can do together
From Quipu to Request Tracker (RT)
When New Contact in Quipu
then Create Ticket in Request Tracker (RT)
When New Invoice in Quipu
then Update ticket in Request Tracker (RT)
From Request Tracker (RT) to Quipu
When Ticket Created in Request Tracker (RT)
then Create Contact in Quipu
When Ticket Status Changed in Request Tracker (RT)
then Find Contacts in Quipu
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 Quipu and Request Tracker (RT)
Triggers and actions 5 triggers · 39 actions
Trigger
New ContactTriggers when a new contact is added in Quipu.
Trigger
New InvoiceTriggers when a new invoice is created in Quipu.
Action
Create ContactCreates a contact (client, supplier or employee) in Quipu.
Action
Create Numbering SeriesCreates a numbering series for invoices or other documents.
Action
Delete ContactDeletes a contact.
Action
Delete InvoiceDeletes an invoice.
Action
Find ContactsFinds contacts by kind, tax ID, email, country or free text.
Action
Get ContactReturns one contact by its ID.
Action
Get InvoiceReturns one invoice by its ID.
Action
Get Simplified InvoiceReturns one simplified invoice (ticket) by its ID.
Action
List Accounting CategoriesLists the accounting categories (income and expense accounts).
Action
List Accounting SubcategoriesLists the accounting subcategories.
Action
List Additional IncomesLists additional incomes.
Action
List Book EntriesLists all book entries (invoices, tickets, paysheets and other documents).
Action
List Economic ActivitiesLists the business's economic activities (IAE).
Action
List InvoicesLists invoices, filtered by kind, contact or date period.
Action
List LiquidationsLists liquidations: payments matched to documents.
Action
List Money AccountsLists bank and cash accounts.
Action
List Money EntriesLists bank and cash movements.
Action
List Numbering SeriesLists the numbering series used to number documents.
Action
List PaysheetsLists paysheets.
Action
List Simplified InvoicesLists simplified invoices (tickets), filtered by kind, contact or period.
Trigger
Ticket CorrespondenceTriggers when a ticket is replied to (that is, corresponded with).
Trigger
Ticket CreatedTriggers when a new Request Tracker ticket is created.
Trigger
Ticket Status ChangedTriggers when a Request Tracker ticket changes status. Can watch for any status change or only for changes to a specific status.
Action
Add assetCreate an asset.
Action
Add userCreate a user.
Action
Comment on a TicketAdd an internal comment to a ticket and send to any internal watchers.
Action
Create TicketCreate a new ticket in Request Tracker.
Action
Find AttachmentLocate an attachment by ID.
Action
Find TicketLocate a ticket by ID.
Action
Find TicketsIssue a query to find matching tickets.
Action
Find TransactionFind a transaction by ID
Action
Get assetRetrieves one asset by ID: name, description, status, catalog, owner, held by, contact, custom fields.
Action
Get queueGet a queue by id or name.
Action
Get userGet a user by id or name.
Action
List queuesList all queues visible to user.
Action
List ticket historyList transactions of a ticket.
Action
Reply to a TicketReply to the requestor and any internal or external watchers of a ticket.
Action
Update ticketGeneral ticket update (Owner, Priority, Queue, custom fields).
Action
Update Ticket Due DateUpdate the due date of a ticket.
Action
Update Ticket StatusUpdate the status of a ticket.
Action
Update Ticket SubjectUpdate the subject of a ticket.
Action
Update userUpdate a user.
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 Quipu
Quipu to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Quipu to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Quipu to StripeStripe is a payment processing platform for online businesses.
Quipu to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Quipu to TrelloTrello is a visual collaboration tool that organizes projects into boards, lists, and cards.
Quipu to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
More into Request Tracker (RT)
HubSpot to Request Tracker (RT)HubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to Request Tracker (RT)Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to Request Tracker (RT)Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Request Tracker (RT)Google Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to Request Tracker (RT)Google Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to Request Tracker (RT)Mailchimp marketing automation and email platform.
Questions
Quipu and Request Tracker (RT), answered
What can start an automation from Quipu?
Any of Quipu's 2 triggers in the catalog, including New Contact and New Invoice. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Request Tracker (RT) when something happens in Quipu?
Any of Request Tracker (RT)'s 19 actions, including Create Ticket, Update ticket, Update Ticket Due Date and Update Ticket Status. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Request Tracker (RT) to Quipu?
Yes. When something happens in Request Tracker (RT), your agent can act in Quipu too. This page covers both directions: Request Tracker (RT)'s triggers and Quipu's actions are listed here as well.
Do I have to build a connector for Quipu or Request Tracker (RT)?
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 Quipu and Request Tracker (RT) 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.