Scoro icon

Scoro

Interact with the Scoro API

Actions46

Overview

This node integrates with the Scoro API, allowing users to perform various operations on different Scoro resources. Specifically, for the Trigger resource and the Update operation, it updates an existing trigger in the Scoro system by sending a JSON object representing the nested request data.

Common scenarios where this node is beneficial include automating updates to triggers based on external events or workflows, such as modifying alert conditions, schedules, or other trigger parameters dynamically without manual intervention.

Practical example:

  • Automatically update a trigger's configuration when a related project status changes.
  • Modify notification triggers based on user input or external system signals.

Properties

Name Meaning
Trigger Select the trigger to update. You can either:
- Choose from a searchable list of existing triggers ("From List" mode).
- Enter the numeric ID of the trigger directly ("By ID" mode).
Request A JSON object representing the nested request payload that defines the updates to apply to the selected trigger. This JSON will be sent as the body of the update request.

Output

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

If the API returns binary data (not indicated here), it would typically represent files or attachments related to the trigger, but this node primarily deals with JSON responses.

Dependencies

  • Requires an active connection to the Scoro API via an API key credential.
  • The node expects credentials containing at least:
    • Base URL of the Scoro instance.
    • Company account identifier.
    • API key for authentication.
  • No additional external dependencies are required beyond the configured Scoro API credentials.

Troubleshooting

  • Invalid Trigger ID: If the trigger ID entered is not numeric, the node will reject it due to validation rules. Ensure the ID is a valid number.
  • Malformed JSON in Request: The "Request" property must contain valid JSON. Invalid JSON syntax will cause parsing errors before sending the request.
  • Unsupported Operation Error: If the operation or resource is incorrectly specified, the node throws an error indicating the operation is unsupported.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify that the API key and base URL are correctly set in the credentials.
  • API Response Errors: Any errors returned by the Scoro API (e.g., invalid fields, permission issues) will be passed through. Review the API response message for details.

Links and References

Discussion