Connect Claude & ChatGPT to Endear

27 tools for Endear

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• assign_customerChanges dataAssign one or more users (`assignee_ids`) to a customer by customer `id`, optionally notifying them.
• book_appointmentVisible to othersBook an appointment on `appointment_calendar_id` and `appointment_booking_page_id` from `start_date_time` to `end_date_time` for a `booker` (first name, email address, time zone, optional phone and notes). The customer may be notified.
• cancel_appointmentDeletesCancel an appointment by `id`, with an optional note for the cancellation notice. The customer is notified unless `suppress_notifications` is true.
• create_customerChanges dataCreate a customer from a list of `attributes`, each a field `key` (see list_customer_fields) with a typed value such as string, email_address or phone_number; optionally assign users with `assigned_to`. Search first to avoid duplicates.
• create_noteChanges dataAdd a note, optionally linked to a customer by `customer_id`, with `title`, `description` and `tags`.
• create_taskChanges dataCreate a task with `title`, `description`, optional `customer_id`, `deadline` {date, time}, `assignee_ids`, repeat schedule and tags. Set `notify_assignees` to notify the assigned users.
• delete_taskDeletesDelete a task by `id`, with `editor_id` of the user making the change.
• get_conversationChanges dataGet one conversation by `id`.
• get_current_brandChanges dataGet the Endear brand this connection belongs to. Use to confirm which brand you are working in.
• get_userChanges dataGet one user by `id` or `username`.
• list_appointment_calendarsChanges dataList appointment calendars, optionally filtered by status or owning team/user. Their IDs are needed to book appointments.
• list_appointment_typesChanges dataList the appointment types (for example styling sessions or fittings) the brand offers. Set `include_deleted` to false to skip removed ones.
• list_booking_pagesChanges dataList appointment booking pages, optionally for one `appointment_type_id`. Their IDs are needed to book appointments.
• list_customer_fieldsChanges dataList the customer fields (built-in and custom) with their keys and types. Use the keys when creating or updating customers.
• reschedule_appointmentChanges dataMove an appointment by `id` to a new `target_start_date_time` and `target_end_date_time`. Set `send_customer_notification` to tell the customer.
• search_appointmentsChanges dataSearch appointments by `search` text or `filters`, paginated with `first`/`after`.
• search_conversationsChanges dataSearch customer conversations by `search` text or `filters`, paginated with `first`/`after`.
• search_customersChanges dataSearch customers by `search` text (name, email, phone) with optional `filters`, sorted by created date, last purchase, total spend or name. Paginate with `first`/`after`. Use this to find a customer before creating one.
• search_messagesChanges dataSearch individual messages sent to or received from customers by `search` text or `filters`, paginated with `first`/`after`.
• search_notesChanges dataSearch notes left on customers by `search` text or `filters`, paginated with `first`/`after`.
• search_productsChanges dataSearch product variants in the brand's catalog by `search` text or `filters`, paginated with `first`/`after`.
• search_tasksChanges dataSearch tasks by `search` text or `filters`, paginated with `first`/`after`.
• search_user_profilesChanges dataSearch the brand's user profiles (store associates and staff) by `search` text. Use to find user IDs for assigning customers, tasks and appointments.
• set_appointment_statusChanges dataMark an appointment by `id` as SCHEDULED, COMPLETED or NO_SHOW; `actor` is {userId} of the user making the change. Use cancel_appointment to cancel.
• update_customer_fieldChanges dataChange one field on a customer: customer `id`, field `key`, and `changes` such as {type: SET, attribute: {string: {value: ...}}}; CLEAR empties the field.
• update_noteChanges dataUpdate a note by `id`: title, description, tags or linked customer. Only the fields you pass change.
• update_taskChanges dataUpdate a task by `id` (with `editor_id`, the user making the change): title, description, deadline, assignees, or `completed`=true to mark it done.

Questions