Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node is designed to retrieve a specific article by its unique identifier. It is useful in scenarios where you need to fetch detailed information about a single article from a collection or database, such as displaying article content on a website, processing article data for analytics, or integrating article details into other workflows.
For example, if you have an article ID and want to get the full article details to display in a CMS or send it via email, this node will perform that retrieval efficiently.
Properties
| Name | Meaning |
|---|---|
| Id | ID of the requested article (number) |
The only required input property is the article's ID, which must be provided to specify which article to retrieve.
Output
The node outputs JSON data representing the article corresponding to the provided ID. The structure of the JSON output typically includes all relevant fields of the article such as title, content, author, publish date, etc., depending on the API's response schema.
If the node supports binary data (not evident from the provided code), it would represent attachments or media related to the article, but no such indication is present here.
Dependencies
- Requires an API key credential for authentication with the external service.
- Depends on a base URL configured in the node credentials to connect to the correct API endpoint.
- Uses an OpenAPI-based properties builder to define its parameters and requests.
Troubleshooting
Common issues:
- Providing an invalid or non-existent article ID will likely result in an error or empty response.
- Missing or incorrect API credentials can cause authentication failures.
- Network connectivity problems may prevent the node from reaching the API.
Error messages:
- Authentication errors indicate issues with the API key or token; verify credentials are correctly set.
- "Article not found" or similar messages suggest the ID does not exist; double-check the ID value.
- Timeout or connection errors imply network issues; ensure the API endpoint is reachable.
Links and References
- Refer to the API documentation of the article service for detailed schema and available fields.
- n8n documentation on creating and using custom nodes with OpenAPI integration.