Actions21
Overview
This node updates a project in the Runn system. It allows users to modify various attributes of an existing project such as its name, confirmation status, budget, client association, and pricing model. The node supports a "dry run" mode to simulate changes without applying them, which is useful for testing or validation before committing updates.
Typical use cases include:
- Adjusting project details after initial creation.
- Correcting or updating budget estimates.
- Changing the client linked to a project.
- Switching the pricing model based on contract changes.
- Testing update logic safely using dry run mode.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the project to update (required). |
| Name | The new name to assign to the project. |
| Is Confirmed? | Boolean flag indicating whether the project is confirmed. |
| Budget | Numeric value representing the project's budget. |
| Client ID | Numeric identifier of the client associated with the project. |
| Pricing Model | The pricing approach for the project. Options: Fixed Price, Time and Materials, Non-Billable. |
| Dry Run | If true, simulates the update without making actual changes in the Runn account. |
| Options | A collection placeholder for additional optional parameters (empty in this context). |
Output
The node outputs an array containing one element per input item, each with a json property holding the updated project data returned from the Runn API. This JSON typically includes the project's updated fields reflecting the changes made.
If the "Dry Run" option is enabled, the output will simulate the update response without modifying any real data.
No binary data output is produced by this node.
Dependencies
- Requires access to the Runn API via an authenticated connection.
- Needs an API key or token configured in n8n credentials to authorize requests.
- The node internally calls helper functions specific to the "projects" resource operations.
Troubleshooting
Common issues:
- Missing or invalid project ID will cause errors since the target project cannot be identified.
- Providing invalid values for properties like budget (non-numeric) or pricing model (unsupported option) may result in API rejections.
- Network or authentication failures can prevent successful API calls.
Error messages:
"Unsupported resource projects"if the resource parameter is incorrect or not handled.- API error messages relayed from Runn, e.g., "Project not found" or "Invalid client ID".
- If "continue on fail" is enabled, errors are returned inside the output JSON under an
errorfield instead of stopping execution.
Resolutions:
- Ensure all required fields, especially the project ID, are correctly set.
- Validate input types and options before running the node.
- Verify API credentials and network connectivity.
- Use the dry run mode to test changes safely.
Links and References
- Runn API Documentation (for detailed API endpoints and data models)
- n8n documentation on creating custom nodes