Actions100
- 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
- Teams Actions
Overview
This node integrates with the ChatWoot API to create a new account. It is useful in scenarios where you want to automate the creation of accounts within ChatWoot, such as onboarding new clients or setting up test accounts programmatically. For example, when a new user signs up on your platform, this node can automatically create a corresponding ChatWoot account without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Name | Name of the account to create |
The "Name" property specifies the name for the new account that will be created in ChatWoot.
Output
The node outputs JSON data representing the newly created account details returned by the ChatWoot API. This typically includes information such as the account ID, name, and other metadata provided by the API response.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the ChatWoot API.
- The base URL for the ChatWoot instance must be configured in the node credentials.
- The node uses the ChatWoot REST API endpoint for account creation.
Troubleshooting
- Authentication errors: Ensure the API key and base URL are correctly set in the node credentials.
- Invalid input: The "Name" property must be a non-empty string; otherwise, the API may reject the request.
- API connectivity issues: Verify network access to the ChatWoot server and that the server is operational.
- Unexpected API responses: Check if the ChatWoot API version matches the expected schema used by the node.