ConnectRequest demo

Overview

Use BigCommerce as a governed source or destination in a Context runbook. Configure the exact records and actions each agent can access.

  • · Vendor-supported OAuth or scoped service credentials
  • · Read and write access configured separately
  • · Tool calls and outcomes recorded per run
Connector contract

Control what agents can do in BigCommerce.

Exact authentication methods and available scopes depend on your BigCommerce plan and deployment. Context keeps the connector configuration explicit.

Read

Read the resources explicitly selected for the runbook.

Act

Use supported write actions only where your team enables them.

Verify

Keep source references, tool calls, and outcomes in the run trace.

Set up the connection

  1. 01

    Authenticate

    Connect BigCommerce with an admin-approved OAuth flow or scoped credential supported by the vendor.

  2. 02

    Choose scope

    Select the accounts, workspaces, projects, or resources available to the runbook.

  3. 03

    Map policy

    Set read and write permissions, reviewer gates, and the identity used for each action.

  4. 04

    Test a run

    Verify one read, one permitted action, and the resulting audit record before rollout.

Build with BigCommerce

BigCommerce can be added to any Context runbook. Start from a prebuilt agent, then choose the resources and actions it needs. Browse all agents →

More in Commerce & payments

ShopifyStripeSquarePayPalAdyenAdobe Commerce

Connect BigCommerce to Context.

Request demo