Claude LetsBot connectorWhat Claude can do in your LetsBot account.
The Claude LetsBot connector exposes 58 tools. 24 read your WhatsApp data, 31 send or change something, 3 are undocumented. Here: what Claude can read, what it can send to your customers, what it asks first, and why the tool count differs between sources.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your WhatsApp inbox
LetsBot is a platform for running a WhatsApp Business line: conversations, contacts, labels, an auto-reply bot and bulk campaigns. With the connector, you handle that inbox from a conversation with Claude. It reads chats, drafts and sends answers, sorts contacts and builds reports, all on your own LetsBot data.
Clear the queue faster. get_my_chats and get_messages show what waits for you, ai_suggest_reply drafts an answer, and send_text_message or send_template delivers it once you agree.
Keep the base tidy. get_contact, update_contact and assign_label let Claude complete a profile and tag it, so the next campaign hits the right people.
Run campaigns and the bot from the chat. create_campaign targets a label, get_campaign_status shows who received what, and update_bot_conversation fixes an outdated auto-reply.
What it does not do matters too. Outside the 24-hour window after a customer's last message, only a template approved by Meta can go out. Orders and catalogue lookups cover Salla and Zid stores only. Nothing runs on its own: the auto-reply bot is LetsBot's, and Claude only acts while it answers you. And with 31 tools able to send or change things, the approval rule below is worth reading. The Integrations hub lists the rest of the family.
The vocabulary in one minute
Five words you will run into when plugging LetsBot in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks what it needs on its own; the directory lists each tool by name.
- Authorization
- LetsBot's own sign-in screen, where you hand Claude the access it will use. Granted once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown in the chat at that moment.
- MCP
- The open standard connectors rely on: it is what lets an assistant like Claude talk to an outside service such as LetsBot.
Connect LetsBot to Claude in three steps
- 01
Find LetsBot in Claude
Open Customize, then Connectors, and look for LetsBot. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization before members can each connect.
- 02
Start the connection
Click Connect on its row, then sign in with your LetsBot account in the window LetsBot opens. If the link breaks one day, use Disconnect and connect again.
- 03
Read the authorization screen
Check the authorization screen before you accept. It belongs to LetsBot, not to Claude, and it sets what the access covers. You can also remove that access later from your LetsBot account.
The 58 tools, sorted by what they do
LetsBot gives Claude 58 tools: 24 that read your account, 31 that change something in it, and 3 no official source describes.
Three groups: what Claude reads, what it sends or changes, and what no official source describes. Names stay in English, as Claude shows them.
- 24 read
- 31 write
- 3 not documented
What Claude reads (24)
24 toolsTwenty-four tools that look at chats, contacts, orders, campaigns and settings, or produce an analysis, without changing your account.
get_contacts
Pages through your LetsBot contacts, with search and filters to narrow the list. Claude can work through a long list a page at a time instead of loading everything at once.
get_contact
Opens the full profile of one contact: details, labels and the last message exchanged. That gives Claude the background of a customer before it drafts anything for them.
get_my_chats
Lists the conversations assigned to the current agent, the person connected. Conversations assigned to colleagues stay out of this view.
get_messages
Reads the messages of one conversation so Claude can go through the exchange. Without it, Claude would only know what you tell it about the exchange.
search_messages
Looks for words across all chats or within a single one. Claude can scan the whole account for a word or phrase, or stay inside one thread when you already know where to look.
get_labels
Lists every label or tag defined in the account, every tag your team has set up, not only the ones in use.
get_label_contacts
Returns the contacts carrying a specific label. It turns a tag into an actual list of people.
get_moderators
Shows the moderators, meaning the agents available on the account, as LetsBot names them.
get_quick_replies
Retrieves the canned replies already saved in the account, the pre-built answers your agents share.
ai_suggest_reply
Drafts a suggested answer for the current conversation, as a proposal for you to read.
ai_summarize_conversation
Condenses a full conversation history into a summary. Claude gets the gist of a long exchange in a few lines.
ai_analyze_contact
Analyzes a contact and the patterns in their conversations, and hands the analysis back to you in the chat.
ai_improve_message
Polishes a draft so it reads better before it goes out, and returns the reworked text to you.
ai_translate_message
Translates a message into the language you need, whichever language that is, and returns the translated text to you.
ai_sentiment_analysis
Scores customer sentiment as positive, negative or neutral, and returns that score to you in the conversation.
ai_dashboard_summary
Produces a one-shot summary of your dashboard. Claude gets the headline figures of the account in a single call.
get_order_status
Fetches the status and details of an order from a Salla or Zid store. Claude can then answer a delivery question with the order's real state instead of a guess.
search_products
Searches the product catalogue of a Salla or Zid store connected to LetsBot.
get_campaigns
Lists your campaigns with their delivery statistics. Each campaign comes back with its own delivery figures, one line per campaign.
get_campaign_status
Breaks down delivery contact by contact for one campaign. It shows, person by person, whether a campaign message reached its recipient or not.
get_bot_status
Shows the state of the bot, its AI mode and its matching settings, in one read-only view.
get_bot_conversations
Lists all the auto-reply conversations configured in the bot. Claude sees every rule at once.
get_bot_settings
Reads every bot and AI setting of the account. Claude reads the whole configuration in one go.
get_ad_lead_settings
Reads how leads coming from ads are captured. It shows the current capture configuration.
What Claude sends or changes (31)
31 toolsThirty-one tools that message customers or edit your account. No source describes a confirmation for any of them, so the general rule below applies.
send_text_message
Approval: see the ruleSends a plain-text WhatsApp message to a contact from your LetsBot number, written in the conversation with Claude.
send_image
Approval: see the ruleDelivers a picture to a contact on WhatsApp, with a caption if you want one under it.
send_video
Approval: see the ruleShares a video clip with a contact, optionally with a caption explaining what it shows.
send_audio
Approval: see the rulePushes an audio file or a voice note into a contact's WhatsApp chat.
send_file
Approval: see the ruleGets a document or a PDF to a contact, such as a quote, a menu or an invoice.
send_location
Approval: see the ruleDrops a map pin with a location into a contact's conversation.
send_contact_card
Approval: see the ruleShares a contact card in vCard format.
send_template
Approval: see the ruleSends a template message that Meta has approved. LetsBot documents it for writing outside the 24-hour window.
send_buttons
Approval: see the rulePosts an interactive message with up to 3 buttons the contact can tap instead of typing.
send_list
Approval: see the rulePresents an interactive list or menu the contact picks from, handy when there are more choices than buttons allow.
reply_to_message
Approval: see the ruleAnswers one specific message in a thread, quoting it so the contact sees exactly what you are responding to.
send_reaction
Approval: see the rulePuts an emoji reaction on a message, a light way to acknowledge it without writing anything.
forward_message
Approval: see the rulePasses a message from one chat on to another conversation.
create_contact
Approval: see the ruleAdds a new contact to your LetsBot account.
update_contact
Approval: see the ruleEdits a contact's information, for instance the name or the email address.
pin_contact
Approval: see the rulePins a conversation to the top of the list, or unpins it.
archive_contact
Approval: see the ruleArchives a conversation, or brings an archived one back.
block_contact
Approval: see the ruleBlocks a contact, or unblocks one.
assign_label
Approval: see the ruleToggles a label on a contact: it adds the label if missing and takes it off if present.
assign_moderator
Approval: see the ruleToggles a moderator on a contact, assigning or unassigning a team member to that conversation. It is the hand-off between agents.
mark_as_read
Approval: see the ruleMarks every message in a chat as read.
create_label
Approval: see the rulePuts a new label into the account.
create_quick_reply
Approval: see the ruleSaves a new canned reply template for the team.
update_quick_reply
Approval: see the ruleRewrites an existing canned reply.
create_campaign
Approval: see the ruleSets up a bulk message campaign aimed at the contacts carrying a label.
toggle_bot
Approval: see the ruleSwitches the bot on or off for one contact. The rest of your contacts keep the bot as before.
create_simple_conversation
Approval: see the ruleAdds a simple auto-reply rule to the bot: a keyword and the text it answers with.
create_interactive_conversation
Approval: see the ruleBuilds an interactive conversation tree for the bot, with buttons leading to the next step.
update_bot_conversation
Approval: see the ruleEdits an existing auto-reply conversation.
update_bot_settings
Approval: see the ruleAdjusts some of the bot or AI settings, leaving the others as they are.
update_ad_lead_settings
Approval: see the ruleEdits the ad-lead capture settings, the counterpart of the reading tool for the same configuration.
Undocumented (3)
3 toolsThe directory lists these three names, but LetsBot's own catalogue leaves them out. Nothing official says what they do, and this page will not guess.
get_unread_contacts
This name is in the directory's tool list, but LetsBot's public tool catalogue does not include it and no other source describes it. This page therefore says nothing about what it does.
The general approval rule below applies to it as well.
ai_employee_performance
Listed in the directory, this name is missing from LetsBot's public catalogue, and no source documents it. The page stays silent on what it covers.
If Claude calls it, the default approval rule still applies.
The directory sheet is the only place this name appears; LetsBot's catalogue page, which lists its tools one by one, does not mention it.
ai_team_report
Nothing official describes this tool: the directory publishes the name only, and LetsBot's own catalogue leaves it out. No capability is claimed for it here. Treat it as unknown.
The general approval rule covers it like any other tool.
The directory sheet is the only place this name appears; LetsBot's catalogue page does not include it in its list.
What Claude asks before it acts
By default, Claude stops and asks before any action it takes on an account for you. With LetsBot that matters a lot: 31 tools can message a customer or change your settings.
On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked every time. They can also bound what a connector may do for the whole organization, for instance keep reading open and close everything that sends, and nobody overrides that from a personal account. Claude works with your LetsBot access and nothing more; LetsBot's sheet says you only ever see your own data. The official read-only versus write labels per tool live only in a connected account's settings.
Which plans it is on
Of the 819 sheets in the official directory, none displays availability per plan. Connector by connector, that answer is not published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can connect. That rule concerns Claude; LetsBot has its own subscription condition, covered in the tip above. For the current state, check the connector's sheet in the official directory from your account.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: an incoming message does not wake Claude up, even if LetsBot's own bot answers it.
The tool list is an observed floor, not a ceiling: an administrator could open more than any public page shows. The partner badge in the directory is not a security audit, and Anthropic writes on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as announced. Only LetsBot documents this connector; Claude's help center has no page on it, and even LetsBot's own tool count differs from the sheet, as shown below.
How many tools does LetsBot expose?
- Claude directory sheet ↗October 202658 named tools.
- LetsBot WhatsApp MCP page ↗undatedA larger catalogue that the publisher says grows weekly, with a few extra publishing tools only in workspaces where that feature is on.
What this page followsThe two lists do not match: LetsBot's page carries tools the sheet does not, and the sheet carries 3 names the page never describes. The page has no date and says the catalogue moves every week, so the list Claude shows in your own account is the one that counts.
Need help connecting LetsBot to Claude?
A person reads every message.
