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 allows users to create (post) new articles in a target system via an API. It is useful for automating content management workflows, such as publishing knowledge base articles, blog posts, or documentation entries programmatically. For example, you could use this node to automatically add new help articles when a support ticket is resolved or to batch upload multiple articles from a CSV file.
Properties
Name | Meaning |
---|---|
Additional Body Fields | Optional fields to include in the article creation request. These include: |
- Content | The main body content of the article. |
- Name | The title or name of the article. |
- Enable Sharing | Boolean flag indicating if the article should have a public URL accessible without login. |
- Folder Id | Numeric ID to associate the article with a specific folder or category. |
- Company Id | Numeric ID to associate the article with a particular company or organization. |
Output
The node outputs JSON data representing the response from the API after creating the article. This typically includes details of the newly created article such as its ID, name, content, sharing status, and associations (folder, company). There is no indication that binary data is output by this node.
Dependencies
- Requires an API key or authentication token configured in n8n credentials to authorize requests.
- Depends on the external API endpoint specified by the base URL credential.
- Uses standard HTTP headers for JSON content type.
Troubleshooting
- Authentication errors: Ensure the API key or authentication token is correctly set up in the node credentials.
- Validation errors: Missing required fields like article name or content may cause the API to reject the request.
- Permission issues: The user associated with the API key must have rights to create articles and assign folders or companies.
- Network errors: Verify connectivity to the API base URL and that it is reachable from the n8n instance.
- Incorrect field types: Provide numeric values for folder_id and company_id; strings or invalid types may cause errors.
Links and References
- Refer to the target system’s API documentation for detailed information on article creation endpoints and field requirements.
- n8n documentation on how to configure API credentials and use HTTP request nodes for similar integrations.