Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node integrates with the Scoro API, specifically allowing users to update existing projects within their Scoro account. It is useful for automating project management workflows by programmatically modifying project details without manual intervention in the Scoro web interface.
Typical use cases include:
- Updating project metadata such as name, status, or deadlines based on external triggers.
- Synchronizing project information from other systems into Scoro.
- Automating bulk updates to multiple projects via n8n workflows.
For example, a user could trigger this node after receiving updated project data from a CRM system and automatically push those changes to the corresponding project in Scoro.
Properties
| Name | Meaning |
|---|---|
| Project | Select the project to update. You can either choose from a searchable list of projects or enter the numeric Project ID directly. |
| Request | A JSON object representing the nested request body that contains the fields and values to update on the selected project. This allows flexible specification of any updatable project attributes supported by the Scoro API. |
Output
The node outputs JSON data representing the response from the Scoro API after attempting to update the project. This typically includes the updated project details or confirmation of the update operation.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Scoro API using valid credentials including:
- Base URL of the Scoro instance.
- Company account identifier.
- API key for authentication.
These credentials must be configured in n8n prior to using the node.
Troubleshooting
Common issues:
- Invalid or missing project ID: Ensure the project ID is numeric and corresponds to an existing project.
- Malformed JSON in the "Request" property: The JSON must be valid and correctly structured according to Scoro's API requirements.
- Authentication errors: Verify that the API key and company account ID are correct and have sufficient permissions.
Error messages:
"Operation 'update' for resource 'project' is not supported."— This indicates a misconfiguration or unsupported operation; verify the resource and operation parameters.- API errors returned from Scoro will usually include HTTP status codes and error messages indicating the cause (e.g., 401 Unauthorized, 404 Not Found).
Links and References
- Scoro API Documentation — Official documentation for available endpoints and request formats.
- n8n Documentation — General guidance on creating and using custom nodes and managing credentials.