Skip to main content

Jumpseller

With the Jumpseller integration, your ChatNorris agent serves your store’s customers with the store’s real data. Depending on what you turn on, the agent:
  • searches products and variants (by name or SKU) and answers the current price and stock;
  • tells the payment and shipping status of an order, only after verifying that it belongs to the visitor;
  • builds the purchase and sends one link per product that adds it to your store’s cart;
  • confirms the payment in the same conversation when the visitor pays;
  • uses your store’s catalog as a knowledge source (descriptions, variants, and links to product pages).
It works in the web widget, WhatsApp, Instagram, Messenger, Telegram, Email, and the API.

Requirements

  • A ChatNorris account on the Standard or Premium plan. You can see the plans at chatnorris.ai/pricing.
  • At least one agent created in ChatNorris. If you don’t have one yet, follow Create an agent.
  • A Jumpseller store and access to its admin to copy the API login and token.
  • The Owner or Admin role in your ChatNorris organization.

Connect the store

Each agent connects to one Jumpseller store.
1

Copy the API login and token

In your Jumpseller store admin, open Account › Preferences. In the API and MCP card, copy the login and, with Show token, the token.
2

Open the agent's Integrations hub

In ChatNorris, go to My agents → [your agent] → Integrations and choose Jumpseller.
3

Paste both keys and connect

Paste the login and the token and click Connect. ChatNorris tests the keys with Jumpseller before saving them: if they don’t work, it tells you why and saves nothing.
The account that owns the token needs the products, orders, hooks, and settings permissions. If you use a dedicated user, check that it has them. Without the hooks permission, payment confirmation can’t be turned on.
The login and the token are stored encrypted and are never shown in the dashboard. With Test connection you can verify them again whenever you want.

Configure the Action

Connecting the store doesn’t turn anything on yet. To choose what the agent does:
1

Create the Jumpseller Action

Go to My agents → [your agent] → Actions, click New action, and choose Jumpseller.
2

Choose the capabilities

Turn on the ones you want (see the table below). Some depend on others.
3

Enable the Action and save

From then on, the agent uses your store in all its conversations.
An agent uses a single store. Also, Build a purchase can’t be turned on if the agent already sells with the Payment Action, and vice versa: an agent builds purchases from a single source.

Order lookup

In Buyer verification you choose which detail the visitor uses to prove the order is theirs: the purchase email (default), the phone, or the billing postal code. Any one match is enough.
Jumpseller’s checkout doesn’t ask for a phone or postal code by default. Turn them on only if your store requires them at checkout (Settings › Checkout): if the order doesn’t have them, verification with that detail fails.
To protect your customers’ data:
  • an order that doesn’t exist and a detail that doesn’t match get exactly the same reply, so nobody can guess order numbers;
  • after 5 failed attempts in the same conversation, order lookup is locked;
  • in the web widget, the agent shows a form for the order number and the verification detail.
For this capability we recommend Claude Sonnet or higher as the agent’s model (Settings → AI). In our tests, smaller models sometimes answer as if the order were already verified.

Build a purchase

When the visitor says what they want, the agent builds the list with the quantities, the price of each product, and a reference total, checking the stock at that moment. If a detail is missing (for example, the size), it asks before adding the product. On confirmation, the agent replies with one link per product. Each link adds that product to your store’s cart with the requested quantity. The visitor opens them one after another in the same browser, so they add up in the same cart, and pays in your Jumpseller checkout, where shipping is calculated.
  • Jumpseller doesn’t have a link with several products at once: that’s why there’s one link per product.
  • If the store has fewer units than requested at that moment, that link doesn’t add the product. The agent lets the visitor know.
  • ChatNorris doesn’t charge or create orders: the sale happens in your store, with your payment methods.
  • In Conversations, an internal note shows the list the agent built.

Payment confirmation

When you turn it on, ChatNorris registers a payment notification in your store (order_paid webhook). When an order is paid, ChatNorris links it to the conversation if all three conditions are met:
  1. the buyer’s email is the email the visitor left in the chat (for example, in the Lead Form);
  2. the agent sent them purchase links in the last 7 days;
  3. the order has at least one of the products from that list.
If they’re met, the agent writes in the conversation “We received your payment! Your order is confirmed”, an internal note records what was charged and, if the agent was handling the conversation, it moves to Resolved.
If the visitor didn’t leave their email in the chat, or paid with a different email, the sale is still recorded in your store, but the agent doesn’t confirm it in the conversation.
When you turn off the capability, delete the Action, or disconnect the store, ChatNorris deletes the payment notification it created. That’s the only thing ChatNorris creates in your store: it doesn’t create or change products or orders.

Import the catalog into the knowledge base

With the store connected, you can add your catalog as a knowledge source so the agent answers about each product’s descriptions, materials, or features, with the link to its page.
1

Add the source

Go to My agents → [your agent] → Knowledge Base → Add source and choose Jumpseller.
2

Import the catalog

Click Import catalog. Your store’s available products are imported.
  • Each product becomes a document with its name, brand, categories, description, variants with SKU, and the link to its page.
  • Prices and stock aren’t stored: the agent checks them live with the Jumpseller Action, so it never answers with an outdated price.
  • The source syncs again on its own at your plan’s frequency (weekly on Standard, daily on Premium). With Import again you update it whenever you want.
With the Action active, the source list also shows the Live Jumpseller catalog row. It isn’t a source: it indicates that the agent checks price and stock directly in the store.

Credits

Connecting the store doesn’t use credits. Each agent response that checks your store live (products, price and stock, or orders) adds 0.5 AI credit to the normal cost of the response. The imported catalog takes up characters of your knowledge base like any other source.

Disconnect

In My agents → [your agent] → Integrations → Jumpseller, click Disconnect. The Jumpseller Action is turned off and keeps its configuration, and ChatNorris deletes the payment notification if it had created one. If you’re no longer going to use the token, reset it in your store’s Account › Preferences.

Frequently asked questions

The agent only sees your store’s available products. Check in Jumpseller that the product isn’t disabled. If you search by SKU, check that the SKU is set on the product or the variant.
Check that the email they paid with is the same one they left in the chat, that the links were sent less than 7 days ago, and that the order includes at least one product from the list. Also check that the Payment confirmation capability is still on.
The message “Could not register the payment notification in Jumpseller” means the account that owns the token doesn’t have the hooks permission. Add it in Jumpseller, click Test connection, and turn it on again.
Jumpseller rejected the saved keys, for example because the token was reset. Copy the new token and paste it into the integration with Replace credentials.
No. An agent uses a single store so it doesn’t answer two different prices for the same product. If you have two stores, create one agent for each.