# Chaser

Chaser is an accounts receivable automation software that helps businesses automate invoice reminders and get paid faster.

- **Category:** accounting
- **Auth:** API_KEY
- **Composio Managed App Available?** N/A
- **Tools:** 30
- **Triggers:** 0
- **Slug:** `CHASER`
- **Version:** 20260307_00

## Tools

### Create Contact Person

**Slug:** `CHASER_CREATE_CONTACT_PERSON`

Tool to create a new contact person for a customer in Chaser. Requires customer_id and external_id. Use when adding additional contacts to an existing customer account.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `status` | string ("ACTIVE" | "ARCHIVED") | No | Contact person status: ACTIVE or ARCHIVED |
| `customer_id` | string | Yes | Customer unique identifier. Both "id" and "external_id" can be used. In case of "external_id" please prepend "ext_" prefix (e.g., ext_1234) |
| `external_id` | string | Yes | Unique external (source system) ID for the contact person |
| `phone_number` | string | No | Contact person's phone number (include country code) |
| `mobile_number` | string | No | Contact person's mobile number (include country code) |
| `contact_last_name` | string | No | Contact person's last name |
| `contact_first_name` | string | No | Contact person's first name |
| `contact_email_address` | string | No | Email address for the contact person |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Invoice

**Slug:** `CHASER_CREATE_INVOICE`

