Integration
Connect Aplos and Request Tracker (RT)
When New contact fires in Aplos, your agent runs Create Ticket in Request Tracker (RT), or Ticket Created in Request Tracker (RT) to Find contacts in Aplos. 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 Aplos and Request Tracker (RT) 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 Aplos and Request Tracker (RT) can do together
From Aplos to Request Tracker (RT)
When New contact in Aplos
then Create Ticket in Request Tracker (RT)
When New contribution in Aplos
then Update ticket in Request Tracker (RT)
From Request Tracker (RT) to Aplos
When Ticket Created in Request Tracker (RT)
then Find contacts in Aplos
When Ticket Status Changed in Request Tracker (RT)
then Get contact in Aplos
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 Aplos and Request Tracker (RT)
Triggers and actions 6 triggers · 32 actions
Trigger
New contactTriggers when a new contact (a donor, individual or company) is added in Aplos.
Trigger
New contributionTriggers when a new contribution (a donation batch) is recorded in Aplos. Use Get contribution with its ID to read the donors, purposes and amounts.
Trigger
New or updated contactTriggers when a contact (a donor, individual or company) is added or changed in Aplos.
Action
Add contributionRecords a contribution (donation record) in Aplos, with one or more lines each crediting a contact and a purpose.
Action
Add payableCreates an accounts payable bill in Aplos, split across one or more expense lines by account and fund.
Action
Add transactionCreates an accounting transaction (journal entry) in Aplos. The transaction lines must balance by amount and fund.
Action
Find contactsReturns the contacts that match the specified name, email, type or last-updated time.
Action
Find contributionsReturns contributions (donation records) that match the specified contact, name and date criteria.
Action
Find transactionsReturns accounting transactions that match the criteria you supply (contact, fund, account, amount, date range, memo, note, tags, reconciled status).
Action
Get contactRetrieve a single Aplos contact (individual or company) by its ID, including emails, phones and addresses.
Action
Get contributionRetrieve a single Aplos contribution record by its ID.
Action
Get payableRetrieves a single payable (bill) by its id.
Action
Get transactionRetrieves a single accounting transaction, including its lines (account, fund, amount) and contact.
Action
List accountsLists the accounts in the organization's chart of accounts, optionally filtered by enabled status, name or account type.
Action
List fundsLists the funds in the Aplos organization, optionally narrowed by name or fund balance account number.
Action
List purposesLists the donation purposes in the Aplos organization, optionally filtered by name or enabled status.
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 Aplos
Aplos to StripeStripe is a payment processing platform for online businesses.
Aplos to OpenAIOpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...
Aplos to OntraportOntraport is an all-in-one CRM, marketing automation, and e-commerce platform.
Aplos to Freshworks CRMFreshworks CRM (Freshsales Suite) — manage contacts, sales accounts, deals, notes, tasks, and appointments.
Aplos to BeanstalkBeanstalk is a code hosting and deployment workflow tool for Git and Subversion.
Aplos to BitlyBitly is a link-management platform for shortening, branding, and tracking URLs.
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
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
Aplos and Request Tracker (RT), answered
What can start an automation from Aplos?
Any of Aplos's 3 triggers in the catalog, including New contact, New contribution and New or updated contact. 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 Aplos?
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 Aplos?
Yes. When something happens in Request Tracker (RT), your agent can act in Aplos too. This page covers both directions: Request Tracker (RT)'s triggers and Aplos's actions are listed here as well.
Do I have to build a connector for Aplos 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.
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.