Integration
Connect Aplos and Azure DevOps
When New contact fires in Aplos, your agent runs Add Link to Work Item in Azure DevOps, or Completed Build in Azure DevOps 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 Azure DevOps 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)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 Azure DevOps can do together
From Aplos to Azure DevOps
When New contact in Aplos
then Add Link to Work Item in Azure DevOps
When New contribution in Aplos
then Create Work Item in Azure DevOps
From Azure DevOps to Aplos
When Completed Build in Azure DevOps
then Find contacts in Aplos
When New Work Item in Azure DevOps
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 Azure DevOps
Triggers and actions 8 triggers · 18 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
Code Push (Git)Triggers when commits are pushed to a Git repository in an Azure DevOps project.
Trigger
Completed BuildTriggers when a build finishes in an Azure DevOps project, with its result (succeeded, failed, partially succeeded or canceled).
Trigger
New Work ItemTriggers when a work item is created in an Azure DevOps project.
Trigger
New Work Item CommentTriggers when someone comments on a work item in an Azure DevOps project.
Trigger
Updated Work ItemTriggers when a work item is updated in an Azure DevOps project, with the work item's current values and the list of fields that changed.
Action
Add Link to Work ItemAdds a link to an Azure DevOps work item: a related, parent, child, predecessor, successor or duplicate link to another work item, or a hyperlink to a web page.
Action
Create Work ItemCreates a new work item (such as a Task, Bug, Issue or User Story) in an Azure DevOps project.
Action
Find Work ItemFinds work items in an Azure DevOps project that match a Work Item Query Language (WIQL) query, returning the matching work item IDs, or the matching links for a link query.
Action
Trigger BuildQueues a new run of an Azure DevOps build pipeline, optionally for a specific branch or commit and with pipeline variables or parameters.
Action
Update Work ItemUpdates an existing Azure DevOps work item: changes its title, description, state, assignee, area, iteration, priority or tags, and can add a discussion comment. Fields left blank are not changed.
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 SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Aplos to StripeStripe is a payment processing platform for online businesses.
Aplos to JotFormJotForm is a web-based WYSIWYG form builder. Create forms, integrate them into your site, and collect...
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.
More into Azure DevOps
ActiveCampaign to Azure DevOpsActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to Azure DevOpsOrganize anything with Airtable, a modern database created for everyone.
Asana to Azure DevOpsAsana is a collaborative information manager for workspace.
2Chat to Azure DevOps2Chat is a conversational commerce automation tool for WhatsApp, Instagram, Messenger, and SMS.
3Scribe to Azure DevOps3Scribe is the most accurate, automated text transcription available.
5pm to Azure DevOps5pm is an online project management tool for teams.
Questions
Aplos and Azure DevOps, 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 Azure DevOps when something happens in Aplos?
Any of Azure DevOps's 5 actions, including Create Work Item, Update Work Item, Add Link to Work Item and Find Work Item. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Azure DevOps to Aplos?
Yes. When something happens in Azure DevOps, your agent can act in Aplos too. This page covers both directions: Azure DevOps's triggers and Aplos's actions are listed here as well.
Do I have to build a connector for Aplos or Azure DevOps?
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 Aplos and Azure DevOps 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.