Integration
Connect BigCommerce to Huntress
When New Customer fires in BigCommerce, your agent runs Add organization in Huntress. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want BigCommerce and Huntress to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What BigCommerce can start in Huntress
When New Customer in BigCommerce
then Add organization in Huntress
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with BigCommerce and Huntress
Triggers and actions 3 triggers · 25 actions
- New Customer
Triggered when a new customer is added.
- New Order With Specified Status
Triggered when a new order is given the specified status.
- New product
Triggers when a new product is added to the BigCommerce catalog.
- Create Customer
Create a new customer.
- Delete brand
Deletes a brand from the BigCommerce catalog.
- Delete category
Deletes a category from the store's catalog by its ID.
- Delete Customer
Delete a customer by ID.
- Delete Product
Delete a product by ID.
- Get brand
Returns a single brand from the store's catalog by its ID, including its name, SEO details, image URL and storefront URL.
- Get category
Returns a single catalog category by its ID, including its name, parent, description, visibility and storefront URL.
- Get Customer
Retrieve a customer by ID.
- Get Order
Retrieve a single order by ID.
- Get Product
Retrieve a single product by ID.
- List Brands
List product brands.
- List Categories
List product categories.
- List Customers
List customers, optionally filtered by email.
- List Order Products
List the line-item products on an order.
- List Orders
List orders, optionally filtered by status or customer.
- List Products
List products in the catalog, optionally filtered by keyword.
- Update brand
Updates an existing brand's name, SEO details, image and storefront URL.
- Update Customer
Update an existing customer by ID.
- Update Order
Update an existing order (e.g. change status) by ID.
- Add organization
Creates a new organization in your Huntress account with a name and agent key.
- Delete organization
Deletes an organization from your Huntress account, optionally revoking its organization key.
- Get organization
Returns the details of a single Huntress organization, including its name, key, agent and incident counts, report recipients and product usage.
- List memberships
Returns the user memberships in your Huntress account, optionally filtered by organization, user or permission level.
- List organizations
Returns the organizations in your Huntress account, optionally filtered by name or key.
- Update organization
Updates a Huntress organization's name, key or report recipients and returns the updated organization.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from BigCommerce
BigCommerce to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
BigCommerce to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
BigCommerce to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
BigCommerce to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
BigCommerce to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
BigCommerce to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Huntress
WaiverFile to HuntressWaiverFile lets your customers sign waivers from a computer, tablet or mobile device.
Questions
BigCommerce and Huntress, answered
What can start an automation from BigCommerce?
Any of BigCommerce's 3 triggers in the catalog, including New Customer, New Order With Specified Status and New product. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Huntress when something happens in BigCommerce?
Any of Huntress's 6 actions, including Update organization, Add organization, Get organization and List memberships. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Huntress to BigCommerce?
Huntress has no triggers in the catalog today, so automations start in BigCommerce. If you need the other direction, ask: your agent reads Huntress's API documentation and adds it.
Do I have to build a connector for BigCommerce or Huntress?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use BigCommerce and Huntress without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.