Neura Market Logo

box-integration-best-practices

Build, debug, or review repeatable Box API integrations and agent workflows for efficient calls, bulk work, and 429 handling.

Chris Kim (Hyunggun)

@iskysun96

Install

$ openclaw skills install @iskysun96/box-integration-best-practices

Box integration best practices

Preserve result coverage and permissions when reducing calls. For bulk work or 429 errors, estimate calls per completed item and peak request rate by Box actor and endpoint. Budget uploads and search against their separate limits. Check the current rate limits; user, endpoint, enterprise, and temporary quality-of-service limits may apply.

Reduce calls

For reviews, trace Box requests through loops and retry paths before changing concurrency or seeking more capacity.

  • Reuse cached access tokens. Request fields needed for a decision in the list response when supported, and reuse returned data instead of fetching each item again. fields reduces call count only when it replaces a follow-up read.
  • Use the largest useful supported page size. For large or changing collections, use marker pagination where supported; follow next_marker to completion and do not treat a marker as a durable checkpoint.
  • Use webhooks or events with a catch-up path instead of repeated full scans. Deduplicate deliveries; checkpoint event stream positions after successful processing. Query supported enterprise metadata templates instead of fetching metadata for every file.
  • When content stays in Box, prefer Box-side copy, move, or update operations over download and re-upload.

Control bulk work and retries

  • Bound concurrency across workers sharing a Box actor, accounting for endpoint and enterprise limits. On 429, honor Retry-After across affected workers. Current official SDKs retry 429s; check the installed version before adding another retry layer. For direct HTTP, use bounded backoff with jitter.
  • For long-running jobs, persist per-item outcomes so work can resume. Reconcile uncertain writes before retrying them.
  • Refresh expired tokens on 401; pause if failures persist. For 403, record item-specific denials and pause when failures indicate actor or app access is wrong.
  • If necessary traffic still exceeds available capacity after removing avoidable calls, surface the capacity need. Do not rotate identities to evade limits.

Check the result

Record Box calls and 429s by actor, endpoint, and status; compare calls per completed item and completed-job throughput on a representative workload. Use the Platform Activity report for historical per-app totals. If a token reaches a browser or other client-side component, downscope it.

Top skills in this category

API Gateway

@byungkyu

Call third-party APIs through the Maton gateway, which injects the credential for an app the user has already connected. Use this skill when the user names a connected app and a concrete action in it - read a mailbox, query a CRM, file an issue, update a spreadsheet, etc.

39488k

OpenClaw Command Center

@jontsai

Mission control dashboard for OpenClaw - real-time session monitoring, LLM usage tracking, cost intelligence, and system vitals. View all your AI agents in one place.

7914k

GitHub

@byungkyu

GitHub API integration with managed OAuth. Access repositories, issues, pull requests, commits, branches, and users. Use this skill when users want to interact with GitHub repositories, manage issues and PRs, search code, or automate workflows. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a GitHub connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a GitHub action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with GitHub examples; they add no GitHub capability - GitHub is itself an event source, so its own events are in `references/github/triggers.md`, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

4719k

google-slides

@byungkyu

Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

3420k

Interview Simulator

@wscats

Simulates mock interviews for any role and experience level with tailored technical, behavioral, and case questions plus detailed feedback and scoring.

2322k