Overview
This node integrates with the Splitwise API to manage expenses and groups. Specifically, for the Expense - Get operation, it retrieves detailed information about a single expense by its ID. This is useful in scenarios where you want to fetch and process specific expense data from Splitwise within an automated workflow, such as generating reports, syncing expenses to accounting software, or triggering notifications based on expense details.
Example use cases:
- Fetching an expense's details after it was created elsewhere.
- Retrieving expense information to verify or audit costs.
- Using expense data to update other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Splitwise API. Options: "API Key" or "OAuth2". |
| Expense ID | The unique numeric identifier of the expense to retrieve. Must be a non-negative number. |
Output
The output JSON contains the full details of the requested expense as returned by the Splitwise API under the json field. This includes fields such as cost, description, currency code, category, group association, and any other metadata related to the expense.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Splitwise API.
- Requires either an API key credential or OAuth2 authentication configured in n8n.
- The base URL used for API requests is
https://secure.splitwise.com/api/v3.0. - The node uses internal helper functions to make authenticated HTTP requests to the Splitwise endpoints.
Troubleshooting
Error: Expense not found or invalid ID
Ensure the provided Expense ID exists and is correct. The ID must be a valid non-negative integer corresponding to an existing expense.Authentication errors
Verify that the API key or OAuth2 credentials are correctly set up and have sufficient permissions to access expense data.API rate limits or connectivity issues
Network problems or hitting API rate limits may cause failures. Check network connectivity and API usage quotas.Unexpected API errors
The node throws errors if the API response contains error messages. Review the error message for details and adjust parameters accordingly.