Check classes, attendance, customers, memberships and invoices in TeamUp and register customers.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 20 tools
Tools target distinct resources and actions, but the set contains adjacent pairs like list_memberships vs list_customer_memberships and list_events vs list_attendances that could be confused if descriptions are skimmed. Descriptions clearly distinguish them, so ambiguity is low overall.
All 20 tools use the goteamup_ prefix followed by a consistent snake_case verb_noun pattern (get_, list_, create_, confirm_, log_, register_, unregister_). No mixed conventions or vague verbs.
20 tools is slightly above the ideal 3-15 range but reasonable given the breadth of the TeamUp domain (customers, memberships, events, invoices, CRM, venues, etc.). Each tool maps to a distinct endpoint or action, so the count is justified.
The surface covers many read operations and a few key actions (create customer, register/unregister, confirm attendance, log CRM), but lacks update/delete for customers and most create/update/delete for events, memberships, invoices, venues, etc. This is a notable gap for a business management API.
Read members, subscriptions, bookings, invoices, payments; create and update members in Members.dev.
Read Mindbody classes, schedules, clients, staff and sales; book clients and appointments.
List classes, workshops and clients; grant passes or credits to clients in Zenamu.
Add one secure layer between your agents and this server.