Actions50
- Status Actions
- Task Actions
- Calendar Actions
- ClientProfile Actions
- Comment Actions
- Company Actions
- Invoice Actions
- Project Actions
- Role Actions
- Time Entry Actions
- Trigger Actions
- User Actions
Overview
The node integrates with the Scoro API to perform various operations on different resources. Specifically, for the Company - Update operation, it allows users to update details of an existing company in their Scoro account by sending a JSON object representing the changes.
This node is beneficial when automating business workflows that involve managing company data, such as updating company profiles, correcting information, or syncing company details from other systems.
Example use cases:
- Automatically update company contact details after receiving new information.
- Sync company metadata from a CRM system into Scoro.
- Batch update multiple companies' attributes based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Company | Select the company to update. You can either pick from a searchable list of companies or specify the company ID directly (must be numeric). |
| Request | A JSON object representing the nested request body with the fields and values to update for the selected company. This JSON will be sent as the update payload. |
Output
The node outputs the response from the Scoro API after attempting to update the company. The output is structured as JSON containing the updated company data or relevant status information returned by the API.
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 active connection to the Scoro API via an API key credential.
- Needs configuration of the base URL and authentication credentials for Scoro within n8n.
- Uses internal methods to fetch lists of companies for selection (searchable list mode).
Troubleshooting
Common issues:
- Invalid or missing company ID: Ensure the company ID is numeric if entered manually.
- Malformed JSON in the "Request" property: The JSON must be valid; otherwise, parsing errors will occur.
- Authentication failures: Verify that the API key and base URL are correctly configured.
- Unsupported operation or resource: The node throws an error if the specified operation-resource combination is not implemented.
Error messages:
Operation 'update' for resource 'company' is not supported.β This indicates a misconfiguration or unsupported operation.- JSON parsing errors when the "Request" field contains invalid JSON.
- API errors returned from Scoro, which should be checked for details like permission issues or invalid data.
Links and References
- Scoro API Documentation (for detailed API request/response formats)
- n8n documentation on Creating Custom Nodes
- JSON validation tools to verify the "Request" input before usage