Integration
Connect My Music Staff and Salla
When something happens in My Music Staff or Salla, your agent does the next thing in the other. Describe it 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 My Music Staff and Salla 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 My Music Staff and Salla can do together
From My Music Staff to Salla
When New Email in My Music Staff
then Add customer in Salla
When New Invoice in My Music Staff
then Add order in Salla
From Salla to My Music Staff
When Product Created in Salla
then Add Payment in My Music Staff
When Product Updated in Salla
then Add Student in My Music Staff
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 My Music Staff and Salla
Triggers and actions 12 triggers · 25 actions
Trigger
Attendance TakenTriggers when attendance is taken or edited for a calendar event.
Trigger
New EmailTriggers when a new email message is created.
Trigger
New InvoiceTriggers when a new invoice is created (manually or by auto-invoicing).
Trigger
New SMSTriggers when a new SMS message is created.
Trigger
New StudentTriggers when a new student is added to your My Music Staff account.
Trigger
Payment AddedTriggers when a payment is recorded in a Family Account.
Trigger
Student Added to EventTriggers when a student is added to an event on the calendar.
Trigger
Student UpdatedTriggers when a student's profile information is updated.
Action
Add PaymentRecords a payment in the Family Account
Action
Add StudentAdds a new student to your My Music Staff account.
Action
Find All ParentsFinds all parents based on Family ID or on search text.
Action
Find Attendance RecordsSearches attendance records by date range, student, teacher, event, or status. Returns matching records with a total count.
Action
Find StudentFinds students based on Student ID or on search text.
Trigger
Customer RegisteredFires instantly when a new customer registers in (or is added to) the Salla store.
Trigger
Order PlacedTriggers when a new order is placed.
Trigger
Product CreatedFires when a new product is created in the Salla store (product.created webhook).
Trigger
Product UpdatedFires when a product in the Salla store is updated.
Action
Add customerCreates a new customer in the Salla store.
Action
Add orderCreates an order in the Salla store (one-time or subscription).
Action
Add order historyAppends a note to an order's history in Salla.
Action
Add product tagCreates a product tag in the Salla store.
Action
Create ProductCreates a product in the Salla store.
Action
Delete customerDeletes a customer from the Salla store's customer list.
Action
Delete ProductDeletes a product from the Salla store by its id.
Action
Find a CategorySearch the store's categories by name keyword and/or category IDs.
Action
Find a CustomerFinds customers in the store whose mobile number, email or name matches a keyword.
Action
Find a ProductReturns the products whose name or SKU matches the keyword, optionally narrowed by status and category.
Action
Get customerReturns a single Salla customer's details by id.
Action
Get orderReturns the full details of a single Salla order by its order id.
Action
Get productGet product details by id.
Action
List customersLists the customers in the Salla store, optionally narrowed by a keyword or a creation-date range.
Action
List productsLists the products in the Salla store, optionally narrowed by keyword, status or category. Returns the first page of results.
Action
Update customerUpdates an existing customer in a Salla store. Only the fields you fill in are changed; blank fields keep their current values.
Action
Update Order StatusChanges the status of a Salla order, either to one of Salla's built-in statuses or to a custom order sub-status.
Action
Update ProductUpdates an existing product in the Salla store. Only the fields you fill in are changed.
Action
Update Product QuantitySets, adds to or subtracts from the stock quantity of one product or variant, identified by product id, variant id or SKU.
Action
Upload Product ImageAttaches one image to a Salla product, either from a public image link or by uploading an image file. A product can hold up to 10 images.
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 My Music Staff
My Music Staff to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
My Music Staff to ElevenLabsElevenLabs is an AI audio research and deployment company.
My Music Staff to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
My Music Staff to MailchimpMailchimp marketing automation and email platform.
My Music Staff to StripeStripe is a payment processing platform for online businesses.
My Music Staff to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Salla
HubSpot to SallaHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SallaSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SallaGoogle Sheets
Gmail to SallaGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SallaGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SallaGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
My Music Staff and Salla, answered
What can start an automation from My Music Staff?
Any of My Music Staff's 8 triggers in the catalog, including New Email, New Invoice, New SMS and New Student. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Salla when something happens in My Music Staff?
Any of Salla's 20 actions, including Create Product, Update customer, Update Order Status and Update Product. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Salla to My Music Staff?
Yes. When something happens in Salla, your agent can act in My Music Staff too. This page covers both directions: Salla's triggers and My Music Staff's actions are listed here as well.
Do I have to build a connector for My Music Staff or Salla?
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.