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 ClientProfile resource and the Update operation, it allows users to update an existing client profile in Scoro by providing the client profile ID and a JSON object representing the updated data.

Common scenarios where this node is beneficial include:

  • Automating updates to client information based on external triggers or workflows.
  • Synchronizing client data from other systems into Scoro.
  • Bulk updating client profiles programmatically without manual intervention.

For example, you could use this node to update a client's contact details or preferences whenever a related event occurs in another system.

Properties

Name Meaning
Client Profile The identifier of the client profile to update. You can select it from a list or specify its numeric ID directly.
Request A JSON object representing the nested request body containing the fields and values to update in the client profile.

The Client Profile property supports two modes:

  • From List: Select a client profile from a searchable list fetched dynamically.
  • By ID: Enter the numeric ID of the client profile manually (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 client profile. This output is available in the json field of the node's output and typically contains the updated client profile data or status information returned by the API.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Scoro API via an API key credential.
  • The node configuration must include the base URL of the Scoro instance and authentication credentials.
  • The node uses internal methods to fetch lists of client profiles for selection when using the "From List" mode.

Troubleshooting

  • Invalid Client Profile ID: If the provided client profile ID is not numeric or does not exist, the node will throw an error. Ensure the 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 Error: If the operation or resource is incorrectly specified, the node will report that the operation is not supported.
  • Authentication Errors: Missing or invalid API credentials will prevent the node from connecting to Scoro. Verify that the API key and base URL are correctly configured.
  • API Response Errors: Any errors returned by the Scoro API (e.g., permission denied, validation errors) will be passed through. Review the API response message for details.

Links and References

Discussion