Integration
Connect Aplos and BugBug
When New contact fires in Aplos, your agent runs Run Suite in BugBug, or Any Cloud Suite Run Failed in BugBug 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 BugBug 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 Aplos and BugBug can do together
From Aplos to BugBug
When New contact in Aplos
then Run Suite in BugBug
When New contribution in Aplos
then Run Test in BugBug
From BugBug to Aplos
When Any Cloud Suite Run Failed in BugBug
then Find contacts in Aplos
When Any Cloud Suite Run Passed in BugBug
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 BugBug
Triggers and actions 9 triggers · 21 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
Any Cloud Suite Run FailedTriggers when a suite run in the BugBug cloud fails. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Cloud Suite Run PassedTriggers when a suite run in the BugBug cloud passes. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Cloud Suite Run StartedTriggers when a suite starts running in the BugBug cloud. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Test Failed in the CloudTriggers when a test run in the BugBug cloud fails. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Test Passed in the CloudTriggers when a test run in the BugBug cloud passes. Returns the run's name, status, timing and a link to it in BugBug.
Trigger
Any Test Started in the CloudTriggers when a test starts running in the BugBug cloud. Returns the run's name, status, timing and a link to it in BugBug.
Action
Get Suite RunReturns one BugBug suite run with its status, timing and error code.
Action
Get Test RunReturns one BugBug test run with its status, timing and error code.
Action
List SuitesReturns the suites in the BugBug project, optionally filtered by name.
Action
List TestsReturns the tests in the BugBug project, optionally filtered by name.
Action
Run SuiteStarts a cloud run of a BugBug suite and returns the new run's ID, status and link.
Action
Run TestStarts a cloud run of a BugBug test and returns the new run's ID, status and link.
Action
Stop Suite RunStops a running BugBug suite run and returns its status.
Action
Stop Test RunStops a running BugBug test run and returns its status.
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 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.
More into BugBug
ActiveCampaign to BugBugActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to BugBugOrganize anything with Airtable, a modern database created for everyone.
Asana to BugBugAsana is a collaborative information manager for workspace.
Brevo to BugBugBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
100Hires ATS to BugBug100Hires ATS is a recruitment software that includes talent sourcing, and applicant tracking to accelerate...
2Chat to BugBug2Chat is a conversational commerce automation tool for WhatsApp, Instagram, Messenger, and SMS.
Questions
Aplos and BugBug, 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 BugBug when something happens in Aplos?
Any of BugBug's 8 actions, including Get Suite Run, Get Test Run, List Suites and List Tests. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from BugBug to Aplos?
Yes. When something happens in BugBug, your agent can act in Aplos too. This page covers both directions: BugBug's triggers and Aplos's actions are listed here as well.
Do I have to build a connector for Aplos or BugBug?
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 BugBug 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.