This repository includes agent skills and a Next.js webhook processor for Box. Follow the steps below to go from a new Box account to a deployed webhook endpoint.
Sign up for a free account at box.com if you do not already have one.
- Open the Box Developer Console.
- Create a new Custom App (Box’s platform integration type used for webhooks and server-side flows).
- Complete the Configuration tab: set authentication, redirect URIs, and any scopes your integration needs, following Box’s app configuration guides.
- For the webhook service in this repo, enable webhooks for the events you care about and copy the Primary and Secondary webhook signing keys (you will add them to the Next.js app’s environment).
From the repository root (where skills-lock.json lives), install the skills pinned in the lockfile into your agent directories:
npx skills experimental_installThis restores the skills listed in skills-lock.json (for example the Box and task-management skills). If you add new skills later, use npx skills add <source> and commit the updated lockfile.
The app lives in process-webhook/.
-
Install dependencies and set environment variables:
cd process-webhook npm install cp .env.example .env -
Edit
.envwith your Box webhook signing keys and Vercel sandbox credentials. Seeprocess-webhook/.env.examplefor all variables. On Vercel, preferVERCEL_OIDC_TOKEN; for local or non-OIDC setups, useVERCEL_TEAM_ID,VERCEL_PROJECT_ID, andVERCEL_TOKENas documented there. -
Deploy (for example with Vercel): connect the repo or the
process-webhookdirectory as a project, add the same environment variables in the dashboard, and deploy. More detail is inprocess-webhook/README.md.
After deployment, your handler is exposed at:
https://<your-deployment-host>/api/box/webhook
In the Box Developer Console, open your app’s webhook settings and set the callback URL to that address (HTTP POST). Save and use Box’s tools to send a test delivery if available.
For day-to-day development of the webhook service, see process-webhook/README.md.