Integration

Belco integration

Belco is customer service software for webshops that gathers email, live chat, phone and social messages of each shop in one shared inbox. List, read, create and send conversations, reply, add notes, assign, snooze, tag, close and reopen them, create or sync contacts (customers and leads with orders, cart and company data), merge contacts, read conversation and call metrics, list users, and manage teams and webhook subscriptions. Authentication is a personal access token, found on your profile page in the Belco dashboard, sent as a Bearer token.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Belco.Built from the 39 Belco tools below, on the connection you add once.

What you can do with Belco

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Conversation, 6 operations

  • create_conversationCreate conversationPOSTStarts a conversation in a shop on the chat, email or phone channel: an outbound message, auto message or follow-up to a contact (to), an inbound message on behalf of a customer (from), or a note.
  • delete_conversationDelete conversationDELETEDeletes a conversation.
  • get_conversationGet conversationGETReturns one conversation with its tags, the contact tags and its items (messages, notes, events, call recordings). Filter the items by date range and sort them oldest or newest first.
  • get_conversation_metricsGet conversation metricsGETReturns conversation metrics for a date range: totals (created, closed, responded, inbound, outbound), median response and resolution times, and rows per hour, day or month, optionally grouped by team, shop, channel or assignee.
  • list_contact_conversationsList contact conversationsGETLists the conversations of one contact in a shop.
  • list_conversationsList conversationsGETLists conversations across your shops, 50 per page by default (limit up to 100, skip to page). Each has its channel, type, status, assignee, team, contact and last message.

Webhook, 5 operations

  • create_webhookCreate webhookPOSTSubscribes an HTTPS URL to events of a shop (for example conversation.created, conversation.closed, call.answered). Deliveries are signed (x-hook-signature); the secret is not passed back here.
  • delete_webhookDelete webhookDELETEDeletes a webhook subscription.
  • get_webhookGet webhookGETReturns one webhook subscription with its shop, URL, events and status.
  • list_webhooksList webhooksGETLists your webhook subscriptions with their shop, URL, events and whether they are active.
  • update_webhookUpdate webhookPUTChanges the URL, the events or the active flag of a webhook subscription.

Contact, 4 operations

  • delete_contactDelete contactDELETEDeletes a contact and all its conversation history.
  • get_contactGet contactGETReturns one contact of a shop with its profile, order statistics, shopping cart, tags, company and custom data.
  • list_contactsList contactsGETLists the contacts of a shop, 50 per page by default (limit up to 100, skip to page), filtered by email, phone number or type (customer, lead or contact). nextPage is set when more pages exist.
  • upsert_contactUpsert contactPOSTCreates or updates a contact in a shop, matched on id (or email): name, email, phone numbers, type, order history, shopping cart, tags, company and custom data. Needs at least id or email.

Tag, 3 operations

  • add_conversation_tagsAdd conversation tagsPUTAdds tags to a conversation and returns all tags now on it.
  • get_conversation_tagsGet conversation tagsGETReturns the tags currently on a conversation.
  • remove_conversation_tagsRemove conversation tagsDELETERemoves the given tags from a conversation and returns the tags left on it.

Team, 3 operations

  • create_teamCreate teamPOSTCreates a team. Needs organization admin access; team names must be unique in the organization (case-insensitive).
  • delete_teamDelete teamDELETEDeletes a team.
  • list_teamsList teamsGETLists the teams of your organization with their members.

Account, 1 operation

  • get_accountGet accountGETReturns the authenticated Belco user: id, email addresses, avatar, live status (available, online, on a call, do not disturb), profile (name, language, time zone) and call forwarding settings.

Activate, 1 operation

  • activate_webhookActivate webhookPUTTurns a webhook subscription on.

Add note, 1 operation

  • add_conversation_noteAdd conversation notePUTAdds an internal note (not sent to the customer) to a conversation.

Assign, 1 operation

  • assign_conversationAssign conversationPUTAssigns a conversation to a user (userId) or a team (teamId); ids come from list_users and list_teams.

Close, 1 operation

  • close_conversationClose conversationPUTCloses an open conversation.

Deactivate, 1 operation

  • deactivate_webhookDeactivate webhookPUTTurns a webhook subscription off without deleting it.

Info, 1 operation

  • get_api_infoGet api infoGETReturns the Belco API version and its documentation URL. Needs no credential.

Item, 1 operation

  • list_conversation_itemsList conversation itemsGETReturns every item of a conversation in one list (no pagination): messages, notes and events, each with its type, author reference and body.

Merge, 1 operation

  • merge_contactsMerge contactsPOSTMerges a source contact into the target contactId: the target survives, the source is retired and its conversations move to the target. Repeating a completed merge is safe (alreadyMerged).

Open, 1 operation

  • reopen_conversationReopen conversationPUTReopens a closed conversation.

Remote id, 1 operation

  • set_contact_remote_idSet contact remote idPUTAssigns your external id (remoteId) to an existing lead or customer. Repeating the same assignment is safe; a different existing remoteId or one taken by another contact is refused with a conflict.

Reply, 1 operation

  • reply_to_conversationReply to conversationPUTPosts a reply to the customer in an existing conversation, on the conversation channel.

Send message, 1 operation

  • send_messageSend messagePOSTSends a message in a shop on the chat, email or phone channel, for example an inbound message on behalf of a customer (type inbound-message with from) or an outbound message to a contact (to).

Shop, 1 operation

  • list_shopsList shopsGETLists the shops (Belco workspaces, one per webshop) your account can access, with id, name, currency, platform type and URL. The shop id is the shopId other tools need.

Snooze, 1 operation

  • snooze_conversationSnooze conversationPUTSnoozes a conversation until a given time (a Unix timestamp in seconds).

Unassign, 1 operation

  • unassign_conversationUnassign conversationPUTRemoves the user and team assignment from a conversation.

User, 1 operation

  • list_usersList usersGETLists the users (agents) of your organization with their emails, live status and profile; their id is the userId for assign_conversation.

Voice, 1 operation

  • get_voice_metricsGet voice metricsGETReturns call metrics for a range (today, yesterday, week, month, quarter or custom dates): per time bucket the number of calls, answered, missed, voicemail, abandoned, inbound and outbound counts and durations.

Use Belco from Claude Code, Cursor or Codex

Connect Belco in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Belco operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Belco

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Belco once

    Add your Belco connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Belco integration FAQ

What can you do with the Belco integration?

LiveContext exposes 39 operations on Belco, covering conversation, webhook, contact and tag.

Popular integrations

Browse the whole catalog