Actions20
Overview
The Plutio Project: Update operation node allows you to update an existing project in your Plutio workspace. This is useful for automating the management of projects, such as changing their name, updating the template, modifying custom fields, or adjusting contributors. Typical use cases include synchronizing project data from other systems, batch-updating project details, or integrating Plutio with other workflow tools.
Example scenarios:
- Automatically update project names and templates based on external triggers.
- Add or remove contributors to a project when team assignments change.
- Update custom fields (such as deadlines or statuses) in bulk.
Properties
| Name | Type | Meaning |
|---|---|---|
| Project ID | String | The unique identifier of the project you want to update. Required to specify which project will be modified. |
| Options | Collection | Additional options for the project update: - Project Name: New name for the project. - Template Name or ID: Select or specify a template to apply to the project. |
| Custom Fields | Fixed Collection | Key-value pairs for custom fields associated with the project. Only dates in YYYY-MM-DD format are accepted for date fields. Each entry includes: - Custom Field Name or ID - Value Name or ID |
| Contributors | Fixed Collection | List of users to assign as contributors to the project. Each contributor can be selected by name or ID. |
Output
- The output is a JSON object representing the updated project as returned by the Plutio API.
- If the update is successful, the response contains the project's updated properties (such as name, templateId, customFields, contributors, etc.).
- If there is an error and "Continue On Fail" is enabled, the output will contain an
errorfield with the error message.
Example output:
{
"_id": "project123",
"name": "Updated Project Name",
"templateId": "template456",
"customFields": [
{
"_id": "field789",
"value": "2024-06-01"
}
],
"contributors": ["user1", "user2"],
// ...other project fields
}
Dependencies
- External Service: Requires access to the Plutio API.
- API Credentials: You must configure valid Plutio API credentials (
plutioApi) in n8n. - n8n Configuration: No special environment variables required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Project ID: If the provided Project ID does not exist, the API will return an error.
- Incorrect Custom Field Format: Dates must be in
YYYY-MM-DDformat for custom date fields. - Contributor Not Found: If a contributor's name or ID does not match any user in Plutio, the update may fail or the contributor will not be added.
- Missing Required Fields: Omitting the Project ID will result in failure, as the node cannot determine which project to update.
Error Messages:
"Project not found": Check that the Project ID is correct and exists in your Plutio account."Invalid custom field value": Ensure all custom field values, especially dates, are in the correct format."Contributor not found": Verify that the contributor exists and the name/ID is accurate.
