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, specifically supporting multiple resources including claims, debtors, companies, users, and more. For the Claim (Case Management API) resource with the List operation, it retrieves a list of claims from the Paywise system.
Typical use cases include:
- Fetching a paginated list of claims for reporting or processing.
- Acting on behalf of a client company to retrieve claims related to that client.
- Integrating claim data into workflows for case management automation.
For example, you might use this node to pull the latest 10 claims starting from an offset of 0, optionally specifying a user ID if acting on behalf of a client.
Properties
| Name | Meaning |
|---|---|
| Limit | Number of claims to return. Determines how many claim records are fetched in one execution. |
| Offset | Number of claims to skip. Useful for pagination to skip a certain number of claims. |
| Act on Behalf of Client | Boolean flag indicating whether the request should be made on behalf of a client company. |
| User ID | The ID of the user to act on behalf of when Act on Behalf of Client is true. |
Output
The output is an array of JSON objects, each representing a claim retrieved from the Paywise Case Management API. Each item contains the full claim data as returned by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Paywise API.
- The node depends on the Paywise API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing an invalid
User IDwhen acting on behalf of a client may result in authorization errors. - Using unsupported values for
LimitorOffsetcould lead to unexpected results or API errors.
Error messages:
"Resource "claim" is not implemented": This indicates the selected resource is not supported by the node; ensure "Claim" is selected."Operation "list" for resource "claim" is not implemented": Indicates the operation is not available for the resource; verify correct operation selection.- Network or API errors will propagate from the underlying API call and should be checked against Paywise API documentation.
Links and References
- Paywise API Documentation
- n8n Documentation on Creating Custom Nodes