Orgo icon

Orgo

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

Actions19

Overview

This node integrates with the Orgo API, a multi-tenant SaaS platform for organizations, to perform various operations on different resources such as users, contacts, events, event registrations, contracts, and payments. Specifically, for the Payment resource with the Get operation, it retrieves detailed information about a single payment by its ID.

Common scenarios where this node is beneficial include:

  • Fetching payment details for record-keeping or auditing.
  • Integrating payment data into workflows for financial reporting.
  • Triggering downstream processes based on payment status or amount.

For example, you might use this node to get the details of a specific payment after a transaction completes, then update your CRM or notify accounting systems.

Properties

Name Meaning
ID The unique identifier of the payment to retrieve. This is a required string input.

Output

The node outputs the payment data in the json field of the output item. The structure corresponds directly to the payment object returned by the Orgo API endpoint /product_payments/{id}.

Typical fields included in the output JSON (based on simplified mapping in other operations) may include:

  • id: Payment ID
  • amount: The amount paid
  • currency: Currency code of the payment
  • status: Current status of the payment
  • paidAt: Timestamp when the payment was made
  • userId: Identifier of the user who made the payment
  • createdAt: Timestamp when the payment record was created

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Orgo API.
  • The node expects the base URL and API token to be configured in the credentials.
  • HTTP requests are made to the Orgo API endpoints using these credentials.

Troubleshooting

  • Missing or invalid ID: If the ID parameter is empty or invalid, the API call will fail. Ensure the ID is correctly provided.
  • Authentication errors: If the API token is missing or incorrect, the request will return authentication errors. Verify the API token in the credentials.
  • Network issues: Connectivity problems to the Orgo API base URL can cause failures. Check network access and API availability.
  • API rate limits or errors: The Orgo API may impose rate limits or return errors for invalid requests. Review error messages and adjust usage accordingly.

If the node throws an error, check the error message for clues, and ensure all required parameters and credentials are properly set.

Links and References

Discussion