Actions57
- Label Actions
- Project Actions
- Add a Team
- Add a User
- Create
- Create a Kanban Bucket
- Create a Link Share
- Create a Project View
- Delete
- Delete a Kanban Bucket
- Delete a Link Share
- Delete a Project View
- Duplicate
- Get
- Get All Link Shares
- Get All Project Views
- Get All Teams
- Get All Users
- Remove a Team From a Project
- Remove a User From a Project
- Update
- Update a Kanban Bucket
- Update a Project View
- Update a Team's Rights on a Project
- Update a User's Rights on a Project
- Task Actions
- Team Actions
- Webhook Actions
Overview
This node integrates with the Vikunja API to perform various operations on resources such as projects, tasks, labels, teams, and webhooks. Specifically, for the Project resource with the Duplicate operation, it allows users to create a copy of an existing project. This is useful when you want to replicate a project’s structure, settings, or content without manually recreating it.
Common scenarios include:
- Quickly setting up a new project based on an existing template.
- Creating backups or versions of a project before making major changes.
- Duplicating projects for similar workflows or clients.
Example: A user has a project "Marketing Campaign Q1" and wants to duplicate it to start "Marketing Campaign Q2" with the same setup.
Properties
| Name | Meaning |
|---|---|
| Project Title or ID | The project to duplicate. Can be selected from a searchable list of projects or specified by ID. |
| Parent Project Title or ID | (Optional) The parent project under which the duplicated project will be created. Also selectable from a list or by ID. |
Output
The node outputs JSON data representing the duplicated project as returned by the Vikunja API. This typically includes details such as the new project's ID, title, creation date, and other metadata.
If the node supports binary data output, it would relate to any files or attachments associated with the project duplication, but this is not indicated in the provided code.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the node credentials.
- Uses internal helper methods to search and map projects for selection lists.
Troubleshooting
- Invalid Project ID or Not Found: If the specified project ID does not exist, the API will return an error. Ensure the project ID is correct or select from the list.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key and URL are correctly set.
- Permission Issues: The authenticated user must have permission to duplicate projects; otherwise, the API may reject the request.
- Parent Project Errors: If specifying a parent project, ensure it exists and is valid; otherwise, duplication might fail.