> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to SuperSaaS

The SuperSaaS connector lets your AI agent act in each user's SuperSaaS account. Each user connects their own SuperSaaS API key once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 30 tools.

**Authentication:** Account Name and API Key
**Categories:** Calendar, Productivity
**Tools:** 30: 19 read, 7 write, 4 destructive
**Users sign in with:** Username and password
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=SUPERSAAS)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the SuperSaaS connection

   In **AgentKit > Connections**, create a SuperSaaS connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'supersaas_agenda_list',
  toolInput: {
    schedule_id: 524012,
    user: '<user>',
  },
  connector: 'supersaas',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="supersaas_agenda_list",
    tool_input={
        "schedule_id": 524012,
        "user": "<user>",
    },
    connection_name="supersaas",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `supersaas_agenda_list`

List User Agenda · Read-only

List one user's appointments in a schedule.
Returns bookings with id, start, finish, resource or service and form fields.
Use this to show a customer their bookings. Use supersaas_range_list for all users.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `user` (`string`, required): The user's name or ID. Use 0 for the administrator. Example: jane@example.com.
- `from` (`string`, optional): Only appointments after this local time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Example: 2026-12-01.
- `slot` (`boolean`, optional): Capacity schedules only: set true to group bookings under their slots, with slot details. Example: false.

Example input: `{"schedule_id":524012,"user":"<user>"}`

### `supersaas_availability_list`

List Free Availability · Read-only

List the free spaces in a resource or capacity schedule after a given time. Not available for service schedules.
Returns slots with start, finish, title, description, location and free count.
Use this to find bookable times before supersaas_booking_create.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `from` (`string`, required): Only free spaces after this local time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 09:00:00.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `full` (`boolean`, optional): Capacity schedules: set true to include full slots. Example: false.
- `length` (`integer`, optional): Resource schedules: only free spaces of at least this many minutes. Example: 60.
- `maxresults` (`integer`, optional): Maximum number of results. Defaults to 10. Example: 10.
- `resource` (`string`, optional): Resource schedules: only free spaces of this resource name. Example: Room 1.

Example input: `{"from":"<from>","schedule_id":524012}`

### `supersaas_booking_get`

Get Appointment · Read-only

Get one SuperSaaS appointment.
Returns the appointment's id, start, finish, resource, contact fields, status, price, created_by and timestamps.
Use supersaas_bookings_list or supersaas_range_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): Appointment (booking) ID. Example: 1234567.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `form` (`boolean`, optional): Set true to include the data of an attached custom form. Example: true.

Example input: `{"id":1234567,"schedule_id":524012}`

### `supersaas_bookings_list`

List Appointments · Read-only

List the appointments of a schedule, optionally within a time window.
Returns appointments with id, start, finish, resource, contact fields, status, price, created_on and updated_on.
Use start and limit=1 to get the next appointment. Use supersaas_range_list for richer date filtering.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `finish` (`string`, optional): Resource and service schedules: only appointments until this time. Example: 2026-12-31.
- `form` (`boolean`, optional): Set true to include the data of an attached custom form. Example: true.
- `limit` (`integer`, optional): Maximum number of results to return. Example: 100.
- `start` (`string`, optional): Resource and service schedules: only appointments from this time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Example: 2026-12-01.

Example input: `{"schedule_id":524012}`

### `supersaas_changes_list`

List Recent Changes · Read-only

List the appointments in a schedule that were created, changed or deleted since a given time.
Returns bookings (or slots with bookings) with id, start, finish, resource or service, deleted flag, created_on, updated_on and form fields.
Use this to sync changes. Use supersaas_range_list for appointments in a date range.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `from` (`string`, optional): Only changes after this UTC time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. The ten most recent changes are returned when empty. Example: 2026-11-01 00:00:00.
- `limit` (`integer`, optional): Maximum number of results to return. Example: 100.
- `offset` (`integer`, optional): Number of results to skip, to page through large result sets. Example: 0.
- `slot` (`boolean`, optional): Capacity schedules only: set true to group bookings under their slots, with slot details. Example: false.
- `to` (`string`, optional): Only changes before this UTC time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Example: 2026-11-30 23:59:59.
- `user` (`string`, optional): Only bookings of this user (name, ID or foreign key). Use 0 for the administrator. Example: 1234fk.