Tool to create a new invoice record in the organization. Use after ensuring the customer exists in Chaser.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | Yes | Date the invoice was issued (ISO 8601) |
| `total` | number | Yes | Total amount of the invoice |
| `status` | string ("DRAFT" | "SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | Yes | Status of the invoice |
| `due_date` | string | Yes | Date payment is due (ISO 8601) |
| `sub_total` | number | No | Sub-total amount of the invoice |
| `amount_due` | number | Yes | Amount left to pay on the invoice |
| `invoice_id` | string | Yes | External unique identifier for the invoice |
| `amount_paid` | number | Yes | Amount paid on the invoice |
| `currency_code` | string | Yes | ISO 4217 currency code, 3 uppercase letters |
| `invoice_number` | string | Yes | Invoice reference number (not necessarily unique) |
| `fully_paid_date` | string | No | Date the invoice was fully paid (ISO 8601), if applicable |
| `customer_external_id` | string | Yes | External ID of the associated customer |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Overpayment

**Slug:** `CHASER_CREATE_OVERPAYMENT`

Creates a new overpayment record in Chaser for tracking customer overpayments. Overpayments represent amounts paid by customers in excess of invoice amounts and can be used to offset future invoices. The customer must exist in Chaser before creating an overpayment (use POST /customers first if needed). Valid statuses: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | Yes | ISO 8601 timestamp when the overpayment was made. |
| `total` | number | Yes | Total amount of the overpayment. |
| `status` | string ("DRAFT" | "SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | Yes | Status of the overpayment. Valid values: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. |
| `currency_code` | string | Yes | Three-letter ISO currency code for the overpayment (e.g., USD, EUR, GBP). |
| `overpayment_id` | string | Yes | External unique identifier for the overpayment. |
| `remaining_credit` | number | Yes | Remaining credit amount available on the overpayment. |
| `customer_external_id` | string | Yes | External identifier of the customer linked to this overpayment. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Delete Contact Person

**Slug:** `CHASER_DELETE_CONTACT_PERSON`

Tool to delete a contact person from a customer record in Chaser. Use this when you need to remove a specific contact person associated with a customer. Requires both the customer identifier and the contact person identifier.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `customer_id` | string | Yes | Customer unique identifier. Both 'id' and 'external_id' can be used. In case of 'external_id' please prepend 'ext_' prefix (e.g. ext_1234) |
| `contact_person_id` | string | Yes | Contact person unique identifier (external_id) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Contact Person by ID

**Slug:** `CHASER_GET_CONTACT_PERSON`

Tool to get a specific contact person by ID for a customer. Use when you need to retrieve detailed information about a contact person associated with a customer in Chaser.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `customer_id` | string | Yes | Customer unique identifier. Both "id" and "external_id" can be used. In case of "external_id" please prepend "ext_" prefix (e.g. /v1/customers/ext_1234) |
| `contact_person_id` | string | Yes | Contact person unique identifier (external_id) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Credit Note by ID

**Slug:** `CHASER_GET_CREDIT_NOTE_BY_ID`

Retrieve detailed information for a specific credit note by its ID. Accepts both internal Chaser IDs and external credit note IDs (with 'ext_' prefix). Use when you need to fetch complete details of a single credit note.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `credit_note_id` | string | Yes | Credit Note unique identifier. Both 'id' and 'credit_note_id' can be used. In case of 'credit_note_id' please prepend 'ext_' prefix (e.g., 'ext_1234'). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Credit Notes

**Slug:** `CHASER_GET_CREDIT_NOTES`

Retrieves a list of credit notes from Chaser. Supports filtering by customer, status, and date range. Returns all credit notes if no filters are specified.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `status` | string ("ACTIVE" | "SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | No | Filter by credit note status. |
| `date_to` | string | No | Filter to credit notes issued on or before this date (YYYY-MM-DD). |
| `date_from` | string | No | Filter to credit notes issued on or after this date (YYYY-MM-DD). |
| `customer_external_id` | string | No | Filter by the external ID of the customer associated with the credit note. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Current Organisation

**Slug:** `CHASER_GET_CURRENT_ORGANISATION`

Tool to retrieve information about the current organisation associated with the API credentials. Use when you need the organisation ID, currency, timezone, or legal details for the authenticated account.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Customer by ID

**Slug:** `CHASER_GET_CUSTOMER_BY_ID`

Retrieve detailed information for a specific customer by their Chaser customer ID. Use this after obtaining the customer_id from listing customers or creating a customer. The customer_id is the internal Chaser identifier (e.g., 'cust_abc123'), not the external_id from your source system.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `customer_id` | string | Yes | The unique Chaser customer ID (e.g., 'cust_abc123'). This is the internal Chaser ID returned when creating or listing customers, not the external_id from your source system. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Customers

**Slug:** `CHASER_GET_CUSTOMERS`

Tool to retrieve a list of all customers associated with the organization. Use when you need to display or process complete customer contact and status information.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Invoice by ID

**Slug:** `CHASER_GET_INVOICE`

Tool to retrieve detailed information for a specific invoice by its ID. Use when you need to view invoice details, payment status, or associated customer information.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `invoice_id` | string | Yes | Invoice unique identifier. Both 'id' and 'invoice_id' can be used. In case of 'invoice_id' please prepend 'ext_' prefix (e.g., ext_1234). For internal Chaser ID, use the id directly (e.g., inv_HbpSNsJrr). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Organization

**Slug:** `CHASER_GET_ORGANIZATION`

Tool to retrieve information about the connected organizations. Use when you need organization IDs, currency, timezone, or legal details before other operations.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Overpayment

**Slug:** `CHASER_GET_OVERPAYMENT`

Retrieve detailed information for a specific overpayment by its ID. Use when you need to fetch overpayment details, check remaining credit, or verify overpayment status. Both internal ID (e.g., op_XXX) and external ID with 'ext_' prefix are supported.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `overpayment_id` | string | Yes | Overpayment unique identifier. Both 'id' and 'overpayment_id' can be used. In case of 'overpayment_id' please prepend 'ext_' prefix (e.g., ext_1234 or op_OUJnSE1wQ for internal ID). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Get Status

**Slug:** `CHASER_GET_STATUS`

Tool to check the status of the Chaser API. Use when you need to verify if the API is operational before making other requests.

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Contact Persons

**Slug:** `CHASER_LIST_CONTACT_PERSONS`

Tool to retrieve contact persons for a specific customer. Returns a paginated list of contact persons with their details. Use when you need to get contact information for a customer's representatives.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `customer_id` | string | Yes | Customer unique identifier. Both 'id' and 'external_id' can be used. In case of 'external_id' please prepend 'ext_' prefix (e.g., 'ext_CUST-2026-001' or 'cust_abc123'). |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Invoices

**Slug:** `CHASER_LIST_INVOICES`

Tool to retrieve invoices with pagination and filtering. Use when you need to fetch invoice records from Chaser with support for various filter criteria including status, amounts, dates, and customer information.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Filter by invoice date. Supported operators: gt, lt, gte, lte, eq, ne. Use ISO date format (YYYY-MM-DD). |
| `page` | integer | No | Page number, starts from 0. |
| `limit` | integer | No | Number of items per page (maximum 100). |
| `total` | string | No | Filter by total invoice amount. Supported operators: gt, lt, gte, lte, eq, ne. |
| `status` | string | No | Filter by invoice status. Supported operators: in, nin, eq, ne. Valid statuses: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. |
| `due_date` | string | No | Filter by due date. Supported operators: gt, lt, gte, lte, eq, ne. Use ISO date format (YYYY-MM-DD). |
| `sub_total` | string | No | Filter by subtotal amount. Supported operators: gt, lt, gte, lte, eq, ne. |
| `amount_due` | string | No | Filter by amount due. Supported operators: gt, lt, gte, lte, eq, ne. |
| `invoice_id` | string | No | Filter by invoice ID. Supported operators: in, nin, eq, ne. |
| `amount_paid` | string | No | Filter by amount paid. Supported operators: gt, lt, gte, lte, eq, ne. |
| `currency_code` | string | No | Filter by currency code (3-letter ISO code). Supported operators: in, nin, eq, ne. |
| `invoice_number` | string | No | Filter by invoice number. Supported operators: in, nin, eq, ne. |
| `fully_paid_date` | string | No | Filter by fully paid date. Supported operators: gt, lt, gte, lte, eq, ne. Use ISO date format (YYYY-MM-DD). |
| `customer_external_id` | string | No | Filter by customer external ID. Supported operators: in, nin, eq, ne. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### List Overpayments

**Slug:** `CHASER_LIST_OVERPAYMENTS`

Tool to retrieve overpayments from Chaser with pagination and filtering. Use when you need to list overpayments, check remaining credits, or filter by customer, amount, currency, or date.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Filter by overpayment date (ISO 8601 format). Supported operators: gt, lt, gte, lte, eq, ne. Example: 'gte:2024-01-01' for dates on or after Jan 1, 2024. |
| `page` | integer | No | Page number to retrieve, starts from 0. |
| `limit` | integer | No | Number of items per page. Maximum is 100. |
| `total` | string | No | Filter by total overpayment amount. Supported operators: gt, lt, gte, lte, eq, ne. Example: 'gte:1000' for total >= 1000. |
| `currency_code` | string | No | Filter by currency code (ISO 4217). Supported operators: in, nin, eq, ne. Example: 'eq:USD' or 'in:USD,GBP'. |
| `overpayment_id` | string | No | Filter by overpayment external ID. Supported operators: in, nin, eq, ne. Example: 'eq:overpay123' or 'in:overpay1,overpay2'. |
| `remaining_credit` | string | No | Filter by remaining credit amount. Supported operators: gt, lt, gte, lte, eq, ne. Example: 'gte:100' for credit >= 100. |
| `customer_external_id` | string | No | Filter by customer external ID. Supported operators: in, nin, eq, ne. Example: 'eq:cust123' or 'in:cust1,cust2'. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Credit Note

**Slug:** `CHASER_POST_CREDIT_NOTE`

Creates a new credit note record in Chaser for tracking customer credits. Credit notes represent amounts owed to customers and are used to reduce outstanding invoices. The customer must exist in Chaser before creating a credit note (use POST /customers first). Note: ACTIVE is not a valid status for creating credit notes via API. Valid statuses: SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | Yes | ISO 8601 timestamp when the credit note was issued. |
| `total` | number | Yes | Total amount of the credit note. |
| `status` | string ("SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | Yes | Status of the credit note. Note: ACTIVE is not a valid status for creating credit notes. |
| `currency_code` | string | Yes | Three-letter ISO currency code of the credit note. |
| `credit_note_id` | string | Yes | Unique identifier for the credit note. |
| `remaining_credit` | number | Yes | Unallocated credit amount remaining on the credit note. |
| `credit_note_number` | string | Yes | Reference number assigned to the credit note. |
| `customer_external_id` | string | Yes | External identifier of the customer linked to this credit note. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Create Customer

**Slug:** `CHASER_POST_CUSTOMER`

Tool to create a new customer record in Chaser. Use after obtaining Basic Auth credentials.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `groups` | array | No | List of customer group objects |
| `status` | string ("ACTIVE" | "ARCHIVED") | No | Customer visibility status (ACTIVE or ARCHIVED) |
| `addresses` | array | No | List of addresses to display on statements |
| `external_id` | string | Yes | Unique external (source system) ID for the customer |
| `company_name` | string | Yes | Name of the company for display in Chaser |
| `phone_number` | string | No | Main phone number |
| `mobile_number` | string | No | Mobile number (include country code) |
| `contact_last_name` | string | No | Contact person's last name |
| `contact_first_name` | string | No | Contact person's first name |
| `contact_email_address` | string | No | Email address to receive Chaser reminders |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Credit Note

**Slug:** `CHASER_PUT_CREDIT_NOTE`

Update an existing credit note in Chaser. All fields are optional. Use this to modify credit note details such as amount, status, or customer association.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | ISO 8601 timestamp when the credit note was issued. |
| `total` | number | No | Total amount of the credit note. Must be non-negative. |
| `status` | string ("DRAFT" | "SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | No | Status of the credit note. Valid values: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. |
| `currency_code` | string | No | Three-letter ISO currency code of the credit note (e.g., USD, GBP, EUR). |
| `credit_note_id` | string | Yes | Credit Note unique identifier. Both 'id' and 'credit_note_id' can be used. In case of 'credit_note_id' please prepend 'ext_' prefix (e.g. ext_1234) |
| `remaining_credit` | number | No | Unallocated credit amount remaining on the credit note. Must be non-negative. |
| `credit_note_number` | string | No | Reference number assigned to the credit note. |
| `customer_external_id` | string | No | External identifier of the customer linked to this credit note. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Customer

**Slug:** `CHASER_PUT_CUSTOMER`

Tool to update an existing customer's information using their unique Chaser customer ID. Use after confirming the customer's ID (the 'id' field, not 'externalID'). Example: "Update contactEmailAddress for customer ID cust_abc123."

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `status` | string ("ACTIVE" | "ARCHIVED") | No | Customer status; either 'ACTIVE' or 'ARCHIVED' |
| `customerID` | string | Yes | The unique internal Chaser customer ID (e.g., 'cust_abc123'). This is the 'id' field returned when creating or retrieving a customer, not the externalID. |
| `companyName` | string | No | Name of the company associated with the customer |
| `phoneNumber` | string | No | The phone number of the customer |
| `mobileNumber` | string | No | Mobile number including country code (e.g., +447261928377) |
| `contactLastName` | string | No | Last name of the primary contact |
| `contactFirstName` | string | No | First name of the primary contact |
| `contactEmailAddress` | string | No | Email address of the primary contact |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Invoice

**Slug:** `CHASER_PUT_INVOICE`

Update an existing invoice in Chaser by its internal ID. Use this to modify invoice status, amounts, dates, payments, or customer associations. Requires the internal Chaser invoice ID (e.g., 'inv_abc123') from invoice creation or retrieval responses.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Invoice issue date in ISO 8601 format |
| `total` | number | No | Total invoice amount |
| `status` | string ("DRAFT" | "SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | No | Invoice status |
| `due_date` | string | No | Payment due date in ISO 8601 format |
| `payments` | array | No | List of payments applied to the invoice |
| `sub_total` | number | No | Subtotal before tax |
| `amount_due` | number | No | Remaining balance due |
| `invoice_id` | string | Yes | Internal Chaser invoice ID (e.g., 'inv_abc123'). Use the 'id' field from invoice creation/retrieval responses, NOT the external invoice_id. |
| `amount_paid` | number | No | Total amount paid |
| `currency_code` | string | No | ISO-4217 currency code, e.g., 'USD' |
| `invoice_number` | string | No | Reference number assigned to the invoice |
| `fully_paid_date` | string | No | Date the invoice was fully paid in ISO 8601 format |
| `customer_external_id` | string | No | External ID of the customer to associate |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Contact Person

**Slug:** `CHASER_UPDATE_CONTACT_PERSON`

Tool to update a contact person for a customer in Chaser. Use when you need to modify contact person details such as name, email, or phone numbers.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `status` | string ("ACTIVE" | "ARCHIVED") | No | Contact person status; either 'ACTIVE' or 'ARCHIVED'. Default is 'ACTIVE' |
| `customerID` | string | Yes | Customer unique identifier. Both "id" and "external_id" can be used. In case of "external_id" please prepend "ext_" prefix (e.g. /v1/customers/ext_1234) |
| `externalID` | string | No | External identifier for the contact person |
| `phoneNumber` | string | No | Phone number of the contact person |
| `mobileNumber` | string | No | Mobile number of the contact person including country code |
| `contactLastName` | string | No | Last name of the contact person (minimum 1 character) |
| `contactPersonID` | string | Yes | Contact person unique identifier (external_id) |
| `contactFirstName` | string | No | First name of the contact person (minimum 1 character) |
| `contactEmailAddress` | string | No | Email address of the contact person |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Update Overpayment

**Slug:** `CHASER_UPDATE_OVERPAYMENT`

Tool to update an overpayment record in Chaser. Use when modifying overpayment details such as remaining credit, status, or other fields. All fields except overpayment_id are optional.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `date` | string | No | Date of the overpayment in ISO 8601 date-time format |
| `total` | number | No | Total amount of the overpayment |
| `status` | string ("DRAFT" | "SUBMITTED" | "AUTHORISED" | "PAID" | "VOIDED" | "DELETED") | No | Status values for overpayments in Chaser. |
| `currency_code` | string | No | Three-letter ISO 4217 currency code |
| `overpaymentId` | string | No | Alternative field for overpayment ID (if updating this field) |
| `overpayment_id` | string | Yes | Overpayment unique identifier. Both 'id' and 'overpayment_id' can be used. In case of 'overpayment_id' please prepend 'ext_' prefix (e.g., ext_1234) |
| `remaining_credit` | number | No | Remaining credit amount on the overpayment |
| `customer_external_id` | string | No | External identifier for the customer |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Upload Invoice PDF

**Slug:** `CHASER_UPLOAD_INVOICE_PDF`

Upload a PDF file to an existing invoice in Chaser. Use this to attach invoice documentation. The file must be a valid PDF document and is sent as multipart/form-data.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `file` | object | Yes | PDF file to upload. Must be a valid PDF document. |
| `invoice_id` | string | Yes | Invoice unique identifier. Use the internal 'id' field from the invoice (format: 'inv_xxxxx'). The external invoice_id format is not supported for this endpoint. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Upsert Customers

**Slug:** `CHASER_UPSERT_BULK_CUSTOMERS`

Tool to bulk upsert up to 100 customers in a single operation. Customers are matched by external_id (or id) for updates. Use when you need to create or update multiple customers efficiently.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entries` | array | Yes | Array of customer objects to upsert (max 100 items). Customers are matched by external_id (or id) for updates. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Upsert Contact Persons

**Slug:** `CHASER_UPSERT_CONTACT_PERSONS`

Tool to bulk insert or update contact persons for a customer. Use when you need to create or update multiple contact persons in a single request (up to 100). Matching is done by external_id - existing contacts with the same external_id will be updated, new ones will be inserted.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entries` | array | Yes | List of contact person entries to insert or update. Maximum 100 entries per request. Matching is done by external_id. |
| `customer_id` | string | Yes | Customer unique identifier. Both 'id' and 'external_id' can be used. For external_id, prepend 'ext_' prefix (e.g., ext_1234) |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Upsert Credit Notes

**Slug:** `CHASER_UPSERT_CREDIT_NOTES_BULK`

Tool to bulk upsert up to 100 credit notes in a single request. Matches by credit_note_id (or id). Use when you need to create or update multiple credit notes efficiently in Chaser.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entries` | array | Yes | Array of credit note objects to upsert. Maximum 100 items per request. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Upsert Invoices

**Slug:** `CHASER_UPSERT_INVOICES`

Tool to bulk upsert up to 100 invoices in a single request. Invoices are matched by invoice_id for updates or created if not found. Use when you need to create or update multiple invoices efficiently.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entries` | array | Yes | Array of invoice objects to upsert. Maximum 100 items. Invoices are matched by invoice_id for updates. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |

### Bulk Upsert Overpayments

**Slug:** `CHASER_UPSERT_OVERPAYMENTS_BULK`

Tool to bulk upsert up to 100 overpayments in Chaser, matching by overpayment_id. Use when you need to create or update multiple overpayment records in a single operation.

#### Input Parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `entries` | array | Yes | Array of overpayment objects to upsert. Maximum 100 entries per request. Matching is performed by overpayment_id. |

#### Output

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `data` | string | Yes | Data from the action execution |
| `error` | string | No | Error if any occurred during the execution of the action |
| `successful` | boolean | Yes | Whether or not the action execution was successful or not |