Search Your WhatsApp History with Claude: Find What Someone Told You (2026)
Someone sent you the address last month, but not in the chat you checked. Ask Claude to search your WhatsApp history by keyword, date and sender, then tell you which chat it came from.
Daniel Roth6 min read
On this page
Someone sent you the address last month. Or the price, or the day the appointment moved. It was in one of your WhatsApp chats, but WhatsApp's search only helps once you remember which chat it was in.
Ask Claude instead. With the Blueticks WhatsApp connector, Claude can search your message history by keyword, date range and sender, across every chat or inside one chat you name. The search only reads. It tells you which chat the message came from and when, so you can open that chat and check.
How does Claude search your messages?
Claude calls the chats tool with the list_messages action. If no chat is named, the search covers all your chats. If you name one chat, or up to 25 chats in one call, it covers only those.
| Filter | What it does |
|---|---|
query_any | Up to 24 keywords. A message matches if any one appears in its text, caption or filename |
since and until | A date range in ISO 8601; an offset is allowed |
sender | A case-insensitive piece of the sender's phone number or ID |
message_types | Kinds of message, for example ["document"] or ["image"] |
limit | Up to 200 messages per chat |
You never type these. You describe the message in plain words and Claude picks the filters. list_messages is a read action, so the search does not send, react or mark anything as read. Claude gets today's date from the utils tool first, so "last month" becomes real timestamps.
What do you need before you start?
A linked WhatsApp number in Blueticks and the connector added to Claude. The connector URL is https://api.blueticks.co/mcp, and you sign in with OAuth, so no key is pasted into Claude. If you have not set that up, how to connect WhatsApp to Claude covers it.
A message search uses two tools: utils for the date and chats for the search. The full list is in the WhatsApp MCP tools guide.
Plan limits apply. The free plan allows 5 requests per fixed 6-hour window (UTC), shared across your API keys and the connector. Each tool call is one request, so a search that takes three calls uses three of your five.
The prompt: find an address across all chats
Paste this into a normal Claude chat and change the keywords and the person:
Using Blueticks, search all my WhatsApp chats for the delivery address someone sent me in the last 60 days. Get today's date first. Look for messages that mention "address", "deliver" or "ship" in the text, caption or filename. Only use read actions. For each match give me the chat name (or its ID if there is no name), who sent it, the date and time, and the sentence where the address appears. Tell me the date of the oldest message you scanned and whether the search was truncated. If you find nothing, say so and do not guess. Do not send, react, archive or mark anything as read.
Behind it, Claude makes about three steps: it reads the date, runs one list_messages search with your words in query_any and since set to the start of the window, then reads the rows and the coverage note and reports back.
A sample answer, with every name and number invented for illustration:
Found 2 matches (invented example)
- Chat "Garden Renovation" (invented), 3 Oct, from +1 555 0100 (invented number)
- Chat "Dana" (invented), 19 Oct, from Dana (invented)
The oldest message scanned is from 27 Aug. The search was not truncated.
Each match names its chat, sender and date, so you know exactly where to look.
Search one chat instead
When you remember the chat, name it. Claude can look the chat up by name first, then search only that chat. Archived chats are left out of chat lookups by default, so say so in the prompt if the chat is archived.
How do you read a "not found"?
A search that reaches your engine returns a coverage note. If the engine is offline there may be none. It shows how many messages were scanned (messagesScanned), whether the scan was cut short (truncated), whether only WhatsApp's search index was checked (indexOnly), and how far back the scan reached (oldestScannedIso). Read these before you accept a miss.
truncated: true. The scan hit its cap, so more matches may exist. Narrow the date range or name the chat, then ask again.indexOnly: true. Only the search index was checked, and captions and filenames were not scanned. A miss here proves nothing.- The oldest scanned date is newer than your range. A search across all chats does not load older history, so it cannot see the older window. The miss says nothing about it.
- The oldest scanned date reaches your range, with no flags. The messages your engine holds for that range were scanned, and none matched. A filtered search does not read the stored backup copy, so a message that exists only there is not searched.
When you name one chat and give a start date, and the first read finds nothing, the connector pages back through older history for that chat, up to 5 pages within about 25 seconds, before it answers. If that loading stops before your start date, the coverage date stays newer than your range, and the answer should say so.
What can go wrong?
- Your engine is offline. A filtered search always skips the stored backup copy, even when the engine is online. If the engine is down, the search can return an empty result that looks like a miss. Ask Claude to check the engine status, reconnect if needed, and search again.
- The sender filter matches numbers, not names. It looks at the sender's phone number or ID. If her contact name is saved only on your phone, search for part of her number instead.
- Common words. "Address" shows up in many messages. Add a date range, a chat name or a second keyword.
- Claude can misread or miss messages. Treat the answer as a pointer, not a verified fact. Before you act on an address, an amount or a date, open the original chat and check the message yourself.
Is it safe to let Claude search your chats?
Searching reads, but the same chats tool also includes actions that send, react, mark as read and archive. You decide what runs. Approve each tool call yourself, read the action name before you click, and do not choose "Allow always." A list_messages call reads. A send_message_text call sends.
Run the search in a normal chat, not in Research. In Research, Claude can call connector tools without asking each time. Treat "Allow always" as something to avoid for a connector that can send, and read Anthropic's custom connector guide for how connector permissions work.
The line "do not send, react, archive or mark anything as read" in the prompt is a request to Claude, not a lock. Your approval is the lock.
Message history is private. Whatever Claude reads in a search is shared with Claude in that conversation, so keep sensitive searches to chats you are comfortable having there.
Related guides
To find documents and photos by filename, type and sender, see how to find any file someone sent you on WhatsApp with Claude. For a summary of the groups you did not read, see the WhatsApp group digest. Plans are on the pricing page.
Frequently asked questions
Can Claude search all my WhatsApp chats at once? Yes. A search with no chat named covers all your chats. You can also name up to 25 chats in one call.
Can I search by a contact's name? The sender filter matches the phone number or ID, not the name saved on your phone. Use part of the number, or search by keyword and date.
What if Claude says nothing was found? Check the coverage note. If the search was truncated, index-only, or the oldest scanned message is newer than your date range, the miss is not final. Name the chat and try again.
