Actions50
- Status Actions
- Task Actions
- Calendar Actions
- ClientProfile Actions
- Comment Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node integrates with the Scoro API, allowing users to perform various operations on different Scoro resources. Specifically, for the Project resource with the Create operation, the node enables creating a new project in Scoro by sending a JSON request body describing the project details.
Common scenarios where this node is beneficial include automating project creation workflows, integrating project management with other systems, or bulk-creating projects based on external data sources.
For example, you could use this node to automatically create a new project when a deal is closed in your CRM, passing project name, company association, and status as part of the request.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body for creating a project. It typically includes fields such as project_name (string), company_id (nullable number), and status (string). The default status is "inprogress". |
Example of the Request property value:
{
"project_name": "New Project",
"company_id": 123,
"status": "inprogress"
}
Output
The node outputs JSON data representing the response from the Scoro API after creating the project. This usually contains details of the newly created project, including its unique identifier and any metadata returned by the API.
If the API supports binary data output (not indicated here), it would be summarized accordingly, but in this case, the output is purely JSON.
Dependencies
- Requires an active connection to the Scoro API.
- Needs an API authentication token and base URL configured via credentials in n8n.
- The node expects the credentials to provide at least:
- Base URL of the Scoro instance.
- Company account ID.
- API key or token for authentication.
Troubleshooting
- Unsupported Operation Error: If you select an operation-resource combination not supported by the node, it will throw an error indicating the operation is unsupported.
- Invalid JSON in Request: Since the request body is parsed from JSON, malformed JSON input will cause parsing errors. Ensure the JSON is valid.
- Authentication Failures: Missing or incorrect API credentials will result in authorization errors. Verify that the API key and base URL are correctly set in the node credentials.
- API Errors: If the Scoro API returns errors (e.g., invalid fields, missing required data), these will be surfaced in the node's output or error messages. Check the request payload against Scoro API documentation.
Links and References
- Scoro API Documentation β Official API reference for understanding available endpoints and request formats.
- n8n Documentation β For general guidance on using and configuring nodes and credentials in n8n.