Actions113
- Accounts Actions
- Account Users Actions
- Agent Bots Actions
- Users Actions
- Inbox API Actions
- Contacts API Actions
- Conversations API Actions
- Messages API Actions
- CSAT Survey Page Actions
- Account Agent Bots Actions
- Agents Actions
- Canned Responses Actions
- Canned Response Actions
- Custom Attributes Actions
- Contacts Actions
- Contact Actions
- Automation Rule Actions
- Help Center Actions
- Conversations Actions
- Conversation Assignment Actions
- Conversation Labels Actions
- Inboxes Actions
- Messages Actions
- Integrations Actions
- Webhooks Actions
- Teams Actions
- Custom Filters Actions
- Reports Actions
Overview
This node operation allows you to add a new category to a Help Center account portal. It is useful for organizing content within a customer support or knowledge base portal by creating categories that group related articles or topics. For example, you might use this node to create categories such as "Product Documentation," "Troubleshooting," or "FAQs" within your Help Center portal, helping users navigate the support content more easily.
Properties
| Name | Meaning |
|---|---|
| Account Id | The numeric ID of the account where the category will be added. |
| Portal Id | The numeric ID of the portal within the account. |
| Description | A textual description of the category. |
| Locale | The locale/language code for the category (e.g., "en", "es"). |
| Name | The name/title of the category. |
| Slug | A URL-friendly identifier for the category. |
| Position | Numeric position to sort the category in the portal list. |
| Associated Category Id | Numeric ID to associate this category with similar categories (e.g., same category in different languages). |
| Parent Category Id | Numeric ID of a parent category to create hierarchical category structures (e.g., subcategories). |
Output
The node outputs JSON data representing the newly created category object returned from the API. This typically includes details such as the category's ID, name, description, locale, slug, position, and any associations or parent-child relationships. The output can be used downstream in workflows to reference the created category or perform further actions.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Help Center service.
- The node uses a base URL configured via credentials to connect to the Help Center API.
- Proper permissions on the account and portal are necessary to create categories.
Troubleshooting
- Missing Required Fields: Ensure that
Account IdandPortal Idare provided and valid numeric values; these are mandatory. - API Authentication Errors: Verify that the API key or authentication token is correctly set up in the node credentials.
- Invalid Locale or Slug: Use supported locale codes and ensure slugs are URL-safe strings.
- Permission Denied: The authenticated user must have rights to modify the specified account and portal.
- Duplicate Slug or Name: Some APIs may reject categories with duplicate slugs or names; check for uniqueness.
- Network Issues: Confirm network connectivity and correct base URL configuration.
Links and References
- Help Center API Documentation (Replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- REST API Best Practices