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, tasks, or settings without manually recreating everything.
Common scenarios include:
- Quickly setting up a new project based on an existing template.
- Creating backups or versions of projects before making major changes.
- Duplicating projects for similar workflows or clients.
Example: You have a project "Website Redesign" and want to start a new project "Website Redesign Q3" with the same tasks and settings. Using this node’s duplicate operation, you can clone the original project and optionally assign a different parent project.
Properties
Name | Meaning |
---|---|
Project Title or ID | The project to duplicate. You can select from a searchable list of projects or specify the project ID directly. |
Parent Project Title or ID | (Optional) The parent project under which the duplicated project will be placed. Select from a list or provide an 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, description, and other metadata.
If the API supports binary data output (not indicated here), it would represent related files or attachments, but this node primarily deals with JSON project data.
Dependencies
- Requires an API key credential for authenticating with the Vikunja API.
- Needs the base URL of the Vikunja instance configured in the credentials.
- Uses internal methods to search projects for selection lists.
Troubleshooting
- Invalid Project ID or Not Found: If the specified project ID does not exist or is incorrect, the API will return an error. Verify the project ID or use the list mode to select a valid project.
- Permission Denied: Ensure the API key has sufficient permissions to read and duplicate projects.
- Parent Project Issues: If specifying a parent project, ensure that the parent project ID is valid and accessible.
- API Connectivity: Check network connectivity and correct API URL configuration if requests fail.
Links and References
- Vikunja API Documentation — Official API docs for understanding project duplication endpoints and parameters.
- Vikunja GitHub Repository — Source code and issues for Vikunja.