Actions53
- Attachment Actions
- Collection Actions
- Comment Actions
- Document Actions
- Event Actions
- File Operation Actions
- Group Actions
- User Actions
Overview
This node interacts with the Outline knowledge base API, allowing users to perform various operations on different resources such as documents, collections, attachments, comments, groups, users, and more. Specifically, for the Document - Get operation, it retrieves detailed information about a specific document by its ID.
Common scenarios where this node is beneficial include:
- Fetching document details to display or process within an automation workflow.
- Integrating Outline documents into other systems by retrieving their metadata and content.
- Automating document management tasks like auditing or reporting based on document data.
Practical example:
- You want to automatically fetch the content and metadata of a particular document in Outline when triggered by an event, then use that data to generate reports or send notifications.
Properties
| Name | Meaning |
|---|---|
| Document ID | The unique identifier of the document to retrieve. This is required for the "Get" operation on the Document resource. |
Output
The output contains a JSON object representing the detailed information of the requested document. This typically includes fields such as the document's title, content (in markdown format), publication status, collection association, creation and update timestamps, and other metadata provided by the Outline API.
If multiple items are processed, the output will be an array of such JSON objects, each corresponding to one input item.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Outline API.
- The node uses the Outline API endpoints via HTTP POST requests to perform actions.
- No additional external dependencies beyond the configured API authentication.
Troubleshooting
Common issues:
- Invalid or missing Document ID: The API call will fail if the Document ID is not provided or incorrect.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network or API downtime: Temporary connectivity issues can cause request failures.
Error messages:
- Errors returned from the Outline API will be passed through, often indicating issues like "Document not found" or "Unauthorized".
- If the node is set to continue on failure, error details will appear in the output JSON under an
errorfield.
Resolutions:
- Verify the Document ID is correct and exists in the Outline knowledge base.
- Check API credentials and permissions.
- Retry after some time if network or service issues are suspected.
Links and References
- Outline API Documentation (general reference for available endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance