Once the integration is active, OneDrive enables the platform to automate file operations, manage document transfers, and sync outputs across relevant areas of your workspace. This documentation outlines how data moves between OneDrive and the platform, which actions and file-based results are supported, and where possible limitations may occur based on permission scopes, folder structure, or Microsoft Graph API constraints.

Trigger Timing and Execution Behavior

Workflows involving OneDrive run based on direct triggers initiated by user actions or internal system events. There is no interval-based polling or background sync. All executions are driven by event-based logic, which ensures that actions are only taken when needed.

Integration timing is configurable. Workflow designers or admins can define when OneDrive actions occur using conditional logic or action parameters. Each operational workflow may include manual triggers (initiated by users) or automated triggers (enabled by reaching a certain status or condition).

• Manual triggers include actions such as a user submitting a record or selecting "Export to OneDrive" from a menu.
• Automated triggers include system-driven events, such as data changes, record completions, time-based conditions, or error recovery patterns.

Execution begins immediately once the trigger condition is met. Total processing time depends on factors like API performance, file sizes, retry logic, and system load.

Payload Structure and Re-Execution Support

Each OneDrive action receives a scoped data payload generated by the triggering event. This may include:

• Complete records or selected field values
• Calculated paths or folder destinations
• Timestamps, user identifiers, or reference metadata
• Attachments, reports, or exported data in file format

The data passed to OneDrive is precise and limited to the context of the action. There is no implicit access to other records or background data, which helps maintain security and proper audit control.

Re-executing OneDrive-related workflows is fully supported. Authorized users can revisit historical records or previously run automation logs and relaunch the OneDrive action if needed. This is helpful for handling failed executions, regenerating outputs, or auditing previous runs.

Data Exchange Between the Platform and OneDrive

The platform exchanges data with OneDrive using Microsoft Graph API endpoints. During execution, files, metadata, and control signals flow between the two systems. The integration supports the following types of data transfer:

From the platform to OneDrive:

• Field values, file attachments, and generated documents
• File paths, folder locations, and naming conventions
• Metadata tags or version-related identifiers

From OneDrive to the platform:

• Upload results, including success or failure status
• File IDs or URLs returned from the Microsoft Graph API
• Optional metadata such as timestamps or storage references
• Traces or structured logs if returned explicitly by the API

Results of OneDrive operations are captured in the platform and may be stored in related records or surfaced in linked summaries. Detailed diagnostics from OneDrive itself must be requested or passed intentionally for debugging or analysis.