Integration
Connect BugBug and CallMaker
When Any Cloud Suite Run Failed fires in BugBug, your agent runs Create Customer Card in CallMaker, or Booking Created in CallMaker to Run Suite in BugBug. 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 BugBug and CallMaker 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 BugBug and CallMaker can do together
From BugBug to CallMaker
When Any Cloud Suite Run Failed in BugBug
then Create Customer Card in CallMaker
When Any Cloud Suite Run Passed in BugBug
then Confirm Order by Order Id in CallMaker
From CallMaker to BugBug
When Booking Created in CallMaker
then Run Suite in BugBug
When Number Change Created in CallMaker
then Run Test in BugBug
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 BugBug and CallMaker
Triggers and actions 21 triggers · 23 actions
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 suiteReturns a single test suite with its settings, tags and tests.
Action
Get Suite RunReturns one BugBug suite run with its status, timing and error code.
Action
Get testReturns a single BugBug test by its ID, including its name, folder, tags, notes and screen size.
Action
Get Test RunReturns one BugBug test run with its status, timing and error code.
Action
List profilesReturns the run profiles defined in your BugBug project.
Action
List suite runsReturns the suite runs in your BugBug project, optionally filtered by suite, status, tags or start date.
Action
List SuitesReturns the suites in the BugBug project, optionally filtered by name.
Action
List test runsReturns the historical test runs in your BugBug project, optionally filtered by test, status, tags or start time.
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.
Trigger
Booking CancelledFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled bookings.
Trigger
Booking ConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed bookings.
Trigger
Booking CreatedTriggers when a new booking is created.
Trigger
Booking RestoredFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored bookings.
Trigger
Booking UnConfirmedFires on the latest bookings. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed bookings.
Trigger
Meeting AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (true) to act only on accomplished meetings.
Trigger
Meeting Not AccomplishedFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_accomplished (false) to act only on meetings that did not take place.
Trigger
Meeting Not SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (false) to act only on unsuccessful meetings.
Trigger
Meeting SuccessfulFires on the latest bookings (meetings). Callmaker's polling API cannot filter by state, so check meeting_successful (true) to act only on successful meetings.
Trigger
Number Change CreatedTriggers when a new number change (a processed customer card) is recorded; returns its ID.
Trigger
Order CancelledFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field to act only on cancelled orders.
Trigger
Order ConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field to act only on confirmed orders.
Trigger
Order CreatedTriggers when a new order is created.
Trigger
Order RestoredFires on the latest orders. Callmaker's polling API cannot filter by state, so check the cancelled field (false) to act only on restored orders.
Trigger
Order UnConfirmedFires on the latest orders. Callmaker's polling API cannot filter by state, so check the confirmed field (false) to act only on unconfirmed orders.
Action
Confirm Order by Order IdConfirms an order and returns the updated order.
Action
Create Customer CardCreates a customer card in a Callmaker project and list, with the field values you supply.
Action
Edit Customer CardUpdates field values on an existing Callmaker customer card.
Action
Edit Order Status by Order IdChanges the status of an order.
Action
Find Booking by Booking IdReturns one Callmaker booking (meeting) by its booking ID, including its customer card, user, times and confirmation state.
Action
Find Descendants Workflows by Workflow IdReturns the IDs of all workflows beneath a workflow.
Action
Find Number by Number IdReturns a number (customer record) by its ID.
Action
Find Order by Order IdReturns an order by its ID.
Action
Find Resource by Resource IdReturns a resource by its ID.
Action
Find User by User IdReturns a user by their ID.
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 BugBug
BugBug to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BugBug to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BugBug to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BugBug to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
BugBug to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BugBug to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into CallMaker
ActiveCampaign to CallMakerActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to CallMakerOrganize anything with Airtable, a modern database created for everyone.
Asana to CallMakerAsana is a collaborative information manager for workspace.
Brevo to CallMakerBrevo is the leading CRM suite designed to cultivate long-term customer relationships and help businesses...
Calendly to CallMakerCalendly is a scheduling automation platform for eliminating the back-and-forth emails to find the perfect...
100Hires ATS to CallMaker100Hires ATS is a recruitment software that includes talent sourcing, and applicant tracking to accelerate...
Questions
BugBug and CallMaker, answered
What can start an automation from BugBug?
Any of BugBug's 6 triggers in the catalog, including Any Cloud Suite Run Failed, Any Cloud Suite Run Passed, Any Cloud Suite Run Started and Any Test Failed in the Cloud. Describe the moment in plain language and your agent picks the right one.
What can your agent do in CallMaker when something happens in BugBug?
Any of CallMaker's 10 actions, including Create Customer Card, Confirm Order by Order Id, Edit Customer Card and Edit Order Status by Order Id. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from CallMaker to BugBug?
Yes. When something happens in CallMaker, your agent can act in BugBug too. This page covers both directions: CallMaker's triggers and BugBug's actions are listed here as well.
Do I have to build a connector for BugBug or CallMaker?
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 BugBug and CallMaker 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.