Example input: `{"schedule_id":524012}`

### `supersaas_fields_list`

List Available Fields · Read-only

List the fields available on a schedule's appointments, or on the user object when schedule_id is empty.
Returns the field list with names and labels.
Use this to see which fields a booking or user accepts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, optional): Schedule ID. Leave empty to list the fields of the user object. Example: 524012.

Example input: `{}`

### `supersaas_form_definitions_list`

List Form Definitions · Read-only

List the custom form definitions in your SuperSaaS account.
Returns each form definition's ID and name.
Use this to get a form_id for supersaas_forms_list.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `supersaas_form_get`

Get Completed Form · Read-only

Get one completed custom form by its ID.
Returns the form's id, reservation_process_id, content, created_on, updated_on, super_form_id, deleted and user_id.
Use supersaas_forms_list to find form IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): ID of the completed form. Example: 12345.

Example input: `{"id":12345}`

### `supersaas_forms_list`

List Completed Forms · Read-only

List the completed custom forms of one form definition, optionally only those updated after a time or filled in by one user.
Returns forms with id, reservation_process_id, content (answers by field number), created_on, updated_on and user_id.
Use supersaas_form_definitions_list for form_id. Use supersaas_form_get for one form.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `form_id` (`integer`, required): ID of the form definition, from supersaas_form_definitions_list. Example: 34567.
- `from` (`string`, optional): Only forms updated after this UTC time, as YYYY-MM-DD HH:MM:SS. Example: 2026-11-01 00:00:00.
- `limit` (`integer`, optional): Maximum number of forms. Defaults to 100. Example: 100.
- `offset` (`integer`, optional): Number of results to skip, to page through large result sets. Example: 0.
- `user` (`string`, optional): Only forms of this user (name, ID or foreign key). Use 0 for the administrator. Example: 1234fk.

Example input: `{"form_id":34567}`

### `supersaas_groups_list`

List User Groups · Read-only

List the user groups defined in your SuperSaaS account.
Returns each group's ID and name.
Use this for the group value when creating or updating users.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `supersaas_promotion_get`

Get Promotion Code · Read-only

Get one SuperSaaS coupon code and how often it was used.
Returns code, description and usage.
Use supersaas_promotions_list to browse codes.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The coupon code. Example: SPRING25.

Example input: `{"id":"<id>"}`

### `supersaas_promotions_list`

List Promotion Codes · Read-only

List the promotional coupon codes in your SuperSaaS account.
Returns codes with code, description and usage count.
Use supersaas_promotion_get for one code.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `limit` (`integer`, optional): Maximum number of results to return. Example: 100.
- `offset` (`integer`, optional): Number of results to skip, to page through large result sets. Example: 0.

Example input: `{}`

### `supersaas_range_list`

List Appointments in Range · Read-only

List the appointments (or, for capacity schedules, the slots) in a schedule within a time range.
Returns bookings or slots with id, start, finish, resource or service, created_on, updated_on and form fields.
Use this for a calendar view. Use supersaas_agenda_list for one user's appointments.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `from` (`string`, optional): Only appointments starting at or after this local time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Defaults to now. Example: 2026-12-01.
- `limit` (`integer`, optional): Maximum number of results to return. Example: 100.
- `offset` (`integer`, optional): Number of results to skip, to page through large result sets. Example: 0.
- `resource_id` (`string`, optional): Only appointments for this resource ID. Example: 31415.
- `service_id` (`string`, optional): Only appointments for this service ID. Example: 27182.
- `slot` (`boolean`, optional): Capacity schedules only: set true to group bookings under their slots, with slot details. Example: false.
- `to` (`string`, optional): Only appointments starting before this local time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Example: 2026-12-31.
- `today` (`boolean`, optional): Set true to return only today's appointments. Example: false.
- `user` (`string`, optional): Resource and service schedules: only bookings of this user (name, ID or foreign key). Use 0 for the administrator. Example: 1234fk.

