Save to Box

Send web data from any Apify Actor straight into Box. Attach Save to Box as an integration and every run lands in a Box folder as an Excel, CSV or JSON file, together with any screenshots, PDFs or reports the run produced. Your team picks it up where they already work, with Box permissions, retention, search, workflows and Box AI.

Why use it

• Web data where your company already works. No exports, downloads or re-uploads. Results land in a Box folder automatically after every run.
• Works with thousands of Actors. Google Maps, Amazon, LinkedIn, Instagram, Google Search, any website crawler. If it runs on Apify, its results can go to Box.
• Version history built in. Give the file a fixed name (e.g. {actor} results) and each run becomes a new version of the same Box file, so you get one file to share and a full history.
• Box does the rest. Use Box Automate to route new files for approval, Box AI to ask questions about them, metadata and retention policies to govern them, and shared links to send them to people.

What gets saved

From the run	Saved to Box as
Dataset (the scraped results)	One file per format you pick: Excel, CSV, JSON, JSON Lines, XML or HTML table
Files in the run's key-value store (optional)	The original files: screenshots, PDFs, HTML snapshots, reports. Internal records like INPUT are skipped

Each file gets a Box description saying which Actor and run produced it, so it's easy to find in Box search.

Use cases

• Competitor and pricing intelligence: daily product, price and review scrapes in a shared Box folder for sales and product teams.
• Lead lists: Google Maps or LinkedIn results delivered as Excel straight to the sales team's folder.
• Brand and reputation monitoring: reviews and social mentions archived in Box, ready for Box AI ("What are customers complaining about this month?").
• Compliance and regulatory monitoring: snapshots of regulator and policy pages archived with your Box retention policies.
• Vendor and supplier research: company data and news per vendor, filed where procurement keeps everything else.
• A knowledge base for Box AI: turn websites into documents Box AI can answer questions about, alongside your internal files.

Quick start

1. Create a Box app (once, about 5 minutes)

1. Go to the Box Developer Console > Create Platform App > Custom App > Server Authentication (Client Credentials Grant).
2. On the Configuration tab:
   • App access level: App Access Only is enough. Choose App + Enterprise Access only if you want to connect as a specific Box user (see step 2 below).
   • Application scopes: Read and write all files and folders stored in Box.
   • Click Save.
3. Get the app authorized: your Box admin approves it under Admin Console > Integrations > Platform Apps Manager. If you are the admin, approve it yourself.
4. Collect three values:
   • Client ID and Client Secret: on your app's page, click the App Details panel icon at the top right (next to the ⋯ button). Click Copy next to Client ID, and Fetch Secret next to Client Secret (Box may ask you to confirm with two-factor authentication).
   • Enterprise ID: Admin Console > Account & Billing.

Just want to try it? Generate a Developer Token for your app in the Box Developer Console and paste it into the Developer token field. It works for 60 minutes and connects as you, with no admin approval needed.

2. Give the app access to your folder

The app has its own Box account, called a service account. Share your target folder with it:

1. Run Save to Box once. If it can't see the folder, the error message tells you the exact service account email, e.g. AutomationUser_1234_abc@boxdevedition.com.
2. In Box, open the folder > Share > Invite people, add that email as Editor.

Alternatively, choose Connect as > A specific Box user, enter your Box user ID, and enable Generate user access tokens in the app's advanced features. Files are then owned by that user, and any folder that user can edit works without extra sharing.

3. Attach it to an Actor

1. Open the Actor whose results you want in Box (e.g. Google Maps Scraper) > Integrations tab > Add integration > search Save to Box.
2. Fill in the Box folder ID (the number at the end of the folder URL, app.box.com/folder/123456789) and your Box connection details.
3. Save. From now on every successful run is uploaded automatically, including runs started by schedules and the API.

Tip: set it up once, reuse it everywhere. Fill in your Box settings on Save to Box, click Save as a new task, and attach that task instead of the Actor. In the integration's Input JSON overrides, add {"datasetId": "{{resource.defaultDatasetId}}"} so each run uploads its own results. Attach integrations to a saved task (e.g. "Weekly leads: dentists in Austin") rather than the Actor itself if you only want some runs to go to Box.

You can also run Save to Box on its own: pick any dataset under Source and click Start.

Options

Option	What it does
Dataset formats	Excel (default), CSV, JSON, JSON Lines, XML, HTML table. Pick several to get one file each
Only these fields	Keep only the columns you need, e.g. title, url, price
Also save files from the run	Upload screenshots, PDFs and other files the Actor stored. Filter by key prefix and cap the count
File name	Template with {actor}, {date}, {time}, {runId}. A fixed name means new versions of one file
Subfolder	e.g. {actor}, {date} or {actor}/{date}. Created automatically
Create shared link	No / people in the folder / anyone in your company
Upload when the dataset is empty	Off by default, so empty runs don't create empty files

Large exports are handled automatically: files over 40 MB use Box's chunked upload API.

Output

The Actor's own dataset lists every uploaded file with its Box file ID, Box URL, size, whether it was a new version, and the shared link if you created one. The OUTPUT record holds the destination folder URL.

Security

• The client secret and developer token are secret inputs: stored encrypted and never written to logs.
• The Actor runs with limited permissions. It can only read the dataset and key-value store of the run it's attached to, nothing else in your Apify account.
• Box access is whatever you grant the app. Use a dedicated folder, and give the service account Editor access only to that folder.

Troubleshooting

Message	Fix
Box sign-in failed (invalid_client)	Client ID or secret is wrong. Copy them again from the Developer Console
Box sign-in failed (unauthorized_client)	The app isn't approved in your enterprise yet. Ask your Box admin to approve it in Platform Apps Manager
Box sign-in failed (invalid_grant)	The Enterprise ID or user ID doesn't match the app
Box folder … is not visible to …	Invite the service account email shown in the message to the folder as Editor
can see folder … but cannot upload	Raise that account's role on the folder to Editor or Uploader

Pricing

No Actor fee. You pay only Apify platform usage, which is tiny: a typical upload runs for about 5 seconds at 512 MB, around 0.0007 compute units, so thousands of uploads cost less than a dollar. The scraping run that produces the data costs far more than saving it to Box.

Exporting a very large dataset (100,000+ rows to Excel)? Raise Memory to 1–2 GB under Run options.

Feedback

Ideas for what should happen in Box next, like metadata, Box AI or Automate triggers? Open an issue on the Actor's Issues tab.

---

Save to Box is an independent integration built on Apify. It is not made, endorsed or supported by Box, Inc. "Box" is a trademark of Box, Inc.