Hapee

Creates or updates up to 500 products at once (same as the spreadsheet upload in Hapee). Upsert by `sku`: an existing SKU is UPDATED, not duplicated. Each item: `sku` and `nombre` (required) and optional `descripcion_corta`, `descripcion_html`, `imagen_url`, `unidad`, `tipo`, `estado` (activo|inactivo), `categoria` (name, created if missing), `precios` ({"CLP": {"precio": 1000, "precio_min": 900, "costo": 600}, "USD": {...}}) and `campos_custom` ({key: value}; the property is created if missing). The answer has created/updated counts and per-row errors. Write all content in the language the user is speaking.

bulk_upsert_products

Cancels an appointment; the guest is notified and external calendars are updated. Confirm with the user first.

cancel_appointment

Cancels a campaign (stops whatever is still to be sent). Confirm with the user first.

cancel_email_campaign

Changes who attends an appointment (`host_user_id`; null = automatic rotation) and syncs the external calendars; check the `sync` part of the result. Confirm with the user first.

change_appointment_host

Copies a product WITH its prices and volume tiers.

clone_product

Connects a custom domain (`domain_type` subdomain | apex) and returns the DNS records the user must add at their DNS provider. Then verify_domain.

connect_domain

Maps the fields of a form to contact properties, CREATING the ones that do not exist, so every answer lands on the contact record. Existing properties are reused. `folder_name` (created if missing) groups the new properties; suggest one named after the form. `fields` (queryKeys) limits it to some fields; `types` forces the type of some. Updates the form's field mapping. Write all content in the language the user is speaking.

connect_form_to_properties

How many contacts would receive a campaign (read-only even though it is a POST: nothing is sent or saved). `audience`: {lista_id, tag_ids, contact_ids, segment_ids, exclude_segment_ids, exclude_lista_ids}. Unsubscribes, bounces and suppressions are already excluded.

count_email_audience

Creates a CRM task (call, send proposal, follow up...). REQUIRES `title`, `due_at` (ISO date-time; if the user did not say when, ASK) and a link to a contact, deal or company. A task linked to a deal inherits its contact and company. `assigned_to` defaults to the record owner. `priority`: baja (low) | media (medium) | alta (high) | urgente (urgent). `followers`: user ids that get notifications. Write all content in the language the user is speaking.

create_crm_task

Creates a blog category. Write all content in the language the user is speaking.

create_blog_category

Creates a blog post and returns its URL. `status` defaults to borrador (draft); publicado (published) puts it live on the public blog: confirm with the user before using it. Write all content in the language the user is speaking.

create_blog_post

Creates a booking calendar. `slug` is its PUBLIC booking URL and must be unique in the subaccount (409 if taken; normalized to lowercase-with-dashes). Without `timezone` the subaccount one is used. `extra` (API field names) accepts availability, buffers, min/max notice, location_type, reminders, pipeline_id/stage_id, form_id, etc. The booking page is public as soon as the calendar is active: confirm the name and slug with the user first. Write all content in the language the user is speaking.

create_calendar

Creates a CRM company. `extra` (API field names) accepts: rut, razon_social, dominio, sitio_web, telefono, email, direccion, ciudad, region, pais, industria, num_empleados, descripcion, revenue_anual, moneda, campos_custom. Write all content in the language the user is speaking.

create_company

Creates a contact. `email` is required. Search first with search_contacts (by email or phone) to avoid duplicates, or use upsert_contact. `contact_type`: lead | customer. `assigned_to`: owner user id (defaults to the signed-in user). `company_id`: CRM company from list_companies. `extra` accepts custom_fields, utm_*, website, address, city, region, country.

create_contact

Adds a note to a contact, authored by the signed-in user. If the contact has open deals (list_contact_deals), ask whether the note should also show on one of them and pass its `deal_id`. Write all content in the language the user is speaking.

create_contact_note

Creates a record of a custom object. `values`: {field_key: value} (keys from list_properties with object_type "co:<key>"). Write all content in the language the user is speaking.

create_custom_object_record

Creates a deal in a pipeline. ALWAYS linked to a contact (`contact_id` required): find it with search_contacts or create it first. Without `stage_id` it enters the first open stage (stage ids come from list_pipelines). `owner_id` defaults to the contact owner or the creator. `expected_close_date` is YYYY-MM-DD. The company is inherited from the contact unless `company_id` is given. Write all content in the language the user is speaking.

create_deal

Adds a note to a deal, authored by the signed-in user. `also_on_contact` is REQUIRED and the user decides it: before calling, ask whether the note should also appear on the deal's contact record (true) or only on the deal (false). Do not assume. Write all content in the language the user is speaking.