Example input: `{"schedule_id":524012}`

### `supersaas_resources_list`

List Resources or Services · Read-only

List the resources or services of a resource or service schedule. Not available for capacity schedules.
Returns each resource's or service's ID and name.
Use this for resource_id values when booking.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.

Example input: `{"schedule_id":524012}`

### `supersaas_schedules_list`

List Schedules · Read-only

List the schedules in your SuperSaaS account.
Returns each schedule's ID and name.
Use this first to get a schedule_id for the appointment and slot tools.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `supersaas_slot_get`

Get Slot · Read-only

Get one slot of a capacity schedule.
Returns the slot's id, start, finish, title, description, location, capacity, level, waiting, color and price.
Use supersaas_slots_list to find slot IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): Slot ID. Example: 98765.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.

Example input: `{"id":98765,"schedule_id":524012}`

### `supersaas_slots_list`

List Slots · Read-only

List the slots of a capacity schedule in start-time order, optionally within a time window.
Returns slots with id, start, finish, title, description, location, capacity, level (places taken), waiting, color and price.
Use this to find slot IDs. Use supersaas_range_list with slot=true to include each slot's bookings.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `finish` (`string`, optional): Only slots starting until this local time. Example: 2026-12-31.
- `limit` (`integer`, optional): Maximum number of slots, up to 2500. Defaults to 100. Example: 100.
- `offset` (`integer`, optional): Number of results to skip, to page through large result sets. Example: 0.
- `start` (`string`, optional): Only slots starting from this local time, as YYYY-MM-DD or YYYY-MM-DD HH:MM:SS. Example: 2026-12-01.

Example input: `{"schedule_id":524012}`

### `supersaas_user_get`

Get User · Read-only

Get one SuperSaaS user by SuperSaaS ID or by your own foreign key.
Returns the user's id, fk, name, email, contact details, role, credit, custom fields, created_on and last_login.
Use supersaas_users_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): User ID: the SuperSaaS numeric ID, or your own key followed by fk, such as 567fk. Example: 567fk.
- `form` (`boolean`, optional): Set true to include the data of an attached custom form. Example: true.

Example input: `{"id":"<id>"}`

### `supersaas_users_list`

List Users · Read-only

List the users in your SuperSaaS account.
Returns users with id, name, email, full_name, phone, role, credit, custom fields, created_on and last_login.
Use this to browse users. Use supersaas_user_get for one user.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `form` (`boolean`, optional): Set true to include the data of an attached custom form. Example: true.
- `limit` (`integer`, optional): Maximum number of users to return. Defaults to 100. Example: 100.
- `offset` (`integer`, optional): Number of results to skip, to page through large result sets. Example: 0.

Example input: `{}`

### `supersaas_booking_create`

Create Appointment · Write

Create an appointment in a resource schedule (with start and finish) or a capacity schedule (with slot_id). Service schedules are not supported.
Returns HTTP 201 with an empty body; the new ID is in the Location header, so use supersaas_range_list to find it afterwards.
Use supersaas_availability_list first to find a free time or slot.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `address` (`string`, optional): Postal address. Example: 1 Main Street, Springfield.
- `country` (`string`, optional): Two-letter ISO 3166-1 country code. The account country is used when empty. Example: US.
- `email` (`string`, optional): Email address of the person booking. Example: jane@example.com.
- `field_1_r` (`string`, optional): Value of the first custom appointment field. Example: First visit.
- `field_2_r` (`string`, optional): Value of the second custom appointment field. Example: Referral.
- `finish` (`string`, optional): Resource schedules: end time in local time, as YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 11:00:00.
- `form_id` (`integer`, optional): ID of an existing custom form to attach to the appointment. Example: 12345.
- `full_name` (`string`, optional): Full name of the person booking. Example: Jane Doe.
- `mobile` (`string`, optional): Mobile number. Example: +1 555 0101.
- `phone` (`string`, optional): Phone number. Example: +1 555 0100.
- `resource_id` (`string`, optional): Resource schedules with several resources: the resource ID or name, from supersaas_resources_list. Example: Room 1.
- `slot_id` (`integer`, optional): Capacity schedules: ID of the slot to book into, from supersaas_slots_list or supersaas_availability_list. Example: 98765.
- `start` (`string`, optional): Resource schedules: start time in the schedule's local time, as YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 10:00:00.
- `super_field` (`string`, optional): Value of the supervisor-only field. Example: Paid at desk.
- `user_id` (`string`, optional): Create the appointment on behalf of this user: SuperSaaS user ID, or your own key with fk such as 567fk. Example: 567fk.
- `webhook` (`boolean`, optional): Set true to trigger the webhooks connected to the account or schedule. Example: false.

