STEP 1
Connect Apify and Microsoft Files
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 Microsoft Files Integration
Connect Apify and Microsoft Files to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Apify and Microsoft Files
Detailed info you need to know about Apify and Microsoft Files integrations in WEXTL. Explore which modules apps support and how you connect them.
Apify
Run Apify Actors and tasks, manage datasets and stores, and watch for Actor run completion events. [5]
Microsoft Files
OneDrive and SharePoint files — upload, download, and manage documents. [6]
How to connect Apify to Microsoft Files
Set up your Apify and Microsoft Files integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Apify and Microsoft Files 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 Microsoft Files. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Apify and Microsoft Files work in WEXTL?
WEXTL exposes actions and triggers for Apify and Microsoft Files 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 triggersMicrosoft Files 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 KeysReturns list of keys.
- Get List of Key-Value StoresReturns list of key-value stores.
Microsoft Files modules
- Activeate a File Container StorageActivate a file storage container object.
- Add Bundle ItemAdd an additional driveItem from a drive to a bundle.
- Copy a Drive ItemMake a new copy of a drive item.
- Create a BundleAdd a new bundle to the user's drive.
- Create a File Container StorageCreate a new file storage container object.
- Create a File Container Storage TypeCreate a new file storage container type.
- Create a FolderCreate a new folder in a drive.
- Delete a BundleRemove a bundle by a provided ID.
- Delete a Bundle ItemRemove an item from a bundle.
- Delete a Drive ItemDelete a DriveItem by using its ID or path.
- Delete a File Container StorageRemove a file storage container object.
- Delete a File Container Storage TypeRemove a single storage container type.
- Download a FileDownload the contents of the primary stream (file) of a drive item.
- Follow a Drive ItemPerforms the a Drive Item operation.
- List Available DrivesRetrieve the list of Drive resources available for a target User, Group, or Site.
- List BundlesGet a list of all the bundles in a user's drive.
- List Drive ActivitiesList the recent activities that took place on a drive.
- List File Storage ContainerGet a list of fileStorageContainer objects that are accessible to a caller.
- List File Storage Container TypesGet a list of the file storage container type objects and their properties.
- List Followed ItemsList the items that have been followed by the signed in user.
- Make an API CallPerform an arbitrary authorized API request.
- Move a Drive ItemMove a driveItem to a new folder.
- Remove a Deleted File Container StoragePermanently remove a deleted file storage container object.
- Restore a Deleted File Container StorageRestore a deleted file storage container object.
- Retrieve a BundleRequest a single bundle by a provided ID.
- Retrieve a DriveRetrieve the properties and relationships of a Drive resource.
- Retrieve a Drive ItemRetrieve the metadata for a driveItem in a drive by file system path or ID.
- Retrieve a File Container StorageRetrieve the properties of a file storage container object.
- Retrieve a File Container Storage TypeRequest a single storage container type.
- Retrieve User DriveRetrieve the properties and relationships of a Drive resource for the current authenticated user.
- Update a BundleUpdate the metadata for a bundle of driveItems by ID.
- Update a FileUpdating an existing file.
- Update a File Container StorageUpdate the properties of a file storage container object.
- Update a File Container Storage TypeUpdate the properties storage container type.
- Upload a FileUpload a new file.
- Watch DrivesTriggers when new drives are created.
- Watch File Storage ContainerWatch for new file storage container.
- Watch File Storage Container TypeWatch for new file storage container type.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Apify and Microsoft Files integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Apify and Microsoft Files.
Connect your Apify and Microsoft Files 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 "Activeate a File Container Storage" in Microsoft Files. Apify has 4 triggers (including Watch Run Aborted, Watch Run Failed, and Watch Run Succeeded); Microsoft Files has 35 actions (including Activeate a File Container Storage, Add Bundle Item, and Copy a Drive Item). 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-Microsoft Files 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 Microsoft Files) 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 + Microsoft Files 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 Microsoft Files integration.
- Apify and Microsoft Files integration source code, module specs and credentials implementation.
- Our Apify and Microsoft Files integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Apify and Microsoft Files — 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
- Microsoft Files integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library