- Brand
- Unknown
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
Habyt ayuda a negocios a operar sus programas de lealtad digital desde ChatGPT. Los propietarios autenticados pueden consultar tarjetas, clientes, pases, sucursales y estadísticas; crear y actualizar tarjetas; registrar sellos o puntos; y preparar notificaciones. Habyt solo accede a la cuenta conectada y solicita confirmación explícita antes de aplicar cambios.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-11-04
- Tool count
- 71
- Market
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Your score is coming
ChatGPT now suggests Plugins on its own when they match a user's request.Your Plugin Discovery Score measures how often yours appears, and it will show here as soon as it’s ready.
What discovery looks like

Get alerts for Habyt
Get updates when Habyt’s Discoverability Score or category rank changes.
Competitive lineup
71 tools agents can invoke
Statistics KPIs for any period, including today. Alias: habyt_get_account_statistics. today, yesterday, this_week, last_week, this_month, or custom dates. tracked_revenue is registered sales.
get_account_statistics
Add points to one issued loyalty pass. Provide quantity as points, or amount in MXN to calculate points using the card rate. Requires confirmation before writing.
add_loyalty_points
Add stamps to one issued stamp pass. Resolves a unique customer/card, reads the current pass state, and requires confirmation before writing. This records a loyalty movement; it does not charge a payment terminal.
add_pass_stamps
Edit a published Habyt card in place (images, logos, colors, copy). For stamp/sessions cards, strip-image input is automatically treated as strip-background-image so the existing stamp design is preserved and the composed strip is regenerated. Reads current config first, applies a partial patch, then requires confirmation_token. Fields disabled in the template edit form are rejected, including coupon type 2 Valor de Campo Personalizado (custom-field-*). Image/color/logo changes update issued passes on Wallet sync. apple-icon is the Apple lock-screen icon and often does NOT change on already-installed iPhones — warn before changing it. Do not draw a fake Wallet mockup; call this tool.
update_card_template
Applies an already prepared live-card edit. Prefer update_card_template for new edits (strip-image, colors, logos). Use this if you already have a confirmation_token from validate_template_draft or update_card_template.
confirm_template_update
Link store locations to a live card (Geo-Push). By default location_names are ADDED to existing stores (merge). Set replace_existing=true to set the exact list. Empty location_names removes all. Requires confirmation.
assign_card_locations
Assign images to a draft or a live card. Prefer this after receiving a chat image. For stamp/sessions cards, the background where stamps appear is strip-background-image; strip-image is accepted as an alias and remapped automatically while preserving the existing stamp design. Pass draft_id, or card_id/card_name to open an edit draft automatically. Public https or data:image URLs. Confirm template updates after attachment.
attach_draft_assets
History of automated notification job runs that sent to your passes (status, dates, rule types). Same data as History on /app/notifications/automated-notifications. Optional card_name filter.
list_automated_notification_history
REQUIRED for a push/aviso to ONE named person. NEVER use the mass-send tool for one customer. A unique customer and card are resolved automatically; call request_token=true immediately and use the final summary as the sole confirmation. Ask only if several people or cards match. Sends only to that person's active pass. Max 100 characters; emojis only for in-house cards.
habyt_send_customer_push
Read-only customer resolver. Use for lookup questions or when an action tool cannot resolve customer_name itself. A single person and single card is unambiguous: continue to request_token=true in the same turn and include identity in the final summary. Ask only when several people or cards match. Never invent an email. Same data as search_customer_passes.
habyt_find_customer
Cancel a wallet push that was scheduled for the future (status pending). Identify by card_name + scheduled_for and/or message_contains, or notification_id from list_sent_notifications. Requires confirmation_token.
cancel_scheduled_notification
READ mcp_server_version and which habyt_* tools exist (notifications, locations, managers, push, plan). REQUIRED when the user asks «mcp_server_version», «qué versión MCP», «qué puedes hacer», or before saying a feature is unavailable. NEVER say get_mcp_capabilities is not exposed — this tool IS the connector capability map.
habyt_get_mcp_capabilities
READ organization-wide favorite customers (marcados como favorito en Habyt). REQUIRED when the user asks «quiénes son mis clientes favoritos», «mis favoritos», etc. — NOT recent_transactions or rankings. Returns count=0 and empty favorites when none (success, not error). To mark or remove, use habyt_set_customer_favorite.
habyt_list_favorite_customers
Create/update automated notification rules (message, active/inactive, days/points config) — same as editing /app/notifications/automated-notifications. REQUIRED to change automated rules from chat. Flow: request_token=true → confirm → confirmation_token. Types: birthday, anniversary, inactivity, welcome_followup, expiration_reminder, points_milestone, next_reward.
habyt_upsert_automated_notification
Creates the live card template after explicit user confirmation. Requires confirmation_token from validate_template_draft. Returns spoken text: explain that the card is live and offer link, QR, and/or printable PDF — ask if the user wants you to share them here. Then use confirm_issuance_link_creation when they pick formats.
confirm_template_creation
Sends a message to support.habyt@solidsens.com for the signed-in owner (same email flow as Dashboard «Reportar un error»). REQUIRED when the user says: «contáctame con soporte», «escribe a soporte», «reportar error», or asks whether a configuration is possible and wants Habyt team to answer — use message with their question (Spanish OK, min 10 chars). This connector HAS support email — NEVER say there is no support channel. If they ask «¿se puede configurar X?», call get_mcp_capabilities first to answer what MCP can do; then offer to email support for the rest. Flow: request_token=true → show summary → user confirms → confirmation_token.
habyt_contact_support
Creates a real store location in the owner's Habyt account. REQUIRED when the user asks to create/add a sucursal, tienda, or ubicación — NEVER say the connector cannot create locations or only prepare data for the web form. Ask ONLY: name, address (or Maps link you geocode), optional geo-push message. Do NOT ask for opening hours, phone, scan radius, or card assignment (use assign_card_locations after). Then call this tool with latitude/longitude. User saying «crea la sucursal» is explicit consent to create.
habyt_create_location
Optional upload form. Use only if the user prefers to drop their own files, or attach_draft_assets cannot use a public https/data URL (sandbox:/mnt/data). Prefer attach_draft_assets so non-technical users stay in ChatGPT. Always show upload_url as a markdown link.
create_asset_upload_session
Activate/deactivate or edit message and configuration for one automated rule on a card (confirm). Prefer habyt_upsert_automated_notification. configuration_value: days/years/points or reward distance shortcut matching the UI edit form.
upsert_automated_notification
Save a proposed card template. For new cards, catalog_id is the preferred default because it preserves a complete design from /app/cards/new-card/from-template. Before calling this tool, show the selected template's general defaults and ask one consolidated optional review; omitted values keep the defaults. Skip that question only if the user already provided the relevant general data or explicitly said to use the template values. Use card_family + payload from scratch only when explicitly requested or no compatible catalog entry exists. Apply the user's payload as a minimal patch over the catalog base.
create_template_draft
Creates a store in Habyt (name, address, lat, long, optional geo-push text). Same as habyt_create_location. NEVER tell the user MCP cannot create locations. Do not ask for hours, phone, or radius.
create_location
Same as get_card_template. Use for design + rules of a named Habyt card. Never browse the Habyt website.
habyt_get_card_design_and_rules
Load live Habyt card design, colors, logos, strip-image status, messages, and program rules by card_name (e.g. Club Café Norte). REQUIRED for «muéstrame el diseño y reglas», «cómo está configurada la tarjeta». Returns payload + design + rules_es. Do NOT open habyt.solidsens.com in a browser — this tool has full data.
get_card_template
Updates an existing store: name, address, coordinates, geo-push global, or weekly geo_push_messages (monday–sunday + global). REQUIRED when the user asks to edit/change a sucursal, tienda, or geo-push text — NEVER say the connector cannot edit locations or only the web form. Use location_name (not UUID). request_token=true → show summary → confirmation_token. User «edita la sucursal X» is explicit consent for this flow.
habyt_update_location
Send or schedule manual Wallet push (Habyt Sandbox and prod). REQUIRED for «manda/envía notificación/push/aviso», all holders or filtered audience, now or scheduled_for. ONE named person → habyt_send_customer_push, never audience=all. This connector INCLUDES send — NEVER say Sandbox lacks push, notifications are disabled, or browser must open /app/notifications. Guide: card_name + message; audience=all or filtered+filters; request_token=true → recipient_count → user confirms → confirmation_token. Parámetros push manual (habyt_send_push_notification): • card_name — nombre de la tarjeta (list_card_templates si dudas). • message — texto del aviso (máx. 100 caracteres; emojis solo si la tarjeta usa motor in-house). • audience=all — todos los titulares activos de esa tarjeta; audience=filtered + filters — segmento. • filters (opcional): birthday (today|thisMonth), retention (active|atRisk|churned), gender, activity, age_group, country, city_state, tier, issued_from/to, transaction_count_min/max. • scheduled_for — ISO en el futuro para programar; omitir = enviar al confirmar. Flujo: request_token=true → muestra recipient_count y resumen → usuario confirma → misma llamada con confirmation_token. Nunca digas que Sandbox no incluye envío ni uses el navegador para mandar push.
habyt_send_push_notification
Account statistics for any question: sales/revenue, transactions, stamps, points, new passes, retention, peak hour, by card or store. REQUIRED for «¿cuánto vendí hoy?», «ayer», «esta semana», «cómo voy», «este mes». NEVER say there is no today cut or statistics are unavailable. Periods (America/Mexico_City): today, yesterday, this_week, last_week, this_month, one_month, two_months, six_months, one_year, or custom + date_from/date_to. Optional card_name and location_name. tracked_revenue is registered sales; $0 is valid. Read spoken.
habyt_get_account_statistics
Generate a downloadable statistics PDF (jsPDF, same KPI style as the dashboard). Ask the user which period in natural language: last month, two months, six months, one year, or custom dates. Map to period preset or date_from/date_to (YYYY-MM-DD). Read-only.
export_account_statistics_pdf
Read-only. Find issued passes by email or name. Continue automatically when one person/card matches; ask one disambiguation question only for multiple matches. Never invent an email. Same as habyt_find_customer.
search_customer_passes
Read which optional questions the public issuance form asks (phone, birth date, gender, country, city/state). Name, last name, and email are always required. Same as dashboard Distribuir → edit issuance form.
get_issuance_form_settings
Returns required fields, assets, locations, back fields, and rules. For card_family=coupon, includes subtype guidance: recommend coupon-type1 (promotion in offer-title only on front) vs coupon-type2 (up to 3 configurable front slots + title).
get_template_requirements
Issue a gift card pass with balance and email the recipient a gift link/PDF (same as Dashboard Regalar on gift templates). Not Mercado Pago Point. Requires request_token then confirmation_token. MCP owner account only.
issue_gift_card
Read-only onboarding checklist aligned with Habyt web tutorials: first location, first card, assign stores, issuance link, optional geo-push/managers. REQUIRED when the user asks to set up their program, «dejar listo», «por dónde empiezo», first connection, or step-by-step launch guide. NEVER auto-run create/update tools — user must opt in to follow each suggestion. Returns pending steps, MCP tools per step, and opt_in_prompt_es.
habyt_get_setup_guide
Returns the signed-in owner's Habyt plan (Inicial/Starter, Pro, Corporate), subscription status, trial or next billing date, and usage vs limits (cards, stores, managers). Use for: «cuál es mi plan», «qué plan tengo», «límites de mi cuenta», «¿soy Pro?», billing/trial questions. Read-only; does not change billing. For contacting support use submit_support_bug_report instead.
get_account_status
READ sent/scheduled manual Wallet push and automated runs (same as /app/notifications history). REQUIRED for «notificaciones enviadas», «últimos dos meses», «qué push mandé», message content with date and card — NEVER say history is disabled, missing permission, or that you only have cards/transactions/recent_transactions. Default last 60 days; pass days=60 for two months. Geo-push lock-screen deliveries are NOT logged per send (see geo_push.note_es).
habyt_list_notification_history
Same as habyt_list_automated_notifications. Full rules all cards when card_name omitted. NEVER refuse read citing disabled permission.
list_automated_notifications
List Habyt card templates (includes account_plan with subscription plan_label_es). For plan-only questions prefer habyt_get_subscription_plan. Design edits: get_card_template then update_card_template.
list_card_templates
List Habyt catalog pass templates (same as /app/cards/new-card/from-template), ordered by product priority. This is the default first step for creating a card unless the user explicitly asks to start from scratch. Choose a clear closest match automatically; ask one choice only when 2–3 materially different styles fit. Use catalog_id with create_template_draft and preserve the complete seeded design.
list_catalog_templates
Alias of habyt_list_favorite_customers — favorite customers by email. Prefer habyt_list_favorite_customers for Spanish prompts. count=0 when empty (not an error).
list_favorite_customers
List customer passes issued for a card template. Resolve the card by card_name (preferred) or card_id. Speak in natural Spanish; do not ask the user for internal IDs.
list_issued_passes
List store locations with geo-push config. Each row includes geo_push_messages_configured (global + lunes–domingo, labeled day_es), geo_push_mode_es, geo_push_message (vigente hoy), geo_push_vigente_fuente_es. Optional location_name for one store. REQUIRED for sucursales/tiendas/geo-push — NEVER say unavailable without calling this tool.
list_locations
Same as habyt_list_managers. List managers with stores, cards, PIN and statistics flags. NEVER refuse listing or ask for browser/screenshots.
list_managers
READ managers for the signed-in account owner: name, email, assigned stores, card templates they can scan, PIN requirement, statistics access. REQUIRED when the user asks «mis gerentes», «quién puede escanear», manager permissions, or team — NEVER say the connector cannot list managers, cannot open /app/managers, or ask for panel screenshots. Do NOT use get_account_status usage.managers alone (call this tool). count=0 is valid. Does NOT create/delete managers.
habyt_list_managers
Read-only: live balance, points, stamps, sessions, or coupon status for one issued pass. Use card_name + customer_email, or pass_code from QR/manual entry. Use this when the user only asks for current status; never invent balances.
get_issued_pass
REQUIRED to mark or remove a favorite. A unique customer name resolves automatically; call request_token=true immediately and use the final summary as the sole confirmation. Ask only when several people match. Does not issue a pass. Organization-wide by email.
habyt_set_customer_favorite
Same as habyt_get_subscription_plan — Habyt plan, trial, billing, limits (read-only).
get_habyt_plan
Alias of habyt_list_notification_history. Manual push history, pending scheduled, automated runs. days=60 for two months. NEVER refuse without calling this tool.
list_sent_notifications
Set the public distribution link to active or inactive (same as the dashboard Distribuir toggle). Requires confirmation_token. Set request_token=true first.
set_issuance_link_status
READ Habyt subscription plan for the signed-in owner. REQUIRED when the user asks: «cuál es mi plan de Habyt», «qué plan tengo», plan name, Inicial/Pro/Corporate, trial, billing renewal, or resource limits. Returns plan_label_es and usage vs limits. This connector HAS subscription access — never tell the user you only see cards.
habyt_get_subscription_plan
Alias of habyt_send_push_notification — manual Wallet push with confirmation. Prefer habyt_send_push_notification for Spanish «manda notificación» prompts.
preview_and_send_notification
Alias of habyt_get_mcp_capabilities. Prefer habyt_get_mcp_capabilities for version and capability checks.
get_mcp_capabilities
Habyt ChatGPT Plugin FAQ
How the directory, categories and Discoverability Score work.
Read the methodologyHow do I improve Habyt's ChatGPT Plugin discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.


