Supersaas MCP integration

Not through this toolkit. The actions cover users, schedules, forms, groups, and promotions - Create User, Update User, List Schedules and the rest - with nothing that creates, reschedules, or cancels a booking. Ayro can get the account ready and point the customer at the right schedule, then hand off for the booking itself.

Yes. Create User accepts a foreign_key and SuperSaaS stores that instead of generating an ID of its own, so a user Ayro creates carries the same identifier as the record in your system. Setting duplicate to 'raise' stops a second account being created against a key that already exists.

List Field List returns the fields configured on a Schedule or User object, so Ayro checks what a profile stores before reading or writing one. That matters because custom fields are set per account rather than fixed by SuperSaaS, and they differ between a schedule and a user.

No. Delete User permanently removes the user from the account and nothing in the toolkit restores one, so it is the action worth keeping behind an explicit confirmation in the conversation. Anything the customer is unclear about is better handed to a human agent with the full history attached.