Integration
Connect My Music Staff to Basin
When something happens in My Music Staff, your agent does the next thing in Basin. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want My Music Staff and Basin to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with My Music Staff and Basin
Triggers and actions 9 triggers ยท 16 actions
Trigger
Attendance TakenTriggers when attendance is taken or edited for a calendar event.
- New Email
Triggers when a new email message is created.
- New Invoice
Triggers when a new invoice is created (manually or by auto-invoicing).
- New SMS
Triggers when a new SMS message is created.
- New Student
Triggers when a new student is added to your My Music Staff account.
- Payment Added
Triggers when a payment is recorded in a Family Account.
- Student Added to Event
Triggers when a student is added to an event on the calendar.
- Student Updated
Triggers when a student's profile information is updated.
- Add Payment
Records a payment in the Family Account
- Add Student
Adds a new student to your My Music Staff account.
- Find All Parents
Finds all parents based on Family ID or on search text.
- Find Attendance Records
Searches attendance records by date range, student, teacher, event, or status. Returns matching records with a total count.
- Find Student
Finds students based on Student ID or on search text.
Trigger
New SubmissionTriggers when your form receives a submission.
- Add form
Create a new form under a project. POST /api/v1/forms.
- Add project
Create a new project (form-organizing container). POST /api/v1/projects.
- Delete form
Destroy a form. DELETE /api/v1/forms/:id.
- Delete submission
Destroy a submission. DELETE /api/v1/submissions/:id.
- Get form
Retrieve a single form by id. GET /api/v1/forms/:id.
- Get submission
Retrieve a single submission by id. GET /api/v1/submissions/:id.
- List forms
List all forms accessible to the account. GET /api/v1/forms.
- List projects
List all projects accessible to the account. GET /api/v1/projects.
- List submissions
List submissions for a form. GET /api/v1/submissions.
- Update form
Update a form's configuration (notifications, spam protection, branding, etc). PATCH/PUT /api/v1/forms/:id.
- Update submission
Update a submission's state fields (spam, read, trash). PATCH/PUT /api/v1/submissions/: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