Scoro icon

Scoro

Interact with the Scoro API

Actions46

Overview

The node integrates with the Scoro API to perform operations on various resources, including invoices. Specifically, the Invoice - Update operation allows users to update an existing invoice by specifying its ID and providing a JSON object representing the fields to be updated. This is useful in scenarios where invoice details need correction or modification after creation, such as updating billing information, payment status, or line items.

Practical examples:

  • Correcting an invoice amount after discovering a pricing error.
  • Adding notes or metadata to an existing invoice.
  • Changing the invoice status (e.g., from draft to sent).

Properties

Name Meaning
Invoice Select the invoice to update either by choosing from a searchable list of invoices or by entering the numeric Invoice ID directly.
Request A JSON object representing the nested request body containing the fields and values to update on the selected invoice.

Details on "Invoice" property options:

  • From List: Search and select an invoice from a list fetched dynamically.
  • By ID: Enter the numeric ID of the invoice manually (must be numeric).

Example of "Request" JSON value:

{
  "status": "sent",
  "notes": "Updated payment terms"
}

Output

The node outputs the response from the Scoro API after attempting to update the invoice. The output is structured as JSON data reflecting the updated invoice object or an error message if the update failed.

If the API supports binary data for invoices (e.g., PDF attachments), this node does not explicitly handle binary output in the provided code snippet.

Dependencies

  • Requires an active connection to the Scoro API via an API key credential.
  • The node expects credentials that provide:
    • Base URL of the Scoro instance.
    • Company account identifier.
    • API key for authentication.
  • No additional external dependencies are indicated.

Troubleshooting

  • Common issues:

    • Providing a non-numeric Invoice ID when using the "By ID" mode will cause validation errors.
    • Malformed JSON in the "Request" property will cause parsing errors before sending the request.
    • Missing or invalid API credentials will result in authentication failures.
    • Attempting to update an invoice that does not exist or is inaccessible may return an error from the API.

  • Error messages:

    • "Operation 'update' for resource 'invoice' is not supported." — indicates a misconfiguration or unsupported operation/resource combination.
    • Validation error "Invoice ID must be numeric" — ensure the invoice ID input matches the required format.
    • JSON parse errors on the "Request" field — verify the JSON syntax is correct.

Links and References

Discussion