STEP 1
Connect Apify and Box
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Apify and Box Integration
Build developer tools workflows between Apify and Box on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and Box
Detailed info you need to know about Apify and Box integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Apify to Box
Set up your Apify and Box integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and Box nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Apify and Box. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and Box work in WEXTL?
WEXTL exposes actions and triggers for Apify and Box that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Apify triggersBox actions
Apify modules
- Add Request to QueueCreates request to queue.
- Batch Add RequestsPerforms batch add requests.
- Build ActorBuilds actor.
- Charge Events in RunCharges events in run.
- Create ActorCreates actor.
- Create DatasetCreates dataset.
- Create Environment VariableCreates environment variable.
- Create Key-Value StoreCreates key-value store.
- Create Request QueueCreates request queue.
- Create ScheduleCreates schedule.
- Create TaskCreates task.
- Create VersionCreates version.
- Decode and Verify DataRetrieves decode and verify data.
- Delete ActorDeletes actor.
- Delete Build (Abort)Aborts build.
- Delete Build (Abort, Cross-Actor)Aborts build (cross-actor).
- Delete DatasetDeletes dataset.
- Delete Environment VariableDeletes environment variable.
- Delete Key-Value StoreDeletes key-value store.
- Delete RecordDeletes record.
- Delete RequestDeletes request.
- Delete Request QueueDeletes request queue.
- Delete Run (Abort)Aborts an Actor run (DELETE semantics).
- Delete Run (Abort, Cross-Actor)Aborts run (cross-actor).
- Delete ScheduleDeletes schedule.
- Delete TaskDeletes task.
- Delete VersionDeletes version.
- Delete WebhookDeletes webhook.
- Download Records (Batch Export)Retrieves download records (batch export).
- Encode and Sign DataEncodes and sign data.
- Get ActorReturns actor.
- Get Browser InfoReturns browser info.
- Get Browser Info (POST Variant)Returns browser info (post variant).
- Get BuildReturns build.
- Get Build (Cross-Actor)Returns build (cross-actor).
- Get Build LogReturns build log.
- Get Build Log (Cross-Actor)Returns build log (cross-actor).
- Get DatasetReturns dataset.
- Get Dataset ItemsReturns dataset items.
- Get Dataset StatisticsReturns dataset statistics.
- Get Default BuildReturns default build.
- Get Environment VariableReturns environment variable.
- Get Environment VariablesReturns environment variables.
- Get Key-Value StoreReturns key-value store.
- Get Last Task RunReturns last task run.
- Get List of ActorsReturns list of actors.
- Get List of BuildsReturns list of builds.
- Get List of DatasetsReturns list of datasets.
- Get List of Key-Value StoresReturns list of key-value stores.
- Get List of KeysReturns list of keys.
Box modules
- Add a User to a GroupCreates a membership that adds a user to a group.
- Add or Update a User's AvatarUploads or replaces a user's profile picture.
- Add Shared Link to FileCreates a public or company-scoped link to a file.
- Add Shared Link to FolderCreates a public or company-scoped link to a folder.
- Apply Watermark To FileOverlays a visual watermark on a file's previews.
- Apply Watermark To FolderOverlays a visual watermark on a folder's previews.
- Assign TaskAssigns a task to a user.
- Cancel Box Sign RequestCancels an existing Box Sign request.
- Commit Upload SessionAssembles the uploaded parts into the final file.
- Copy FileCopies a file to another folder in Box.
- Copy File RequestDuplicates a file request onto a different folder.
- Copy FolderCopies a folder to another location in Box.
- Create a GroupCreates a new group in the enterprise.
- Create a UserCreates a new managed user in the enterprise.
- Create Box Sign RequestCreates a new Box Sign request with specified signers and source files.
- Create CollaborationInvites a user or group to collaborate on an item.
- Create CommentPosts a new comment on a file, folder, or other item.
- Create FolderCreates a new folder in Box.
- Create Folder LockLocks a folder to prevent it from being moved or deleted.
- Create Metadata Instance on FileApplies a metadata template's values to a file.
- Create Metadata Instance on FolderApplies a metadata template's values to a folder.
- Create Metadata TemplateDefines a new custom metadata template schema for the enterprise.
- Create TaskCreates a new task on a file.
- Create Upload SessionStarts a chunked upload session for a new file.
- Create Upload Session for Existing FileStarts a chunked upload session for a new version of an existing file.
- Create User InviteInvites an external user to become a collaborator in the enterprise.
- Create Web LinkSaves a URL as a bookmark inside a folder.
- Create Zip DownloadBundles multiple files and folders into a downloadable zip archive.
- Delete a UserDeletes a managed user from the enterprise.
- Delete a User's AvatarRemoves a managed user's profile picture.
- Delete FileMoves a file to the trash, from which it can still be restored or permanently erased.
- Delete File RequestRemoves a file request page from Box.
- Delete FolderMoves a folder to the trash, from which it can still be restored or permanently erased.
- Delete Folder LockReleases a lock that prevented a folder from being moved or deleted.
- Download FileDownloads the binary content of a file.
- Download Zip ArchiveDownloads the binary content of a zip archive.
- Find File for Shared LinkResolves a shared link URL to its file.
- Find Folder for Shared LinkResolves a shared link URL to its folder.
- Find Metadata Template by Instance IDFinds the metadata template a specific metadata instance was created from, by that instance's ID.
- Get a GroupReturns the details of a single group.
- Get a Group MembershipReturns a single user's role and status within a group.
- Get a UserReturns the profile of a single user.
- Get a User's AvatarReturns the binary image data of a managed user's profile picture.
- Get Box Sign Request by IDRetrieves a specific Box Sign request by its ID.
- Get Box Sign Template by IDRetrieves a specific Box Sign template by its ID.
- Get CollaborationReturns the details of a single collaboration.
- Get Collection by IDReturns the name and type of a single collection, such as Favorites.
- Get CommentRetrieves a specific comment by ID.
- Get File InformationReturns a file's metadata, including its name, size, and parent folder.
- Get File RequestReturns the title, status, and destination folder of a file request page.
Frequently asked questions
Common questions about connecting Apify and Box.
Connect your Apify and Box accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Apify's "Watch Run Aborted" fires, WEXTL can "Add a User to a Group" in Box. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); Box has 148 actions (including Add a User to a Group, Add or Update a User's Avatar, and Add Shared Link to File). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Apify-to-Box automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Apify (or Box) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Apify + Box automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Apify and Box integration.
- Apify and Box integration source code, module specs and credentials implementation.
- Our Apify and Box integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Box — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Apify integration information
- Box integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library