create_deal_note

Creates a DRAFT campaign (nothing is sent). Content: `template` (gallery index), `blocks` or `template_id` (saved template). Sender: `from_email` on a verified domain (list_email_senders), `sender_identity_id`, or nothing (platform sender). Include a `footer` block with the unsubscribe link. Write all content in the language the user is speaking.

create_email_campaign

Saves a reusable email template (blocks or a gallery template). Write all content in the language the user is speaking.

create_email_template

Creates a form as a DRAFT (publishing is a separate step: publish_form). Without `fields` it gets four defaults (email, name, phone, message). Own `fields` each need `id`, `type`, `queryKey` and `mapping`; without them the form looks fine but submissions do not create or update the contact (use connect_form_to_properties afterwards). Write all content in the language the user is speaking.

create_form

Creates a DRAFT funnel (nothing goes live). Without `steps` it starts with one opt-in step. `steps`: [{nombre, tipo (page | optin | sales | checkout | thank_you | webinar), slug?, template? (index from list_web_templates) or blocks?}]. Publish later with publish_funnel once the user approves. Write all content in the language the user is speaking.

create_funnel

Adds a DRAFT step at the end of a funnel, optionally with content (`template` index or `blocks`). `step_type`: page | optin | sales | checkout | thank_you | webinar. Write all content in the language the user is speaking.

create_funnel_step

Creates a DRAFT landing page (or a page of a site with `site_id`). Content: `template` (list_web_templates) or `blocks` (get_web_block_catalog). SEO: page_title (~60 chars) and meta_description (~155 chars). Returns the URL it will have once published. Write all content in the language the user is speaking.

create_page

Creates a sales pipeline. `stages`: list of {nombre, color, probabilidad, stage_type} where stage_type is open | won | lost. Without `stages` the six default stages are created. Write all content in the language the user is speaking.

create_pipeline

Adds a stage to a pipeline. `stage_type`: open | won | lost (won/lost count as closed in the forecast). Without `position` it goes last. Write all content in the language the user is speaking.

create_pipeline_stage

Creates a product. `extra` (API field names): sku, slug, descripcion_corta, categoria_id, tags, unidad, estado, impuesto_default_pct, campos_custom. The SKU must be UNIQUE (400 `sku_duplicado`). It is born WITHOUT a price: set one with save_product_price or it cannot be quoted. Write all content in the language the user is speaking.

create_product

Creates a product category (optionally under `parent_id`). Write all content in the language the user is speaking.

create_product_category

Creates a custom field. `field_type` (API values): texto (text) | textarea | numero (number) | monetario (money) | phone | email | url | dropdown | multiselect | radio | checkbox | fecha (date) | datetime... `extra` accepts opciones (choices), nombre (key), descripcion, placeholder, obligatorio, show_in_forms and the folder: `carpeta` (name, created if missing) or `folder_id` (list_property_folders). For the fields of a form, connect_form_to_properties creates and connects them in one go. Write all content in the language the user is speaking.

create_property

Creates a folder to group properties (e.g. the ones of a form). Write all content in the language the user is speaking.

create_property_folder

Creates a DRAFT quote (nothing is sent). Link it to a deal and/or contact. Add lines afterwards with add_quote_line; discounts and taxes with update_quote. Dates are YYYY-MM-DD. Write all content in the language the user is speaking.

create_quote

Creates a new editable version of a quote (e.g. after it was sent), authored by the signed-in user. The previous version is kept.

create_quote_version

Creates a DRAFT multi-page website. `fields` (API field names): slug, descripcion, default_title_suffix, default_og_image, favicon_url, logo_url, theme, default_lang. Then add pages with create_page(site_id) and menus with save_site_menu. Write all content in the language the user is speaking.

create_site

Deletes an AI agent. IRREVERSIBLE (there is no trash): confirm with the user first.

delete_ai_agent

Deletes a CRM task. IRREVERSIBLE (to close it instead use update_crm_task with status="completada"). Confirm with the user first.

delete_crm_task

Deletes a blog post. IRREVERSIBLE: confirm with the user first.

delete_blog_post

Deletes a calendar. If it has FUTURE pending or confirmed appointments it is archived instead (inactive) and the answer says how many. Without future appointments it is really deleted, with its past appointments and blocks. Confirm with the user first.

delete_calendar

Moves a contact to the trash. It can be brought back with restore_contact. Confirm with the user before deleting.

delete_contact

Deletes a contact note. IRREVERSIBLE: confirm with the user first.

delete_contact_note

Moves a deal to the trash (restore_deal brings it back). Confirm with the user first.

delete_deal