Integration
Connect Akada and CallMaker
When Account Created fires in Akada, your agent runs Create Customer Card in CallMaker, or Booking Created in CallMaker to Send Customer Message in Akada. 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 Akada 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 Akada and CallMaker can do together
From Akada to CallMaker
When Account Created in Akada
then Create Customer Card in CallMaker
When Student Created in Akada
then Confirm Order by Order Id in CallMaker
From CallMaker to Akada
When Booking Created in CallMaker
then Send Customer Message in Akada
When Number Change Created in CallMaker
then Find records globally in Akada
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 Akada and CallMaker
Triggers and actions 17 triggers · 34 actions
Trigger
Account CreatedTriggers when a new customer account is added to the studio.
Trigger
Student CreatedTriggers when a new student is added to the studio.
Action
Cancel Calendar EventCancels a single scheduled calendar event instance in Akada. If the event is already cancelled, nothing changes.
Action
Find records globallySearches the studio's classes, customers, staff, students and users for matching text and returns the matches in each category.
Action
Get Calendar EventReturns a single scheduled calendar event (class, private lesson, rental or rehearsal) by its ID, along with the related class, room, session and staff details.
Action
Get ClassReturns one class by ID.
Action
Get CustomerReturns one customer account by ID.
Action
Get SessionReturns a single studio session, including its registration dates and class start and end dates.
Action
Get Staff MemberReturns one staff member by ID.
Action
Get StudentReturns one student by ID.
Action
Get Studio InfoReturns the studio's profile information, such as its name, address and contact details.
Action
List Calendar EventsReturns the studio's scheduled calendar events (classes, private lessons, rentals, rehearsals) within a date range, with optional filters.
Action
List Class AttendanceReturns the attendance entries for one class on a given date, with the students and staff in that class.
Action
List ClassesReturns a page of the studio's classes, optionally filtered by session, class type or class level.
Action
List Class LevelsReturns the studio's class levels.
Action
List Class RoomsReturns the studio's class rooms.
Action
List Class StudentsReturns the students enrolled in one class.
Action
List Class TypesReturns the studio's class types.
Action
List Customer MessagesReturns the message conversation between the studio and a specific customer, most recent first.
Action
List CustomersReturns a page of the studio's customer accounts.
Action
List Customer StudentsReturns the students that belong to one customer account.
Action
List SessionsReturns the studio's sessions (terms).
Action
List StaffReturns a page of the studio's staff members.
Action
List StudentsReturns a page of the studio's students.
Action
List UsersReturns the list of users for the studio, with their display names, usernames, emails and roles.
Action
Send Customer MessageSends a message to a customer account; it appears in the customer's message thread.
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 Akada
Akada to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Akada to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Akada to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Akada to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Akada to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Akada 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
Akada and CallMaker, answered
What can start an automation from Akada?
Any of Akada's 2 triggers in the catalog, including Account Created and Student Created. Describe the moment in plain language and your agent picks the right one.
What can your agent do in CallMaker when something happens in Akada?
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 Akada?
Yes. When something happens in CallMaker, your agent can act in Akada too. This page covers both directions: CallMaker's triggers and Akada's actions are listed here as well.
Do I have to build a connector for Akada 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 Akada 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.