Scoro icon

Scoro

Interact with the Scoro API

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, the node updates an existing trigger in the Scoro system by sending a JSON object representing the updated request data.

Common scenarios include automating updates to triggers based on workflow conditions or external events, such as modifying alert criteria or scheduled actions within Scoro without manual intervention.

Practical example: Automatically update a trigger's configuration when a related project status changes, ensuring that notifications or automated tasks remain aligned with current project parameters.

Properties

Name Meaning
Trigger Select the trigger to update. You can either choose from a list of existing triggers or specify the trigger ID directly (must be numeric).
Request A JSON object representing the nested request payload containing the fields and values to update the selected trigger.

Output

The node outputs JSON data representing the response from the Scoro API after updating the trigger. This typically includes the updated trigger details confirming the changes made.

If the API supports binary data in responses (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON data.

Dependencies

  • Requires an API key credential for authenticating with the Scoro API.
  • Needs the base URL and company account ID configured in the credentials.
  • The node uses internal helper functions to handle routing and API requests.
  • No additional external dependencies beyond the Scoro API and n8n's credential management.

Troubleshooting

  • Invalid Trigger ID: If the trigger ID is not numeric or does not exist, the node will throw an error. Ensure the trigger ID is correct and numeric.
  • Malformed JSON in Request: The "Request" property expects valid JSON. Invalid JSON syntax will cause parsing errors. Validate JSON before input.
  • Unsupported Operation or Resource: If the operation or resource is not supported, the node throws an error indicating so.
  • Authentication Errors: Missing or incorrect API credentials will result in authentication failures. Verify API key and other credential details.
  • API Endpoint Issues: Incorrect base URL or network issues may cause request failures. Confirm the base URL and network connectivity.

Links and References

Discussion