SendSeven Messaging

List messaging campaigns (WhatsApp, Telegram, SMS, browser push) with their status and delivery counts. For EMAIL campaigns use list_email_campaigns. Note: "total" in the response reflects only the number of campaigns returned in this call (bounded by "limit"), NOT the true total number of matching campaigns on the server — the server does not report an overall count. If "total" equals your requested "limit", there may be more campaigns you aren't seeing; narrow with "status" to check. Examples: - "Show me our campaigns" - "Which campaigns are still sending?" → status="sending" - "List draft…

List all connected messaging channels (WhatsApp, Telegram, Email, etc.) with their health status. Shows which channels are active and if any have issues. Health monitoring currently only covers email, messenger, and instagram channels. WhatsApp, Telegram, SMS, live chat, and RCS channels report health="not_monitored" — that means no connection-error monitoring exists for them yet, NOT that something is wrong. Only trust the health field for the three monitored types. Examples: - "Which channels are active?" - "Is our WhatsApp integration working?" - "Show me the channel health status"

List all contact lists and newsletter lists. Shows list name, type (static/dynamic/newsletter), subscriber count, and ID. Use the list IDs when creating campaigns to target specific audiences. Examples: - "Show me all our lists" - "Which newsletter lists do we have?" - "How many subscribers are in the VIP list?"

List and filter customer conversations. Use this to check open conversations, find conversations needing attention, or search for specific conversations. Examples: - "Show my open conversations" → status="open", assigned_to="me" - "Any conversations needing reply?" → needs_reply=true - "Find conversation about refund" → search="refund" - "Snoozed WhatsApp conversations" → status="snoozed", channel_type="whatsapp"

List email campaigns with their status, subject line, and delivery statistics. Shows draft, scheduled, sending, and completed email campaigns. Examples: - "Show me our email campaigns" - "What email campaigns have been sent?" - "List all draft email campaigns"

List email mailboxes (sender identities) configured for your account. Each mailbox has an email address and display name used as the 'From' field when sending emails. Use the mailbox ID with the send_email tool's mailbox_id parameter to send from a specific mailbox. Examples: - "What email addresses can I send from?" - "Show me our configured mailboxes" - "Which mailbox is the default?"

List the knowledge base's folder structure (a tree of folders, e.g. "General", "Websites", "Ticket Summaries", and any custom folders). Each folder shows its document count and id — use a folder's id as the folder_id parameter on query_knowledge_base to search within just that folder. Examples: - "What folders are in our knowledge base?" - "How many documents are in the Product Documentation folder?"

List all tags in your workspace. Tags are color-coded labels you can apply to conversations and contacts for organization and filtering. Examples: - "Show all tags" → list_tags() - "Search for VIP tag" → search="VIP"

List SendSeven Team Chat channels, for discovering a valid channel_ref before calling send_team_chat_channel_message. Read-only - requires team_chat:read (a separate scope from the teamchat:write bot-messaging tools). Two modes: - Default (include_browsable omitted or false): channels the connected user has already joined. - include_browsable=true: channels that exist but the user hasn't joined yet (discoverable/joinable channels). A channel doesn't need to be "joined" for send_team_chat_channel_message to work - only allow_bots=true and not archived matter - so this mode is useful for findin…

List all team members in your workspace. Returns user IDs, names, emails, and roles. Use this to find agent IDs for assign_conversation. Examples: - "Who's on the team?" → list_team_members() - "Find the support agents" → list_team_members()

List email sender domains that are verified with your email provider(s). A send_email using a "from_email"/mailbox whose domain is NOT in this list will typically fail to send or be marked unauthenticated by the recipient's mail server. Use this before send_email if you're unsure whether a given from address will work. Examples: - "Which domains can we send email from?" - "Is example.com verified for sending?" - "Why did my email send fail — is the domain verified?"

List configured webhook endpoints with their subscribed events, health status, and recent failures. Examples: - "Show my webhooks" - "Is my n8n webhook still working?"

List approved WhatsApp message templates. Use these templates to send messages to contacts outside the 24-hour messaging window. Shows template name, language, status, and content, including buttons, header type/media, and whether it's a carousel template. Use get_whatsapp_template for a single template's full detail (e.g. carousel cards). Note: "total" is the true total count of matching templates on the server (not just the count returned on this page) — use offset to page through when total exceeds the returned count. Examples: - "Show me our WhatsApp templates" - "What templates do we ha…

Search the knowledge base using AI. Queries across FAQ documents, website content, uploaded files, and past ticket summaries. Returns an AI-generated answer with source citations. Examples: - "What's our refund policy?" → query="refund policy" - "How do I set up WhatsApp integration?" → query="WhatsApp integration setup" - "What are our business hours?" → query="business hours"

Reopen a closed conversation, returning it to the Open tab.

Search contacts by name, phone number, or email, and/or filter by tag membership. Returns matching contacts with their available channels, tags, and full contact_methods list (each with its own id, type, value, and is_primary flag). `query` is free-text over name/email/phone/contact-id only — it does NOT match by tag name. To find contacts carrying a specific tag, use `tag_id` instead: call list_tags first to get the tag's id, then pass that id here. If both `query` and `tag_id` are given, the text search applies within the set of contacts carrying the tag(s); multiple tag_ids match contacts …

