Scoro icon

Scoro

Interact with the Scoro API
Join our community

Actions50

Overview

This node integrates with the Scoro API to perform various operations on different resources. Specifically, for the Task - Update operation, it allows users to update an existing task in Scoro by specifying the task ID and providing a JSON object representing the fields to update. This is useful in scenarios where task details need to be programmatically modified, such as updating deadlines, statuses, or descriptions based on workflow logic.

Practical examples include:

  • Automatically updating task progress after completion of a related step in a project.
  • Changing task assignments or priorities based on external triggers.
  • Modifying task metadata dynamically from other integrated systems.

Properties

Name Meaning
Task The task to update. Can be selected from a searchable list of tasks or specified by numeric Task ID.
Request A JSON object representing the nested request body containing the fields and values to update on the task.

The Task property supports two modes:

  • From List: Select a task from a searchable dropdown list.
  • By ID: Enter the numeric Task ID directly (must be numeric).

The Request property expects a valid JSON string that will be parsed and sent as the update payload.

Output

The node outputs the response from the Scoro API after attempting to update the task. The output is structured as JSON data reflecting the updated task object or relevant status information returned by the API.

If the API returns binary data (not typical for this operation), it would be included accordingly, but this operation primarily deals with JSON responses.

Dependencies

  • Requires an active connection to the Scoro API via an API key credential.
  • The node uses credentials that must provide:
    • Base URL of the Scoro instance.
    • Company account identifier.
    • API key for authentication.
  • No additional external dependencies beyond the Scoro API and n8n's HTTP request capabilities.

Troubleshooting

  • Invalid Task ID: If the Task ID is not numeric or does not exist, the node will throw an error. Ensure the Task ID is correct and numeric.
  • Malformed JSON in Request: The Request property must contain valid JSON. Invalid JSON will cause parsing errors before sending the request.
  • Unsupported Operation/Resource: If the operation or resource is not supported, the node throws an explicit error indicating so.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Verify API key and company account ID.
  • API Endpoint Issues: Incorrect base URL or network issues can cause request failures. Confirm the base URL and network connectivity.

Links and References

Discussion