Actions46
- Calendar Actions
- ClientProfile Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Status Actions
- Task Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
This node integrates with the Scoro API to perform operations on various resources, including Client Profiles. Specifically, the Update operation for the ClientProfile resource allows users to modify an existing client profile by providing its ID and a JSON object representing the updated data. This is useful in scenarios where client information needs to be kept current, such as updating contact details, preferences, or other profile attributes.
Practical examples include:
- Updating a client's billing address after they move.
- Modifying contact persons or notes related to a client.
- Adjusting client-specific settings or custom fields stored in the profile.
Properties
| Name | Meaning |
|---|---|
| Client Profile | The identifier of the client profile to update. Can be selected from a list of existing profiles or specified directly by numeric ID. |
| Request | A JSON object representing the nested request body containing the fields and values to update in the client profile. |
Details:
- Client Profile supports two modes:
- From List: Select a client profile from a searchable dropdown list.
- By ID: Enter the numeric ID of the client profile manually (must be numeric).
- Request 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. The output is structured as JSON data reflecting the updated client profile or the result of the update operation.
If the API returns binary data (not typical for this operation), it would be included accordingly, but primarily the output is JSON representing the updated resource state.
Dependencies
- Requires an active connection to the Scoro API via an API key credential.
- The node uses the base URL and authentication credentials configured in the node's credentials.
- No additional external dependencies beyond the Scoro API are required.
Troubleshooting
- Invalid Client Profile ID: If the provided client profile ID does not exist or is not numeric, 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.
- API Authentication Errors: If the API key or company account ID is incorrect or missing, the node will fail to authenticate. Verify credentials in the node configuration.
- Unsupported Operation Error: If the operation or resource is not supported, the node throws an explicit error indicating so.
- Network Issues: Connectivity problems with the Scoro API endpoint can cause timeouts or failures.
Links and References
- Scoro API Documentation — Official API docs for reference on client profile fields and update operations.
- n8n Documentation on Creating Custom Nodes for further customization guidance.