Send an email to a contact. Finds the contact by email address or name, resolves the email channel, and sends with proper email fields (subject, body, CC, BCC). This is the ONLY tool for sending emails. Do NOT use send_message_to_contact for email — it lacks email-specific fields like subject lines. The body supports HTML formatting. For plain text emails, the text will be sent as-is (wrapped in basic HTML). You can optionally specify a custom sender address (from_email) and display name (from_name). The from_email must belong to a verified domain configured in SendSeven — use list_verified…

Send a message to a contact on the best available channel (WhatsApp, Telegram, SMS, Messenger, Instagram). Finds the contact by phone number or name. If no open conversation exists, one is created automatically. For sending EMAILS, use the send_email tool instead — it supports subject lines, HTML body, CC/BCC. Attachments (images, video, audio, documents): pass the attachments array. Each entry is EITHER {"id": "<attachment-id>"} for a file already uploaded to SendSeven, OR {"url": "https://...", "filename": "photo.jpg"} for a public URL that SendSeven downloads server-side. On WhatsApp/Tele…

Reply to an existing conversation. Use this when you already have a conversation_id (e.g., from list_conversations or get_conversation). Much simpler than send_message_to_contact — just provide the conversation ID and your reply text. Attachments (images, video, audio, documents): pass the attachments array. Each entry is EITHER {"id": "<attachment-id>"} (already uploaded) OR {"url": "https://...", "filename": "photo.jpg"} (public URL, downloaded server-side). Works on both chat channels and email replies. Examples: - After viewing a conversation: "Reply saying we'll process their refund" - …

Post a message to a SendSeven Team Chat channel as a bot. The channel must have "Allow Bots to send messages" enabled in its Team Chat settings; archived channels always reject bot messages, and the AI Knowledge Base channel (#knowledgebase) permanently rejects them too (allow_bots is forced off there). Other system channels like #general/#shoutbox default to allowing bots and behave like any other channel. Bot messages always render with a bot avatar. Attachments: provide EITHER attachment_ids (previously uploaded) OR attachments (public URLs, downloaded server-side) - both forms are accepte…

Send a SendSeven Team Chat direct message to a user as a bot. Always allowed once authenticated - unlike channel messages, there is no "Allow Bots" setting or archived-channel restriction for DMs. Bot messages always render with a bot avatar. Attachments: provide EITHER attachment_ids (previously uploaded) OR attachments (public URLs, downloaded server-side) - both forms are accepted and may be combined. Example: "DM user U123: Your report is ready" -> user_id="U123", text="Your report is ready"

Send an approved WhatsApp template message. Templates are required to reach contacts OUTSIDE the 24-hour messaging window. Use list_whatsapp_templates to see available templates and their variables. Identify the recipient with ANY ONE of: - contact_id — a SendSeven contact - contact_method_id — a specific WhatsApp contact-method UUID (whatsapp_id or whatsapp_bsuid). Highest priority: if given with contact_id, this wins. - whatsapp_id — sent directly: a phone number (leading '+' is stripped), an alphanumeric WhatsApp id, OR a Business-Scoped User ID like "US.13491208655302741918" (kept verbati…

Switch the connected user's OWN out of office on (or schedule it), optionally handing their conversations to a substitute. While absent, new conversations of the user's contacts and their assigned conversations that get a new customer message move to the substitute. Acts only on the user who connected this server. substitute_mode: "none" (default), "user" (needs substitute_user_id from list_team_members), "round_robin_inbox" / "least_busy_inbox" (needs substitute_inbox_id), "round_robin_tag" / "least_busy_tag" (needs substitute_tag_id). Examples: - "I'm out of office until Monday, Anna cover…

Snooze (postpone) a conversation until a given time, or clear an active snooze. Snoozed conversations stay open but move off the Open tab until the snooze expires. Examples: - "Snooze this until tomorrow 9am" → snooze_until="2026-07-18T09:00:00Z" - "Unsnooze the conversation" → unsnooze=true

Add a tag to a contact. Use list_tags first to find available tag IDs.

Add a tag to a conversation. Use list_tags first to find available tag IDs.

Remove a tag from a contact.

Remove a tag from a conversation.

Update an existing contact. Only the fields you provide are changed. Use search_contacts first to find the contact ID. Examples: - "Update Lisa's phone number to +49 170 9999999" - "Set the contact's email to new@example.com" - "The contact speaks German and English" → languages="de,en" - "Make Anna the owner of this contact" → owner_user_id=<Anna's id from list_team_members> - "Remove the contact owner" → owner_user_id=null

Upload a file from a public URL so it can be reused as an attachment across multiple sends. Returns an attachment id you can pass as {"id": "..."} to send_reply, send_email, or send_message_to_contact's attachments parameter, instead of passing the URL each time. Note: if the same URL was already uploaded for this tenant, the existing attachment is returned instead of creating a duplicate. There is no way to list previously-uploaded attachments — save the returned id if you'll need it again. Examples: - "Upload this PDF so I can attach it to several replies" → url="https://.../invoice.pdf" …