Connect your studio
- Open Agent Tools → Marketplace → Magicline Open API.
- Enter the Studio ID and the API key issued for that studio.
- Enter your Magicline Open API URL, for example
https://your-studio.open-api.magicline.com/v1. Use the URL and key from the same Magicline activation. - Save the connection and select Assign to attach it to an assistant. Give each connection a recognizable studio name.
- Open Installed → Edit → Tools to enable or disable individual functions.
What your assistant can look up
These six reads are selected initially. The extended catalog contains 169 documented operations. Additional reads depend on your Magicline access. Booking and other writes remain unavailable in this connection, including when selected in the catalog.
Ask for the location before retrieving studio-specific facts. Use the time tool before interpreting “tomorrow” or “next week”. Course and session IDs come from earlier results for the same studio; visitors should not have to know them. Pages can include a continuation cursor: follow it before claiming a complete list. A bookable session may still be full or have a waitlist.
One assistant, several studios
Connect and assign each studio separately. Famulor automatically gives new connections distinct tool names for each studio. Existing connections keep their naming format; there is no naming switch to configure. Describe the supported locations and require confirmation when a city name is ambiguous. On a location change, retrieve fresh results and discard the previous studio’s course IDs, session IDs and availability. Use direct tools for studio lookups; an automation is optional.Use Magicline in automations
Under Automations → Connections, connect Magicline or choose Import from Agent Tools. Importing preserves the credentials and selected operations. Add a Magicline action and map its fields from the trigger or earlier steps. Its response is available to later actions, including other connected apps. Start the flow manually, on a schedule, from a conversation event or with an inbound webhook. The connection does not subscribe to Magicline events. Use an automation when several steps must run together; a CRM is not required to connect Magicline.Booking availability
This connection currently reads information and does not create bookings. Booking requires provider write permission and support for the specific booking operation. Availability alone is not a reservation. Only confirm a booking after a successful booking response; check an unclear result before retrying. Any later CRM step should preserve the actual booking status and the visitor’s consent.API, MCP, CLI & SDK
POST /api/v1/tools/magicline · MCP connect_magicline · CLI famulor connect-magicline.
POST /api/v1/automations/connections/import · MCP import_automation_connection · CLI famulor import-automation-connection.