# clearEmployeeSchedule

Drop the schedule of one employee on one contact (`attachmentId` from getContactEmployees). It stays on the contact and still answers when the contact writes in. Safe to repeat. A booked FOLLOW_UP is not a schedule: that is cancelEmployeeFollowUp.

- Call: `POST https://server.goliathdata.com/api/v1/call` with `{ "operationId": "clearEmployeeSchedule", "variables": {...} }`
- Scope: `WRITE`
- Type: mutation
- Idempotency: honors `Idempotency-Key` (24 h)
- Rate-limited: no

## Variables

- `attachmentId`: `ID!` (required)

## Response (data, an example)

```json
{
  "aiEmployeesMutation": {
    "clearAiEmployeeSchedule": {
      "id": "<ID>",
      "agentId": "<ID>",
      "status": "ACTIVE"
    }
  }
}
```

## Example

```bash
curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "clearEmployeeSchedule",
    "variables": {
      "attachmentId": "<attachmentId>"
    }
  }'
```