Cloodo Finance icon

Cloodo Finance

Get data from Cloodo Worksuite API

Actions12

Overview

The node "Cloodo Finance" integrates with the Cloodo Worksuite API to retrieve financial data related to invoices, payments, and recurring transactions. Specifically, for the Recurring - Get operation, it fetches details of a single recurring transaction by its unique ID. This is useful in scenarios where you need to access or verify specific recurring billing or subscription information within your workflows.

Practical examples include:

  • Retrieving details of a customer's recurring payment setup to display or process further.
  • Automating reporting or reconciliation tasks by fetching recurring transaction data.
  • Integrating recurring billing information into other systems or dashboards.

Properties

Name Meaning
ID The unique identifier of the recurring transaction to retrieve. You must provide this ID to get the specific recurring record.

Output

The node outputs JSON data representing the details of the requested recurring transaction. This typically includes fields such as the recurring transaction's ID, amount, frequency, status, start date, next payment date, and any other metadata provided by the Cloodo Worksuite API for recurring entries.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the recurring transaction, but based on the code and properties, the output is purely JSON.

Dependencies

  • Requires an active connection to the Cloodo Worksuite API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for API requests is https://erp-amz.cloodo.com/v4.
  • Proper network access to the API endpoint is necessary.

Troubleshooting

  • Missing or invalid ID: If the ID property is empty or incorrect, the API will likely return an error indicating that the resource was not found. Ensure the ID corresponds to an existing recurring transaction.
  • Authentication errors: If the API key or token is missing or invalid, the node will fail to authenticate. Verify that the API credentials are correctly set up in n8n.
  • Network issues: Timeouts or connectivity problems can cause failures. Check network access and API availability.
  • API changes: If the Cloodo Worksuite API changes its endpoints or response formats, the node may require updates.

Links and References

Discussion