Integration

DaySchedule integration

DaySchedule is appointment scheduling software with a booking CRM. Check open time slots of an event type, webinar or service; create, read, update, confirm, reschedule, cancel, reassign and delete bookings; manage invitees, their status and check-in; manage CRM contacts and their notes, calls and tasks; manage the waiting list; read booking pages, working-hour schedules, users and teams; and pull booking and revenue reports. Bookings, invitees, contacts and waiting list entries hold personal data. Left out: configuring event types, booking pages, schedules, teams and users, automation workflows, email campaigns and messages, short links and their analytics, background jobs and file storage. Authentication is an API key from Settings, API keys in the DaySchedule app, sent as the apiKey query parameter.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DaySchedule.Built from the 47 DaySchedule tools below, on the connection you add once.

What you can do with DaySchedule

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Id, 22 operations

  • delete_activityDelete activityDELETEDeletes a contact activity.
  • delete_bookingDelete bookingDELETEDeletes a booking. Use cancel_booking instead to cancel it with a reason and notify the people involved.
  • delete_contactDelete contactDELETEDeletes a CRM contact.
  • delete_inviteeDelete inviteeDELETERemoves an invitee from its booking.
  • delete_waitlist_entryDelete waitlist entryDELETERemoves a person from the waiting list.
  • get_activityGet activityGETReturns one contact activity (note, call or task) with its status, date, attached file and the user who logged it.
  • get_availabilityGet availabilityGETReturns the open time slots of an event type, webinar or service between two dates, per day with the remaining capacity and the users free in each slot, in the requested time zone.
  • get_bookingGet bookingGETReturns one booking with host, resource, time, status, location, calendar links, reschedule history, attendees, and invitees with their answers, payment and check-in state.
  • get_contactGet contactGETReturns one CRM contact (personal data) with email, phone, company, location, source, rating, tags, custom fields and follow-up date.
  • get_inviteeGet inviteeGETReturns one invitee with contact details, status, cancel reason, answers, services, payment, check-in state and UTM tracking (personal data).
  • get_pageGet pageGETReturns one booking page with its domain, description, logo, colors, branding, SEO and analytics integration ids.
  • get_resourceGet resourceGETReturns one event type, webinar or service with all its settings: scheduling window, notice, durations, prices, capacity, locations, members, intake questions and booking URL.
  • get_scheduleGet scheduleGETReturns one working-hour schedule: time zone, available hours per weekday with per-slot limits, daily limit and default flag.
  • get_teamGet teamGETReturns one team with its name, description and users.
  • get_userGet userGETReturns one user of the account with email, role, status, permissions, location, time zone and team access.
  • get_waitlist_entryGet waitlist entryGETReturns one waiting list entry: the person's contact details, the wanted slots, status and when they were notified.
  • update_activityUpdate activityPATCHUpdates the fields given on a contact activity: type, title, description, status, date or file.
  • update_bookingUpdate bookingPUTUpdates a booking: host, start time, location and invitees are required; subject, description, status, color and notes are optional. Use reschedule_booking to only move the time.
  • update_booking_internal_noteUpdate booking internal notePATCHSets the internal note of a booking (visible to your team only).
  • update_contactUpdate contactPATCHUpdates the fields given on a CRM contact (name, email, phone, company, city, country, source, rating, tags, custom fields, follow-up date).
  • update_inviteeUpdate inviteePUTUpdates an invitee: name (required), email or phone, guests, status, time zone, answers, services, payment and custom fields.
  • update_waitlist_entryUpdate waitlist entryPUTUpdates a waiting list entry: email, wanted slots and status are required, name and mobile optional.

Activity, 2 operations

  • create_activityCreate activityPOSTLogs an activity on a CRM contact: a note, a call or a task, with title, description, status, date and an optional file reference.
  • list_activitiesList activitiesGETLists the activities (notes, calls and tasks) logged on a CRM contact, with status, date, attached file and the user who logged it.

Assignee, 2 operations

  • assign_bookingAssign bookingPATCHReassigns a booking to another user of your team. With notify_all, DaySchedule emails the new assignee, with the reason if given.
  • assign_contactsAssign contactsPUTAssigns one or more CRM contacts to a user of your team.

