Skip to main content
Glama
606,627 tools. Updated 2026-09-24 10:13

"How to Create a WhatsApp Bot" matching MCP tools:

  • Update a WebZum site's universal contact fields — phone, email, WhatsApp, the primary contact channel, address, hours — OR the business/brand name. Use this (NOT update_site_html) for these fields: it updates the canonical business record AND sweeps every page, so contact-form delivery, tel:/mailto:/wa.me links, header, footer, page titles, and body copy all stay in sync. WhatsApp: pass an instruction like "add my WhatsApp +966 55 123 4567" (keep the country code) to render a wa.me click-to-chat button site-wide, or "make WhatsApp the main way to reach us" to set it as the primary CTA. Required: businessId, versionId, and a conversationHistory containing at least one user turn describing the change verbatim. Do NOT use for general copy/layout edits (use update_site_html) — this tool only touches contact fields + the business name. Returns { versionId, status: 'completed' | 'in_progress', ...extra }. If status is 'in_progress', poll get_site_status with the returned versionId every 5-10s until isComplete is true. Concurrency: edits on the same businessId MUST be serial.
    ConnectorNo auth
  • Connect or reconnect the user's WhatsApp account directly in the conversation without leaving the agent. Default mode returns a QR code image to scan from WhatsApp > Linked devices; with phone_number it returns a pairing code to type on the phone instead (useful when the QR image cannot be displayed). Then poll account_connection_status until connected. Requires an active trial/subscription and a free WhatsApp slot on the plan; otherwise the result explains the upgrade. Use account_id to re-authenticate an existing disconnected WhatsApp account.
    ConnectorOAuth
  • List chats for WhatsApp, Instagram or Telegram, most recently active first; use it to find a chat_id. LinkedIn requires inbox-specific listing. V2 filters: type, before/after (on the chat's last activity), archived and unread; WhatsApp pages by offset, other providers by cursor. For 'messages received between X and Y' call messaging_list_recent_messages, which also reads the messages.
    ConnectorOAuth
  • Creates a WhatsApp group and adds the given participants. This NOTIFIES everyone you add and cannot be undone if the participant list is wrong, so it is a write operation: the first call (confirm=false) returns a preview of the name + participants without creating anything; set confirm=true to actually create. Resolve numbers first with whatsapp_search_contacts. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
    ConnectorOAuth
  • Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.
    ConnectorNo auth
  • Create a real estate listing for the authenticated agent. Always creates a private DRAFT — it is NOT visible publicly. A city or neighborhood is enough to start; NEVER invent coordinates (fabricated pins are discarded). The response returns an edit-page link with a map: ask the user to open it and drop the pin on the exact property location, and wait for their confirmation before publish_listing — publishing is blocked until a human sets the pin and at least one photo. Requires a CONNECTED account with a verified WhatsApp number — if unsure, call account_status FIRST and, if not connected, share the connect steps it returns instead of attempting to create.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Create a real estate listing for the authenticated agent. Always creates a private DRAFT — it is NOT visible publicly. A city or neighborhood is enough to start; NEVER invent coordinates (fabricated pins are discarded). The response returns an edit-page link with a map: ask the user to open it and drop the pin on the exact property location, and wait for their confirmation before publish_listing — publishing is blocked until a human sets the pin and at least one photo. Requires a CONNECTED account with a verified WhatsApp number — if unsure, call account_status FIRST and, if not connected, share the connect steps it returns instead of attempting to create.
    ConnectorNo auth
  • Create and submit a WhatsApp message template to Meta for approval. Text templates only (header text, body with {{1}} variables, footer) — add buttons in the app. The template is NOT usable until Meta approves it (check with list_templates). Submitting consumes the store’s Meta template allowance.
    ConnectorNo auth
  • Create and submit a WhatsApp message template to Meta for approval. Text templates only (header text, body with {{1}} variables, footer) — add buttons in the app. The template is NOT usable until Meta approves it (check with list_templates). Submitting consumes the store’s Meta template allowance.
    ConnectorNo auth
  • Send a WhatsApp verification code to the agent's mobile number. Publishing listings requires a verified WhatsApp number — if account_status shows can_publish=false, use this to start verification. A 6-digit code is delivered to the number over WhatsApp; then call verify_whatsapp_code with it.
    ConnectorNo auth
  • Generate a ready-to-send WhatsApp message for one of the authenticated agent's OWN listings: a polished, WhatsApp-tuned caption + a one-tap wa.me link (optionally pre-addressed to a client phone) + the property's main photo to attach. Use whenever the agent wants to send, share, or forward a listing to a client (or to their WhatsApp status). Pass listing_id (from my_listings); optionally client_phone to pre-address the chat. After calling, you can personalize the message for a specific client and rebuild the wa.me link yourself (URL-encode the new text into https://wa.me/<number>?text=...).
    ConnectorNo auth
  • Send a WhatsApp verification code to the agent's mobile number. Publishing listings requires a verified WhatsApp number — if account_status shows can_publish=false, use this to start verification. A 6-digit code is delivered to the number over WhatsApp; then call verify_whatsapp_code with it.
    ConnectorNo auth
  • Generate a ready-to-send WhatsApp message for one of the authenticated agent's OWN listings: a polished, WhatsApp-tuned caption + a one-tap wa.me link (optionally pre-addressed to a client phone) + the property's main photo to attach. Use whenever the agent wants to send, share, or forward a listing to a client (or to their WhatsApp status). Pass listing_id (from my_listings); optionally client_phone to pre-address the chat. After calling, you can personalize the message for a specific client and rebuild the wa.me link yourself (URL-encode the new text into https://wa.me/<number>?text=...).
    ConnectorNo auth
  • Create a contact manually — for imports or externally-sourced audiences; contacts who message a bot are created automatically. Requires the manage_broadcasts permission. platformId must be unique within the bot (duplicate fails with 409); botId may be omitted only when the application has exactly one bot. The variables map takes variable NAMES (or full folder paths when a name is ambiguous) — not ids — and unknown names fail with 422. NOT idempotent: retrying a success creates nothing new only because the duplicate platformId is rejected.
    ConnectorNo auth
  • Returns the Control Plane operating guide — the resource model, how secrets/images/workloads/domains fit together, production-grade defaults, how to verify a change landed, and how to handle failures. Read it once per session before the first create/update/delete, and any time a multi-resource task spans unfamiliar ground.
    ConnectorOAuth
  • Company facts for Jenesis Travel: licence, contact, WhatsApp, enquiry-led model. Call this first. If the user wants a real person, share the WhatsApp URL.
    ConnectorNo auth
  • Read call history across your WhatsApp accounts, oldest first. Page with after_cursor: pass back the next_cursor you were given, and keep going until has_more is false to export the whole history. Each call says whether it was answered and how long it lasted.
    ConnectorOAuth
  • WhatsApp health check (wacli doctor): which account is linked (number), last sync time, store lock, message/chat counts, a `link_state` verdict — not_linked (the user must scan a QR) · linked_idle (linked, no socket open right now; wacli reconnects on demand, nothing to do) · linked_live — and `sync_running` / `sync_started_at` / `sync_last_completed_at` / `sync_last_result` for the background job whatsapp_sync starts (#1453). Read `link_state` and `requires_user_action`, NOT `connected`: a linked session spends most of its time with `connected: false`, which on its own says nothing about whether sends work — a session WhatsApp refuses by version looks identical. Treating it as an outage tells the user to re-link a healthy link (#2138). ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
    ConnectorOAuth
  • Reads WhatsApp poll results. With poll_id: that poll's question, options and vote counts; without it: recent polls in the chat. chat_id MUST come from whatsapp_list_chats / whatsapp_list_groups. IMPORTANT — the counts are INDICATIVE, not definitive: WhatsApp poll votes are end-to-end encrypted and a vote can be silently missing if this device was unlinked when it arrived. The response includes a completeness_caveat and, for group polls, the group's participant count as the denominator. NEVER report a poll result as final without the caveat — verify the firm tally in the WhatsApp app. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
    ConnectorOAuth
  • Sends a file attachment to a WhatsApp chat. The chat_id MUST come from a previous whatsapp_list_chats call — never fabricate IDs. file_path must be an absolute path to a local file. This is a write operation: the first call (confirm=false) returns a preview without sending; set confirm=true to actually send. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
    ConnectorOAuth
  • Sends a text message to a WhatsApp chat. The chat_id MUST come from a previous whatsapp_list_chats call — never fabricate IDs. This is a write operation: the first call (confirm=false) returns a preview without sending; set confirm=true to actually send. ⚠️ Uses Wacli (unofficial WhatsApp client). Accounts may be restricted for ToS violations.
    ConnectorOAuth