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, specifically allowing users to create new time entries within their Scoro account. It is useful for automating time tracking by programmatically adding time logs associated with projects, tasks, or other activities managed in Scoro. For example, a user could automate logging billable hours from a time tracking tool directly into Scoro without manual entry.
Properties
| Name | Meaning |
|---|---|
| Request | A JSON object representing the nested request body used to create a time entry in Scoro. |
The "Request" property expects a JSON structure that matches the Scoro API's requirements for creating a time entry. This allows full flexibility to specify all relevant fields such as start time, end time, description, project ID, task ID, and any custom fields supported by Scoro.
Output
The node outputs JSON data representing the response from the Scoro API after creating the time entry. This typically includes details of the newly created time entry such as its unique ID, timestamps, associated project/task, and any metadata returned by the API.
If the API supports returning binary data (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Scoro API.
- Needs credentials including:
- Base URL of the Scoro instance.
- Company account identifier.
- An API key credential for authentication.
- The node uses these credentials to authenticate and send requests to the Scoro API endpoint.
Troubleshooting
- Unsupported Operation Error: If you select an operation not supported for the "Time Entry" resource, the node will throw an error indicating the operation is unsupported. Ensure you select "Create" when working with time entries.
- Invalid JSON in Request: The "Request" property must contain valid JSON. Malformed JSON will cause parsing errors. Use proper JSON formatting.
- Authentication Failures: Incorrect or missing API credentials will result in authentication errors. Verify your API key and company account ID are correct.
- API Endpoint Issues: Ensure the base URL is correctly set to your Scoro instance URL. Network issues or incorrect URLs will cause request failures.
Links and References
- Scoro API Documentation — Official API docs for understanding the required JSON structure for creating time entries.
- n8n Documentation — General guidance on using n8n nodes and handling JSON input properties.