Booking, 2 operations

  • create_bookingCreate bookingPOSTBooks an appointment: a host user, a start time, a location and at least one invitee (name plus email or phone). DaySchedule can send confirmation emails and calendar invites, as the event settings decide. payment=1 adds a payment link.
  • list_bookingsList bookingsGETLists appointment bookings with host, resource, start and end time, status, location, invitees and their answers. Filter by date range, user, email or search text; paginated with offset and limit.

Contact, 2 operations

  • create_contactCreate contactPOSTCreates a CRM contact: a name plus an email or phone, and optionally company, city, country, source, rating, tags, custom fields and a follow-up date.
  • list_contactsList contactsGETLists the CRM contacts (personal data) with email, phone, company, city, source, rating, tags, custom fields and follow-up date. Filter with search; paginated.

Invitee, 2 operations

  • create_inviteeCreate inviteePOSTAdds an invitee to an existing booking, with name, email or phone, status, time zone, answers to the intake questions and custom fields.
  • list_inviteesList inviteesGETLists the invitees of one booking with their contact details, status, answers to the intake questions, payment, check-in state and tracking data (personal data). Paginated.

Waitlist, 2 operations

  • create_waitlist_entryCreate waitlist entryPOSTAdds a person to the waiting list for one or more date and time slots, by email (name and mobile optional).
  • list_waitlist_entriesList waitlist entriesGETLists the people on the waiting list (personal data) with the date and time slots they want and whether they were notified. Paginated.

Attendee, 1 operation

  • set_booking_attendeesSet booking attendeesPATCHSets the attendees of a booking (the guests added with the guest option), replacing the current list.

Bulk, 1 operation

  • import_contactsImport contactsPOSTImports several CRM contacts in one call; each needs a name plus an email or phone.

Cancel, 1 operation

  • cancel_bookingCancel bookingPATCHCancels a booking with a reason. With notify_all, DaySchedule notifies the people involved.

Checkin, 1 operation

  • check_in_inviteeCheck in inviteePATCHMarks an invitee as checked in (or not) at the appointment and records custom field values.

Confirm, 1 operation

  • confirm_bookingConfirm bookingPATCHSets the status of a booking to confirmed (the default), completed or noshow.

Dashboard, 1 operation

  • get_dashboard_reportGet dashboard reportGETReturns one booking or revenue report for a period, under a key named after the report: bookings by user, date or status, revenue by currency, date or gateway, popular resources and weekdays, busiest users, new vs repeat customers.

Page, 1 operation

  • list_pagesList pagesGETLists the account's booking pages with their domain, branding, visibility and SEO settings. Paginated.

Reschedule, 1 operation

  • reschedule_bookingReschedule bookingPATCHMoves a booking to a new start time with a reason; the end time follows the duration unless given. With notify_all, DaySchedule notifies the people involved.

Resource, 1 operation

  • list_resourcesList resourcesGETLists the account's bookable resources (event types, webinars and services) with their settings, durations, prices, locations, intake questions and booking URL.

Schedule, 1 operation

  • list_schedulesList schedulesGETLists the working-hour schedules with their time zone, weekly availability, daily limit and default flag. Paginated.

Status, 1 operation

  • update_invitee_statusUpdate invitee statusPATCHChanges an invitee's status (confirmed, canceled, completed, no-show and others) with an optional reason. With notify_all, DaySchedule notifies the people involved.

Team, 1 operation

  • list_teamsList teamsGETLists the account's teams with their name, description and users. Paginated.

User, 1 operation

  • list_usersList usersGETLists the users of the DaySchedule account with their email, role, status, permissions, time zone and team access. Paginated.

Use DaySchedule from Claude Code, Cursor or Codex

Connect DaySchedule in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DaySchedule operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect DaySchedule

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect DaySchedule once

    Add your DaySchedule connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

DaySchedule integration FAQ

What can you do with the DaySchedule integration?

LiveContext exposes 47 operations on DaySchedule, covering id, activity, assignee and booking.

Popular integrations

Browse the whole catalog