Example input: `{"schedule_id":524012}`

### `supersaas_booking_update`

Update Appointment · Write

Update a SuperSaaS appointment. Only the fields you send change.
Returns HTTP 200 with an empty body, 404 if it no longer exists, or 422 with errors.
Use supersaas_booking_get first to see current values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): Appointment (booking) ID. Example: 1234567.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `address` (`string`, optional): Postal address. Example: 1 Main Street, Springfield.
- `country` (`string`, optional): Two-letter ISO 3166-1 country code. The account country is used when empty. Example: US.
- `email` (`string`, optional): Email address of the person booking. Example: jane@example.com.
- `field_1_r` (`string`, optional): Value of the first custom appointment field. Example: First visit.
- `field_2_r` (`string`, optional): Value of the second custom appointment field. Example: Referral.
- `finish` (`string`, optional): Resource schedules: end time in local time, as YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 11:00:00.
- `form_id` (`integer`, optional): ID of an existing custom form to attach to the appointment. Example: 12345.
- `full_name` (`string`, optional): Full name of the person booking. Example: Jane Doe.
- `mobile` (`string`, optional): Mobile number. Example: +1 555 0101.
- `phone` (`string`, optional): Phone number. Example: +1 555 0100.
- `resource_id` (`string`, optional): Resource schedules with several resources: the resource ID or name, from supersaas_resources_list. Example: Room 1.
- `slot_id` (`integer`, optional): Capacity schedules: ID of the slot to book into, from supersaas_slots_list or supersaas_availability_list. Example: 98765.
- `start` (`string`, optional): Resource schedules: start time in the schedule's local time, as YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 10:00:00.
- `super_field` (`string`, optional): Value of the supervisor-only field. Example: Paid at desk.
- `webhook` (`boolean`, optional): Set true to trigger the webhooks connected to the account or schedule. Example: false.

Example input: `{"id":1234567,"schedule_id":524012}`

### `supersaas_promotion_duplicate`

Duplicate Promotion Code · Write

Create a new coupon code by copying an existing code's settings.
Returns the result of the copy.
Create the template code on the Promotions screen first; this tool cannot set discount rules itself.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `id` (`string`, required): The new coupon code to create. Example: SPRING25-JANE.
- `template_code` (`string`, required): The existing coupon code to copy. Example: SPRING25.

Example input: `{"id":"<id>","template_code":"<template_code>"}`

### `supersaas_slot_create`

Create Slot · Write

Create a slot in a capacity schedule; other fields take the schedule's defaults.
Returns HTTP 201 with an empty body; the new slot ID is in the Location header, so use supersaas_slots_list to find it.
Use the slot ID as slot_id in supersaas_booking_create.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `finish` (`string`, required): End time in local time, as YYYY-MM-DD HH:MM:SS. Must be after start. Example: 2026-12-01 19:00:00.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `start` (`string`, required): Start time in the schedule's local time, as YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 18:00:00.
- `capacity` (`string`, optional): Number of places. Send - for no limit, or 0 to accept no appointments. Example: 12.
- `color` (`string`, optional): Color: a hex code such as #112233, or a number from 0 to 14 for a standard color. Example: #3366cc.
- `description` (`string`, optional): Longer description, up to 2000 characters. Example: Beginner-friendly flow class.
- `location` (`string`, optional): Location of the slot. Example: Studio A.
- `price` (`string`, optional): Price of one appointment, when the schedule takes payment. Example: 15.00.
- `title` (`string`, optional): Title shown on the slot. Example: Yoga class.

