Actions2
Page
AI-generatedOverview
This node interacts with a Growi instance to retrieve information about pages. Specifically, for the "Default" resource and "Page" operation, it fetches details of a single page by its path or ID from the Growi wiki platform. This is useful in scenarios where you want to automate documentation workflows, synchronize content, or extract specific page data for further processing within n8n.
Example use cases:
- Automatically fetching documentation pages for reporting or backup.
- Integrating Growi content into other systems or dashboards.
- Triggering actions based on the content or existence of specific pages.
Properties
| Name | Type | Meaning |
|---|---|---|
| Path | String | The path (or ID) of the Growi page to retrieve. Default: /. |
Output
The node outputs a JSON object with the following structure:
{
"page": { /* Full page object as returned by the Growi API */ }
}
- The
pagefield contains all properties of the requested page as provided by the Growi API. The exact structure depends on the Growi server's response but typically includes metadata such as title, content, creator, timestamps, etc.
Dependencies
- Growi API: Requires access to a running Growi instance.
- API Credentials: Needs a credential set named
growiApiwith at least:token: API access token.baseUrl: Base URL of the Growi instance.
Troubleshooting
- Invalid Credentials: If the API token or base URL is incorrect, requests will fail with authentication errors. Ensure your credentials are valid and have sufficient permissions.
- Path Not Found: If the specified path does not exist, the API may return an error or an empty result. Double-check the path value.
- Network Issues: Connectivity problems between n8n and the Growi server can cause timeouts or connection errors.
- Error Messages: Common errors include HTTP 401 (Unauthorized), 404 (Not Found), or 500 (Server Error). Check the Growi server logs and ensure the API endpoint is reachable.