Build It With Claude

Fill in the <…> parts and paste this into Claude (or any capable AI assistant). It will generate the full connector — script, n8n workflow, or webhook handler — for your system.

I want to connect my customer system to Whatbot (a WhatsApp Business platform)
so that my contacts/leads automatically sync into Whatbot's shared inbox.

Whatbot exposes a REST API:
- Auth: send the header  X-API-Key: <MY_WHATBOT_API_KEY>
- Upsert contacts:  POST https://api.whatbot.in/public/v1/contacts
  Body is a JSON ARRAY of contacts:
  [
    { "phone": "9876543210", "name": "Ravi",
      "tags": ["gold"], "opt_in": true,
      "attributes": { "city": "Chennai", "budget": "15L" } }
  ]
- Contacts upsert by phone (re-sending the same phone updates it).
- "phone" is required; any keys under "attributes" become custom fields
  usable as {{variables}} in WhatsApp templates.

My system is: <DESCRIBE IT — e.g. a Postgres "leads" table / a HubSpot CRM /
a Google Sheet / a Node backend>.

Please write <a script / an n8n workflow / a webhook handler> in <MY STACK,
e.g. Node.js or Python> that, whenever a contact is created or updated in my
system, pushes it to Whatbot via that endpoint. Handle: normalizing phone to
E.164, batching multiple contacts per request, retrying on 5xx/429, and
mapping my fields (name, email, city, …) into Whatbot's name + attributes.
Give me the full code and exactly how to run/deploy it.

Once it generates the connector, drop in your real API key and run it — your contacts start flowing into whatbot, under Contacts.

Or connect Claude to your workspace (MCP)

Whatbot also runs a hosted MCP server, so Claude — or any tool that speaks the Model Context Protocol — can work with your WhatsApp conversations directly. There is nothing to install or host.

An admin opens Settings → Connect an AI assistant (MCP).
Create an API key under Settings → API Keys (copy it straight away — it is shown only once).
Pick your tool on the MCP page — Claude Code, Claude Desktop, an editor, or any CLI tool — and copy the ready-made config into it, with your key in place of the placeholder. The page shows the server address (it ends in /v1/mcp/sse); the key goes in the X-API-Key header, or as Authorization: Bearer <key>.

The assistant gets six tools:

Tool	What it does
`list_conversations`	The most recently active conversations, optionally only open or closed ones
`get_messages`	The latest messages of one conversation (up to 100)
`get_contact_activity`	One contact’s summary by phone number: conversations, tags, attributes, flows, forms, broadcasts — no message text
`search_messages`	Find messages containing a phrase across all conversations (an exact-text match, not a fuzzy one)
`send_message`	Send text, a file or an approved template — sends a real message
`schedule_message`	Send an approved template at a future time — sends a real message