Integration

Richpanel integration

Richpanel is a customer service helpdesk for e-commerce brands. Create, read and update conversations (tickets), reply to customers, add private notes, assign agents and tags, find conversations and customer profiles by email or phone, sync customers, orders and subscriptions from your store, manage tasks and their comments, list users, teams, tags and channels, and query helpdesk analytics. Not exposed: file upload (its response is undocumented) and the separate GraphQL Returns API. Authentication is an API key from Settings, Integrations, API Keys, sent in the x-richpanel-key header. Rate limit: 50 requests per 30 seconds.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Richpanel

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

  • assign_conversationAssign conversationPOSTAssign a conversation to an agent: assignee is the user id (from list_users).
  • create_conversationCreate conversationPOSTCreate a conversation (ticket) with its first message. Required: status, channel, comment_body, comment_sender_type, and the sender and recipient (from_/to_address for email, from_/to_id otherwise).
  • get_conversationGet conversationGETGet a conversation by id: status, priority, subject, assignee, channel, tags, messages (comments) and its inbox URL.
  • get_conversation_by_numberGet conversation by numberGETGet a conversation by its ticket number (conversation_no), with messages. Limited availability: may not work for conversations imported from other systems.
  • list_customer_conversationsList customer conversationsGETList the conversations of a customer by email or phone: set type to email or phone and id to the value. Returns each conversation id, assignee and customer name.
  • update_conversationUpdate conversationPUTUpdate a conversation: close or reopen, change priority or assignee, or add a message or private note. Send only the fields to change.

Task, 5 operations

  • create_taskCreate taskPOSTCreate a task linked to a conversation (conversation_id and title required), optionally assigned with a due date and priority. Returns the task with its task_id.
  • delete_taskDelete taskDELETEDelete a task (a soft delete). Returns success and a message.
  • get_taskGet taskGETGet one task by its task_id: title, description, status, priority, assignee, due date and comment count.
  • list_tasksList tasksGETList tasks with filters (status, priority, assignee, conversation, due dates, search), sorting and pagination. Page through with page while pagination.has_next is true.
  • update_taskUpdate taskPATCHUpdate a task: send only the fields to change (title, description, assignee, due_date, priority, status). Returns the updated task.

Channel, 2 operations

  • get_channelGet channelGETGet one connected channel by id (from list_channels): its type, brand name and timestamps.
  • list_channelsList channelsGETList the channels connected to the Richpanel workspace (email, chat, social, phone), each with id, type and brand name. No parameters.

Conversation order, 2 operations

  • attach_order_to_conversationAttach order to conversationPUTLink a store order to a conversation, by the store app client id and the order id.
  • get_conversation_orderGet conversation orderGETGet which order is linked to a conversation: returns orderId and appClientId, which get_order takes.

Conversation tag, 2 operations

  • add_conversation_tagsAdd conversation tagsPUTAdd tags to a conversation by tag id (from list_tags; ids, not names). Duplicates are ignored; at least one valid tag is required.
  • remove_conversation_tagsRemove conversation tagsPUTRemove tags from a conversation by tag id (from list_tags). Removing a tag the conversation does not carry does nothing.

Customer, 2 operations

  • search_customersSearch customersGETFind customer profiles by email or phone: set type to email or phone and id to the value. Returns the matching profiles (name, email, location, counts).
  • upsert_customerUpsert customerPOSTCreate a customer profile, or update it when one with the same uid exists (upsert). appClientId is required; send only the fields you have. Returns the profile id.

Order, 2 operations

  • get_orderGet orderGETGet an order of a store by its order id: amounts, payment status, line items, fulfilments with tracking, billing and shipping address.
  • upsert_ordersUpsert ordersPOSTCreate or update orders for a store (upsert). Pass appclient_id and orders, a list of order events; each needs event "order", properties (orderId, amount, status, items) and user_properties.

Private note, 2 operations

  • delete_private_noteDelete private noteDELETEDelete a private note from a conversation. noteId is the id of the note in the conversation messages (get_conversation with include_private_notes=true).
  • update_private_noteUpdate private notePUTReplace the text (and attachments) of a private note on a conversation.

Tag, 2 operations

  • create_tagCreate tagPOSTCreate a tag. Richpanel lowercases the name and replaces spaces with hyphens. Returns the new tag id.
  • list_tagsList tagsGETList the tags of the workspace, each with id and name. Use the ids (not names) with add_conversation_tags, remove_conversation_tags and create_conversation.

Task comment, 2 operations

  • add_task_commentAdd task commentPOSTAdd a comment to a task. User ids listed in mentions are notified. Returns the comment.
  • list_task_commentsList task commentsGETList the comments and activity entries of a task, paginated. Page through with page while pagination.has_next is true.

User, 2 operations

  • get_userGet userGETGet one user (agent) by id: name, email, role and avatar.
  • list_usersList usersGETList the users (agents) of the workspace, each with id, name, email and role. Use an id as assignee_id when assigning conversations or tasks.

Attachment, 1 operation

  • get_attachment_urlGet attachment urlGETGet a fresh signed download URL for a conversation attachment, valid 7 days. Pass key (object key or any Richpanel URL of the file) plus conversationId or conversationNo.

Conversation message, 1 operation

  • send_conversation_messageSend conversation messagePUTSend an agent message on an existing conversation. body is required; author_id is the sending agent (from list_users); attachments are file URLs.

Conversation task, 1 operation

  • list_conversation_tasksList conversation tasksGETList the tasks linked to a conversation, with a status summary (open, in progress, closed, overdue, due today, due this week) and pagination.

Report, 1 operation

  • query_report_metricsQuery report metricsPOSTQuery helpdesk analytics (volumes, response times, CSAT, agent performance) between two dates, up to 5 metrics, optionally grouped by one dimension. Get names from list_report_metrics.

Report metric, 1 operation

  • list_report_metricsList report metricsGETList the metric names, filter fields and breakdown dimensions query_report_metrics accepts. Static data: call once and reuse.

Subscription, 1 operation

  • upsert_subscriptionsUpsert subscriptionsPOSTCreate or update subscriptions for a store (upsert). Pass appclient_id and subscriptions, a list of subscription events with properties (orderId, status, amount, items, dates) and user_properties.

Team, 1 operation

  • list_teamsList teamsGETList the teams of the workspace, each with id and name. No parameters.

Use Richpanel from Claude Code, Cursor or Codex

Connect Richpanel in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Richpanel 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 Richpanel

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Richpanel once

    Add your Richpanel 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.

Richpanel integration FAQ

What can you do with the Richpanel integration?

LiveContext exposes 36 operations on Richpanel, covering conversation, task, channel and conversation order.

Popular integrations

Browse the whole catalog