Example input: `{"finish":"<finish>","schedule_id":524012,"start":"<start>"}`

### `supersaas_slot_update`

Update Slot · Write

Update a slot in a capacity schedule. Only the fields you send change; other occurrences of a repeating series are not changed.
Returns HTTP 200 with an empty body, 404 if it no longer exists, or 422 with errors.
Use supersaas_slot_get first to see current values.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): Slot ID. Example: 98765.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `capacity` (`string`, optional): Number of places. Send - for no limit, or 0 to accept no appointments. Example: 12.
- `color` (`string`, optional): Color: a hex code such as #112233, or a number from 0 to 14 for a standard color. Example: #3366cc.
- `description` (`string`, optional): Longer description, up to 2000 characters. Example: Beginner-friendly flow class.
- `finish` (`string`, optional): End time in local time, as YYYY-MM-DD HH:MM:SS. Must be after start. Example: 2026-12-01 19:00:00.
- `location` (`string`, optional): Location of the slot. Example: Studio A.
- `price` (`string`, optional): Price of one appointment, when the schedule takes payment. Example: 15.00.
- `start` (`string`, optional): Start time in the schedule's local time, as YYYY-MM-DD HH:MM:SS. Example: 2026-12-01 18:00:00.
- `title` (`string`, optional): Title shown on the slot. Example: Yoga class.

Example input: `{"id":98765,"schedule_id":524012}`

### `supersaas_user_create`

Create User · Write

Create a user in your SuperSaaS account; SuperSaaS assigns the ID.
Returns HTTP 201 with an empty body; the new ID is in the response's Location header, so use supersaas_users_list to find the user afterwards.
Use supersaas_user_update with your own key (such as 567fk) to create or update a user under your own ID.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Login name of the user, up to 50 characters. Must be an email address if the account uses email addresses as login names. Example: jane@example.com.
- `address` (`string`, optional): Postal address. Example: 1 Main Street, Springfield.
- `country` (`string`, optional): Two-letter ISO 3166-1 country code. Example: US.
- `credit` (`string`, optional): Credit balance, in the format chosen on the Payment Setup screen. Example: 10.
- `duplicate` (`string`, optional): Set raise to fail with an error instead of updating when the user already exists. Example: raise. One of: `raise`.
- `email` (`string`, optional): Email address. Ignored when the login name is the email address. Example: jane@example.com.
- `field_1` (`string`, optional): Value of the first custom user field. Example: Member.
- `field_2` (`string`, optional): Value of the second custom user field. Example: Gold.
- `full_name` (`string`, optional): Full name. Example: Jane Doe.
- `group` (`integer`, optional): ID of the group to put the user in, from supersaas_groups_list. Example: 1201.
- `mobile` (`string`, optional): Mobile number. Example: +1 555 0101.
- `phone` (`string`, optional): Phone number. Example: +1 555 0100.
- `role` (`integer`, optional): User role: 3 regular user (default), 4 superuser, -1 blocked. Example: 3. One of: `3`, `4`, `-1`.
- `super_field` (`string`, optional): Value of the supervisor-only field. Example: VIP.
- `timezone` (`string`, optional): IANA time zone. Example: America/New_York.
- `webhook` (`boolean`, optional): Set true to trigger the webhooks connected to the account or schedule. Example: false.

Example input: `{"name":"<name>"}`

### `supersaas_user_update`

Update or Create User · Write

