Overview
This node interacts with the SePay API to retrieve transaction data. Specifically, the "Get By ID" operation under the "Transaction" resource fetches detailed information about a single transaction by its unique identifier.
Common scenarios where this node is useful include:
- Retrieving detailed information for a specific transaction to verify payment status or details.
- Integrating transaction lookups into automated workflows for reconciliation or reporting.
- Fetching transaction data on-demand based on user input or other triggers.
For example, you might use this node in a workflow that, upon receiving a transaction ID from a form submission, fetches the full transaction details and then updates a database or sends a notification.
Properties
| Name | Meaning |
|---|---|
| Transaction ID | The unique identifier of the transaction to retrieve. This is required for the "Get By ID" operation. |
Output
The node outputs an array of JSON objects representing transactions. For the "Get By ID" operation, the output contains a single transaction object with detailed fields as returned by the SePay API under the transaction key.
Example structure of one item in the output JSON array:
{
"id": "string",
"amount": "number",
"date": "string",
"status": "string",
"reference_number": "string",
...
}
(Note: The exact fields depend on the SePay API response.)
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the SePay API.
- Needs an API authentication token credential configured in n8n (referred to generically as an API key credential).
- Uses the Axios HTTP client library internally to make requests.
Troubleshooting
Common issues:
- Invalid or missing transaction ID will cause the API call to fail.
- Expired or incorrect API token will result in authorization errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors from the SePay API are caught and rethrown with the prefix
SePay API Error:followed by the error message from the API response. - If the error is not from the API response, the original error is thrown.
- Errors from the SePay API are caught and rethrown with the prefix
Resolution tips:
- Verify the transaction ID is correct and exists in SePay.
- Ensure the API token credential is valid and has necessary permissions.
- Check network connectivity and firewall settings.
- Review the error message for specific API error details.
Links and References
- SePay API Documentation (assumed base URL from code; check official docs for details)
- Axios HTTP Client