Overview
BigCommerce lets your agent search products, browse categories, read order details and check shipment and tracking information. Three more actions can prepare a basket, update an order's delivery address or cancel an unpaid order, if your API permissions and Cevanos settings allow them.
You do not build these actions yourself. You choose from 15 supplied capabilities: 12 Reads and 3 Does.
The journey at a glance
- 1Find BigCommerceOpen Integrations, search for BigCommerce and click Connect.
- 2Connect BigCommercePaste the store hash and access token, then Verify & connect.
- 3Check the BigCommerce pageConfirm Connected, then check health with Test connection.
- 4Choose what it can doTick Workspace and This agent, then Save capabilities.
- 5Set up Actions and approvalsSwitch actions on and choose whether changes wait for approval.
- 6Try itAsk a product question, then an order question, in the Playground.
Before you start
You need:
- An active BigCommerce store and a staff account that can manage store-level API accounts.
- A store hash (not a website address) and a store-level API account access token.
Create an API account in BigCommerce
- 1Sign in to the BigCommerce control panel and open Settings → Store-level API accounts.
- 2Choose Create API Account and, when asked, select the V2/V3 API token type.
- 3Give the account a name you will recognise, such as “Cevanos Support Agent”.
- 4For a first, read-only setup, allow Products, Orders and Customers to be read. Leave everything else at None.
- 5Save the account and copy its Access Token. Keep it in your password manager.
- 6Copy the store hash: the short code after /stores/ in the API path. In https://api.bigcommerce.com/stores/abc123/v3/, the hash is abc123.
Scopes cannot be edited later
BigCommerce store-level scopes cannot simply be changed after you create the account. If you need different permissions, create a replacement API account and reconnect with it.
Start read-only
Read-only access to Products, Orders and Customers is enough for safe first testing. The actions that change something need extra permissions; add them only when you need them.
Step 1
Find BigCommerce
- 1In the Cevanos dashboard, open your agent and go to Deployment → Integrations.
- 2Type BigCommerce in the search box, or look under Commerce.
- 3Check the badge on the card. Available means it is not connected yet. Click Connect.
Result
The Connect BigCommerce pop-up opens.
Step 2
Connect BigCommerce
2a. Before you start
- 1Read the note: Cevanos checks what you enter against BigCommerce before saving anything.
- 2Click Get started.
2b. Enter the credentials
| Field | What to enter |
|---|---|
| Store | Only the store hash from the control panel or API path, not the full store address. |
| Access token | The access token from the store-level API account. Treat it as a secret. |
- 1Paste the store hash and access token into their fields.
- 2Click Verify & connect.
If it fails
Check the store hash, the token and the API scopes before you try again.
2c. Connected
- The pop-up says “BigCommerce is connected”.
- If this store was connected before, you may be offered Switch them on to restore its previous capabilities. Review them before you restore.
- Click Choose what it can do to go straight to Step 4, or Back to integrations.
Result
Cevanos can reach your store. No action is switched on or authorized yet.
Step 3
Check the BigCommerce page
- 1Go back to Deployment → Integrations and search for BigCommerce.
- 2Check that the badge says Connected and the card offers Choose what it can do.
- 3Open the BigCommerce page to review the field mapping, permissions, connection status and Health → Test connection.
Result
You can confirm BigCommerce is connected. If Test connection fails, check the token is still valid and has the scopes it needs.
Step 4
Choose what it can do
Click Choose what it can do. Each capability has two checkboxes: Workspace controls whether any agent in the workspace may have it, and This agent controls whether the agent you are setting up may use it. Both must be ticked.
- 1For public questions, tick Search the catalogue and Read one product in both columns.
- 2For personal order lookups, tick the order reads you need. They need customer matching, not just an order number.
- 3Leave the actions that change orders off until you have reviewed both the API permissions and your approval policies.
- 4Click Save capabilities.
API permissions
The three Does capabilities need the matching BigCommerce write permissions as well as authorization in Cevanos. A switch on screen does not prove the token has write access.
Result
The capabilities ticked in both columns are available to this agent.
Step 5
Set up Actions and approvals
- 1In your agent's left sidebar, open Actions and find BigCommerce under Commerce.
- 2Open the BigCommerce panel and use the All, On, Reads, Does and Cannot run filters.
- 3Turn on only the capabilities this agent needs.
- 4Under When this agent does something on BigCommerce, choose Wait for approval if people should review actions before they run. Individual Does actions may have their own setting.
- 5Before switching on an action that changes something, check its identity requirement, your Governance policies and the API permissions.
Setting, not approving
Actions sets whether an action waits. Team members approve or reject an actual request in Operations → Pending actions. Choosing Wait for approval does not approve anything by itself.
- Reads run immediately and need no approval.
- Actions marked Matched customer run only after the customer's email or phone is matched to a customer.
- Actions marked Confirmed customer also need a verification code: the customer gets a 6-digit code by email, valid for 10 minutes and usable once. A newer code replaces an older one. Once the code is accepted, the customer may need to send one more message (for example “yes”) before the action is proposed.
- Actions that change something wait in Operations → Pending actions until a team member approves them.
- Approving in Pending actions can reload the Playground and reset its Test as email, so open Pending actions in a second browser tab while you test.
Result
You know which BigCommerce actions this agent can run and which changes wait for a person.
Step 6
Try it
Start with a low-risk product question, then move on to matched-customer questions in the Playground.
| Ask | What to check |
|---|---|
| “What products do you sell?” | Catalogue search runs and answers come from current product data. |
| “Tell me about this product.” | Read one product returns the right item. |
| “Where is my order?” | The agent matches the customer before showing order details. |
| “What is my tracking number?” | Shipment details are shown only for a matched customer with tracking data. |
| “Please cancel my unpaid order.” | Only try this in a test store with the write scope and confirmation in place; check approvals in Operations. |
- 1Ask one question in the Playground and check the agent's answer and the action result.
- 2If an action is waiting for approval, open Operations → Pending actions to review it. Do not assume the store has already changed.
- 3Confirm the outcome in BigCommerce itself before treating a change as done.
Result
Your agent answers catalogue and order questions from BigCommerce, and only for the customer it has matched.
Reference
What BigCommerce can do
BigCommerce supplies 15 capabilities: 12 reads and 3 that change something. “Matched customer” and “Confirmed customer” are requirements, not a way around verification or Governance.
15 capabilities · 12 reads · 3 that change something
- Anyone can ask
Search the catalogue
bigcommerce.search_products - Anyone can ask
Read one product
bigcommerce.get_product - Anyone can ask
Browse the catalogue
bigcommerce.browse_products - Anyone can ask
List product categories
bigcommerce.list_categories - Anyone can ask
Read product sizes and colours
bigcommerce.list_variants - Anyone can ask
Read product reviews
bigcommerce.list_reviews - Anyone can ask
Read delivery options
bigcommerce.list_shipping_options - Anyone can ask
Check a discount code
bigcommerce.check_coupon - Matched customer
Find this customer's orders
bigcommerce.list_orders - Matched customer
Read one order
bigcommerce.get_order - Matched customer
Read the items in an order
bigcommerce.get_order_items - Matched customer
Read shipping and tracking
bigcommerce.get_order_shipments
- Matched customer
Prepare a basket
bigcommerce.create_cart - Confirmed customer
Change delivery address
bigcommerce.update_order_address - Confirmed customer
Cancel an unpaid order
bigcommerce.cancel_order
Good to know
A read-only token is enough for the reads. The three actions that change something need BigCommerce write permissions too.
Troubleshooting
| Problem | What to check |
|---|---|
| Verify & connect fails | Check the store hash, that the token was copied in full, and the API scopes. Create a new API account if you need different scopes. |
| Connected, but the agent cannot search | Check that Workspace and This agent are both ticked and saved, then check Actions. |
| Order details are not returned | Customer matching may be needed. Check that the order belongs to the customer the agent identified. |
| An action that changes something fails | A read-only token cannot make changes. Check the modify scopes, your Cevanos policies and whether the order is eligible. |
| An action is pending | Open Operations → Pending actions; it may need approval before it runs. |
| A product or tracking value is missing | Check that the data exists in BigCommerce and that the capability and token permissions cover it. |
| Test connection fails | Check the token is still valid and has the scopes it needs. A Connected badge alone does not prove every call will succeed. |
Optional
Disconnect BigCommerce
- 1Open the BigCommerce page and find Disconnect BigCommerce.
- 2Review which agents and capabilities are affected, then confirm only if you want Cevanos to stop using the store.
- 3To revoke the credential itself, delete its store-level API account in BigCommerce.
Two separate controls
Disconnecting in Cevanos and revoking the API account in BigCommerce are separate. Never put real access tokens in screenshots, support tickets or customer-facing documents.
Help from BigCommerce
Ready to connect BigCommerce?
Open your agent's Integrations and click Connect on the BigCommerce card.