Actions46
- 🏢 PROJECT Actions
- 📋 BOARD Actions
- 📝 CARD Actions
- ➕ Create Card
- 🔍 Get Card
- ✏️ Update Card
- 🗑️ Delete Card
- 🏷️ Add Label to Card
- 🚫 Remove Label from Card
- 👤 Add Member to Card
- 🚫 Remove Member from Card
- ✅ Create Task in Card
- 🔄 Update Task
- 🗑️ Delete Task
- 📎 Create Attachment in Card
- ✏️ Update Attachment
- 🗑️ Delete Attachment
- 📋 Get All Card Actions
- 💬 Create Comment on Card
- ✏️ Update Comment
- 🗑️ Delete Comment
- 👤 USER Actions
Overview
The Planka n8n node with Resource 👤 USER and Operation ➕ Create User allows you to create a new user in your Planka project management system via its API. This operation is useful for automating user onboarding, integrating HR or signup workflows, or batch-creating users from external systems (like CRMs or spreadsheets).
Practical examples:
- Automatically add new employees to Planka when they join your company.
- Sync users from another platform into Planka.
- Bulk-create test users for onboarding or training purposes.
Properties
| Name | Type | Meaning |
|---|---|---|
| String | Email address of the user. Required for account creation and login. | |
| Password | String | Password for the user's account. Required for authentication. |
| Name | String | Full name of the user. |
| Username | String | Unique username for the user within Planka. |
| Phone | String | (Optional) Phone number of the user. |
| Organization | String | (Optional) Organization the user belongs to. |
| Language | String | (Optional) Preferred language of the user. |
| Subscribe to Own Cards | Boolean | Whether the user should be automatically subscribed to cards they create. Default: true. |
| Is Admin | Boolean | Whether the user has administrative privileges. Default: false. |
Output
The output will be a JSON object representing the newly created user as returned by the Planka API. The structure typically includes fields such as:
{
"id": "string",
"name": "string",
"email": "string",
"username": "string",
"phone": "string",
"organization": "string",
"language": "string",
"subscribeToOwnCards": true,
"isAdmin": false,
// ...other fields provided by Planka
}
- The exact structure may include additional metadata or nested objects depending on the Planka API version.
Dependencies
- External Service: Requires access to a running Planka instance with API enabled.
- API Credentials: You must configure n8n credentials for
plankaApi(typically an API token or similar). - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Missing Required Fields: If any required property (Email, Password, Name, Username) is missing, the node will throw an error.
- Duplicate Email/Username: Attempting to create a user with an email or username that already exists will result in an error from the Planka API.
- Invalid Credentials: Incorrect or missing API credentials will cause authentication errors.
- Network Issues: If n8n cannot reach your Planka instance, you'll see connection or timeout errors.
Error messages and resolutions:
"Email is required"or"Username already exists": Ensure all required fields are filled and unique."401 Unauthorized": Check your Planka API credentials in n8n."ECONNREFUSED"or"ENOTFOUND": Verify the Planka API URL and network connectivity.
