Actions53
- Attachment Actions
- Collection Actions
- Comment Actions
- Document Actions
- Event Actions
- File Operation Actions
- Group Actions
- User Actions
Overview
The node interacts with the Outline knowledge base API, specifically handling file operations when the "File Operation" resource and "List" operation are selected. It retrieves a list of file operations performed within the Outline system. This is useful for monitoring or auditing file-related activities such as uploads, deletions, or processing tasks.
Practical scenarios include:
- Tracking recent file operations to audit changes.
- Fetching paginated lists of file operations for reporting.
- Integrating file operation data into workflows for further automation or notifications.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional filters and pagination controls: |
| - Date Filter | Filter file operations by date range: Day, Week, Month, Year |
| - Include Archived | Whether to include archived documents in results (boolean) |
| - Include Drafts | Whether to include draft documents in results (boolean) |
| - Limit | Number of results to return (1 to 100, default 25) |
| - Offset | Number of results to skip (pagination offset, minimum 0, default 0) |
| - Sort | Field to sort by: Created At, Updated At, Title, Index |
| - Direction | Sort direction: Ascending or Descending |
| - Status Filter | Filter by document status: Published, Draft, Archived (multi-select, default Published) |
These properties allow fine-tuning the list query to retrieve specific subsets of file operations based on time, status, sorting, and pagination.
Output
The output is an array of JSON objects representing file operations retrieved from the Outline API. Each item corresponds to a file operation record containing details such as operation ID, status, timestamps, and related metadata.
If multiple items are returned by the API, they are all included in the output array. The node does not output binary data for this operation.
Example output structure (simplified):
[
{
"id": "fileOperationId",
"status": "completed",
"createdAt": "2024-01-01T12:00:00Z",
"updatedAt": "2024-01-02T12:00:00Z",
"resultUrl": "https://example.com/file-operation-result"
// ... other metadata fields
},
...
]
Dependencies
- Requires an API key credential for authenticating with the Outline knowledge base API.
- The node uses HTTP POST requests to communicate with the Outline API endpoints.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Exceeding rate limits imposed by the Outline API may result in request failures.
- Providing invalid filter values (e.g., unsupported date filter) can cause API errors.
- Pagination parameters (limit, offset) must be within allowed ranges; otherwise, the API may reject the request.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- Validation errors from the API often specify which parameter is incorrect; adjust input accordingly.
- Network or timeout errors suggest connectivity issues; retry or check network settings.