Orgo icon

Orgo

Interact with Orgo API - Multi-tenant SaaS platform for organizations

Actions19

Overview

This node interacts with the Orgo API, a multi-tenant SaaS platform for organizations, to manage various organizational resources. Specifically, the Payment - Get Many operation retrieves multiple payment records from the system.

The node fetches a list of payments with options to limit the number of results and choose between simplified or raw output formats. This is useful in scenarios such as financial reporting, auditing, or integrating payment data into other workflows.

Practical examples:

  • Retrieve the latest 50 payment transactions to generate a summary report.
  • Fetch all payment details for reconciliation with accounting software.
  • Use simplified output to quickly display key payment information in dashboards.

Properties

Name Meaning
Output Choose the format of returned data:
- Simplified: Returns key fields only.
- Raw: Returns all available payment data.
Limit Maximum number of payment records to return (minimum 1). Defaults to 50.

Output

The node outputs an array of JSON objects representing payment records.

  • If Output is set to Simplified, each payment object includes key fields:

    • id: Payment identifier
    • amount: Payment amount
    • currency: Currency code
    • status: Payment status
    • paidAt: Date/time when payment was made
    • userId: Identifier of the user who made the payment
    • createdAt: Record creation timestamp

  • If Output is set to Raw, the full payment data as returned by the Orgo API is provided without filtering.

No binary data is produced by this operation.

Dependencies

  • Requires connection to the Orgo API endpoint.
  • Needs an API token credential configured in n8n for authentication.
  • The base URL and API token are obtained from the node credentials.
  • HTTP requests use standard REST methods with JSON payloads.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authentication failures.
    • Exceeding API rate limits may result in errors or throttling.
    • Providing a limit value less than 1 will be rejected.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • "Authentication failed": Check that the API token credential is correctly set.
    • "Invalid limit parameter": Ensure the limit is a positive integer.
    • "Resource not found" or empty results: Verify that payments exist and parameters are correct.
    • "Request timeout": Confirm network stability and API availability.

To resolve errors, verify credentials, input parameters, and network access. Enable "Continue on Fail" in the node settings to handle partial failures gracefully.

Links and References

Discussion