Actions20
- Claim (Case Management API) Actions
- Debtor (Case Management API) Actions
- Info (Case Management API) Actions
- Company (Partner API) Actions
- User (Partner API) Actions
- User Invite (Partner API) Actions
Overview
This node integrates with the Paywise API to manage various resources, including debtors, claims, companies, users, and more. Specifically, for the Debtor (Case Management API) resource with the Get operation, it retrieves detailed information about a specific debtor by their ID. This is useful in scenarios where you need to fetch debtor data for case management, reporting, or further processing within an automation workflow.
Practical examples include:
- Automatically retrieving debtor details when a new claim is created.
- Fetching debtor information to verify identity or status before proceeding with case actions.
- Integrating debtor data into CRM or accounting systems via n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Debtor ID | The unique identifier of the debtor to retrieve. |
| Act on Behalf of Client | Boolean flag indicating whether the request should be made on behalf of a client company. |
| User ID | When acting on behalf of a client, this is the ID of the user to impersonate for the request. |
Output
The node outputs JSON data representing the debtor's details as returned by the Paywise Case Management API. The exact structure depends on the API response but typically includes fields such as debtor name, contact information, status, and related case data.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Paywise API.
- The node expects proper configuration of the Paywise API credentials within n8n.
- Network access to the Paywise API endpoint is necessary.
Troubleshooting
- Missing or invalid Debtor ID: The node requires a valid debtor ID; ensure this property is correctly set.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Act on Behalf of Client issues: If using the "Act on Behalf of Client" option, ensure the User ID is provided and valid.
- API connectivity problems: Check network connectivity and API availability if requests fail.
- Common error messages will relate to missing parameters, unauthorized access, or resource not found; resolving these involves verifying input properties and credentials.