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 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.
Common scenarios where this node is beneficial include:
- Automating updates to company information based on external triggers or workflows.
- Synchronizing company data from other systems into Scoro.
- Bulk updating multiple companies' details programmatically.
For example, you could use this node to update a company's address or contact information whenever it changes in your CRM system.
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 containing 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 and typically contains the updated company data or status information returned by the API.
If the API supports binary data in responses (not indicated here), it would be included accordingly, but this node primarily deals with JSON data.
Dependencies
- Requires an active connection to the Scoro API via an API key credential.
- The node expects the base URL and authentication credentials (API key and company account ID) to be configured in the node's credentials.
- No additional external dependencies are required beyond the Scoro API access.
Troubleshooting
- Error: Operation not supported — This occurs if an unsupported resource-operation combination is selected. Ensure "Company" resource and "Update" operation are chosen.
- Invalid Company ID — If specifying the company by ID, ensure the ID is numeric; otherwise, validation will fail.
- Malformed JSON in Request — The "Request" property must contain valid JSON. Invalid JSON will cause parsing errors.
- Authentication Errors — Verify that the API key and base URL credentials are correctly set up and have sufficient permissions.
- API Errors — Any errors returned by the Scoro API (e.g., company not found, permission denied) will be passed through. Check the API response message for details.
Links and References
- Scoro API Documentation (for detailed API endpoints and request formats)
- n8n Documentation on Creating Custom Nodes