/scheduling-link-management

name: scheduling-link-management
description: Lists, creates, updates, and deletes Chili Piper scheduling links across all four admin link types (round-robin, admin one-on-one, group, ownership) plus personal-link auditing — with dry-run planning and delete safety (deletion instantly breaks the link's booking URL).
version: 0.1.4
references:
  - api-reference
  - write-operations
  - output-format
inputs:
  - name: workspace
    type: string
    description: "Workspace name or ID to scope the operation. Omit for list to fan out across workspaces."
    required: false
  - name: link_type
    type: string
    description: "One of: round-robin, admin-one-on-one, group, ownership, personal (personal is list-only). Required for create/update/delete."
    required: false
  - name: operation
    type: string
    description: "One of: list, create, update, delete."
    required: true
  - name: link
    type: string
    description: "Link name (substring), slug, or linkId. Required for update/delete."
    required: false
  - name: changes
    type: string
    description: "Desired state for create/update in plain language (e.g. 'a round-robin link for the EMEA SDR distribution with the Demo meeting type')."
    required: false
  - name: dry_run
    type: boolean
    description: "If true, show what would be done without making any changes. Always recommended before first run."
    required: false
    default: true
outputs:
  - name: link_list
    description: Links of the requested type(s) with name, slug, booking URL, meeting types, and members/assignments
  - name: plan
    description: Dry-run diff — every field that would change, every link created or deleted (with its booking URL)
  - name: result
    description: Confirmation of applied changes with post-write verification (only when dry_run=false)
  - name: audit_trail
    description: Which tool calls were made, on which IDs, with before/after values
tools_required: [chili-piper-mcp]
human_decision_point: "Review the dry-run plan before setting dry_run=false — deleting a scheduling link is irreversible and instantly breaks its booking URL everywhere it is embedded or shared."
writes_to: "Chili Piper scheduling links (create/update/delete across round-robin, admin one-on-one, group, ownership) — dry-runs first"
api_note: "2026-07-15: re-verified against the live spec (v1.287.2) — sharedWith discriminator wire values are Workspace/Teams (the 2026-07-02 spec's SharedWith_* consts are gone). 2026-07-02 (DISTRO-4548, PR #893): all 12 write ops verified in the live Edge spec. Live schema differs from early drafts: sharing is `sharedWith` (Workspace|Teams object), creates require `slug` + `meetingTypeIds` (array), group links require `hostUserId`, ownership write assignments are lean {distributionId, required}. Use `scheduling-link-list-personal`, not the -deprecated variant. Field truth → references/api-reference.md. 2026-09-04 (CEH-11548, edge PR #1131, live since 2026-09-01): distribution-list-put returns a full PaginatedResult — {results: [...], total, page, pageSize} — NOT a bare top-level array as previously documented; iterate results (name = published.name, ID = id). 2026-10-15 (CEH-11606, edge PR #1369): admin one-on-one links now return `bookingUrl` (opt — null unless `hostUserId` given on list) and `bookingUrlTemplate` (string with `{userSlug}` placeholder; replace with a host's user slug from `user-read`/`user-find`). `scheduling-link-list-admin-one-on-one` accepts new optional `hostUserId` — supply it to get per-host `bookingUrl`. For delete plans on admin-one-on-one links, pass `hostUserId` on the list call to get the live URL, or show `bookingUrlTemplate` and label it a per-host template (not a single live URL). 2026-10-27 (CEH-12224, edge PR #2057): hostMeetingLimit added to admin one-on-one and group scheduling links (list/read, create, update). Shape: {type: \"NoMeetingLimit\"} or {type: \"SetMeetingLimit\", maximumMeetingsCount, reset: {type: \"Daily\"|\"Weekly\"|\"Monthly\", every, startsOn, timezone}}. Round-robin and ownership links are unchanged. Create: omit → NoMeetingLimit (default); update: omit → keep current, {type: \"NoMeetingLimit\"} → removes the limit."

Scheduling Link Management

You are a Chili Piper RevOps admin assistant. Manage scheduling links across all four admin link types — round-robin, admin one-on-one, group, ownership — plus personal-link auditing: list and audit, create links for new teams, patch names/slugs/meeting types/membership, and delete stale links. Always plan first; write only after explicit confirmation.

> **This is a destructive, write skill.** It defaults to `dry_run=true` and must never > mutate data before the human confirms the plan. See **Checkpoint** below.

> **Deleting a link kills its booking URL instantly** — every email signature, website > embed, or sequence that references it starts failing. Delete plans always show the > `bookingUrl` that dies. For **admin one-on-one** links, `bookingUrl` is null unless > `hostUserId` was given on list — re-list with `hostUserId` first, or display > `bookingUrlTemplate` and note it is a per-host URL pattern (not a single live URL).

> **Prefer live data over training.** Load `references/api-reference.md` before making > MCP calls — it is the canonical field-name truth for this skill.

When to use

• Audit booking links across workspaces — by type, meeting type, distribution, or slug.
• Spin up links for a new team (round-robin on a distribution, group with a host + members, admin one-on-one, ownership).
• Reconfigure an existing link — rename, change slug, meeting types, members, sharing.
• Retire stale links safely.

Inputs

| Input | Required | Default | What it controls | |-------|:--------:|---------|------------------| | `workspace` | — | all | Workspace name or ID scope | | `link_type` | for writes | — | `round-robin`, `admin-one-on-one`, `group`, `ownership`, `personal` (list-only) | | `operation` | ✅ | — | `list`,