Update a SuperSaaS user by ID. If the user does not exist it is created, unless notfound is set.
Returns HTTP 200 on success, or 422 with errors.
Use your own key with an fk suffix (such as 567fk) to keep SuperSaaS in sync with your user database.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): User ID: the SuperSaaS numeric ID, or your own key followed by fk, such as 567fk. Example: 567fk.
- `address` (`string`, optional): Postal address. Example: 1 Main Street, Springfield.
- `country` (`string`, optional): Two-letter ISO 3166-1 country code. Example: US.
- `credit` (`string`, optional): Credit balance, in the format chosen on the Payment Setup screen. Example: 10.
- `email` (`string`, optional): Email address. Ignored when the login name is the email address. Example: jane@example.com.
- `field_1` (`string`, optional): Value of the first custom user field. Example: Member.
- `field_2` (`string`, optional): Value of the second custom user field. Example: Gold.
- `full_name` (`string`, optional): Full name. Example: Jane Doe.
- `group` (`integer`, optional): ID of the group to put the user in, from supersaas_groups_list. Example: 1201.
- `mobile` (`string`, optional): Mobile number. Example: +1 555 0101.
- `name` (`string`, optional): Login name of the user, up to 50 characters. Must be an email address if the account uses email addresses as login names. Example: jane@example.com.
- `notfound` (`string`, optional): What to do when the user does not exist: error returns 404, ignore returns 200 without creating. Leave empty to create the user. Example: error. One of: `error`, `ignore`.
- `phone` (`string`, optional): Phone number. Example: +1 555 0100.
- `role` (`integer`, optional): User role: 3 regular user (default), 4 superuser, -1 blocked. Example: 3. One of: `3`, `4`, `-1`.
- `super_field` (`string`, optional): Value of the supervisor-only field. Example: VIP.
- `timezone` (`string`, optional): IANA time zone. Example: America/New_York.
- `webhook` (`boolean`, optional): Set true to trigger the webhooks connected to the account or schedule. Example: false.

Example input: `{"id":"<id>"}`

### `supersaas_booking_delete`

Delete Appointment · Destructive

Delete (cancel) a SuperSaaS appointment.
Returns HTTP 200 when deleted, or 404 when it no longer exists.
Use this to cancel a booking.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): Appointment (booking) ID. Example: 1234567.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.
- `webhook` (`boolean`, optional): Set true to trigger the webhooks connected to the account or schedule. Example: false.

Example input: `{"id":1234567,"schedule_id":524012}`

### `supersaas_promotion_delete`

Delete Promotion Code · Destructive

Delete a coupon code. Bookings that used it keep their discount.
Returns HTTP 200 when deleted, or 404 when the code does not exist.
Use this to retire a code.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): The coupon code to delete. Example: SPRING25-JANE.

Example input: `{"id":"<id>"}`

### `supersaas_slot_delete`

Delete Slot · Destructive

Delete a slot from a capacity schedule, together with every appointment booked into it, without notifying those people. This cannot be undone.
Returns HTTP 200 when deleted, or 404 when it no longer exists.
Use supersaas_slot_get first if you need a record of its bookings.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`integer`, required): Slot ID. Example: 98765.
- `schedule_id` (`integer`, required): Schedule ID. Get it from supersaas_schedules_list (it is also the number at the end of the schedule's Configure Overview URL). Example: 524012.

Example input: `{"id":98765,"schedule_id":524012}`

### `supersaas_user_delete`

Delete User · Destructive

Delete a SuperSaaS user.
Returns HTTP 200 when deleted, or 404 when the user does not exist.
Use this to remove users that left your system.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): User ID: the SuperSaaS numeric ID, or your own key followed by fk, such as 567fk. Example: 567fk.
- `webhook` (`boolean`, optional): Set true to trigger the webhooks connected to the account or schedule. Example: false.

Example input: `{"id":"<id>"}`

## Related

Other Calendar connectors ([all 25](/agentkit/connectors/?category=calendar)):

- [Google Calendar](/agentkit/connectors/googlecalendar/): Scalekit connector, OAuth, 30 tools
- [Zoom](/agentkit/connectors/zoom/): Scalekit connector, OAuth, 58 tools
- [Calendly](/agentkit/connectors/calendly/): Scalekit connector, OAuth, 64 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
