> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Chaser

The Chaser connector lets your AI agent act in each user's Chaser account. Each user connects their own Chaser API key and secret once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 53 tools.

**Authentication:** API Key and Secret
**Categories:** Accounting & Finance
**Tools:** 53: 20 read, 30 write, 3 destructive
**Users sign in with:** API key
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CHASER)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Chaser connection

   In **AgentKit > Connections**, create a Chaser connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'chaser_contact_person_get',
  toolInput: {
    contact_person_id: '<contact_person_id>',
    customer_id: '<customer_id>',
  },
  connector: 'chaser',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="chaser_contact_person_get",
    tool_input={
        "contact_person_id": "<contact_person_id>",
        "customer_id": "<customer_id>",
    },
    connection_name="chaser",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `chaser_contact_person_get`

Get Contact Person · Read-only

Get one contact person of a customer by its external ID.
Returns the contact's name, email, phone numbers and status.
Use chaser_contact_person_get when you know the contact's external ID. Use chaser_contact_persons_list to list them.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_person_id` (`string`, required): Contact person external_id. Example: CP-001
- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001

Example input: `{"contact_person_id":"<contact_person_id>","customer_id":"<customer_id>"}`

### `chaser_contact_persons_list`

List Contact Persons · Read-only

List the additional contact persons of a customer.
Returns each contact's external_id, name, email, phone numbers and status.
Use chaser_contact_persons_list to see who receives chasers besides the main contact.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001

Example input: `{"customer_id":"<customer_id>"}`

### `chaser_credit_note_get`

Get Credit Note · Read-only

Get one credit note by Chaser ID or external credit_note_id.
Returns the credit note's number, remaining credit, total, status, date and customer.
Use chaser_credit_note_get when you know the ID. Use chaser_credit_notes_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `credit_note_id` (`string`, required): Credit note ID: the Chaser ID or your credit_note_id prefixed with ext_. Example: ext_CN-2001

Example input: `{"credit_note_id":"<credit_note_id>"}`

### `chaser_credit_notes_list`

List Credit Notes · Read-only

List credit notes, filtered by customer, status, currency or date.
Returns a page of credit notes with ID, number, remaining credit, total, status and customer.
Use chaser_credit_notes_list to find credits. Use chaser_credit_note_get to read one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `currency_code` (`string`, optional): Only credit notes in this currency. Example: GBP
- `customer_external_id` (`string`, optional): Only credit notes of the customer with this external_id. Example: CUST-001
- `date_from` (`string`, optional): Only credit notes dated on or after this date (ISO 8601). Example: 2026-10-01
- `date_to` (`string`, optional): Only credit notes dated on or before this date (ISO 8601). Example: 2026-10-31
- `limit` (`number`, optional): Items per page, at most 100. Example: 50. Default: `100`.
- `page` (`number`, optional): Page number, starting from 0. Example: 0. Default: `0`.
- `status` (`string`, optional): Only these statuses, comma-separated. Example: AUTHORISED

Example input: `{}`

### `chaser_customer_get`

Get Customer · Read-only

Get one customer by Chaser ID or external ID.
Returns the customer's details, contact, addresses, groups and balances, plus any additional_fields requested.
Use chaser_customer_get when you know the ID. Use chaser_customers_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `additional_fields` (`array`, optional): Extra fields to include: payment_portal_link, payer_rating and average_days_to_pay. Example: ["payment_portal_link"]

Example input: `{"customer_id":"<customer_id>"}`

### `chaser_customer_notes_list`

List Customer Notes · Read-only

List the notes on a customer.
Returns each note's ID, message, type, reminder date and author.
Use chaser_customer_notes_list to read the collection history. Use chaser_customer_note_create to add a note.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001

Example input: `{"customer_id":"<customer_id>"}`

### `chaser_customers_list`

List Customers · Read-only

List customers, filtered by external ID, company name, contact name or email, or status.
Returns a page of customers with ID, external_id, company name, main contact, status and balances, plus any additional_fields requested.
Use chaser_customers_list to find customers. Use chaser_customer_get to read one by ID.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `additional_fields` (`array`, optional): Extra fields to include: payment_portal_link, payer_rating and average_days_to_pay. Example: ["payer_rating", "average_days_to_pay"]
- `company_name` (`string`, optional): Only customers with exactly this company name. Example: Acme Ltd
- `contact_email_address` (`string`, optional): Only customers whose main contact has exactly this email. Example: accounts@acme.example
- `contact_last_name` (`string`, optional): Only customers whose main contact has this last name. Example: Doe
- `external_id` (`string`, optional): Only these customers: one or more external IDs, comma-separated. Example: CUST-001,CUST-002
- `limit` (`number`, optional): Items per page, at most 100. Example: 50. Default: `100`.
- `page` (`number`, optional): Page number, starting from 0. Example: 0. Default: `0`.
- `status` (`string`, optional): Only customers with this status. One of: ACTIVE, ARCHIVED. Example: ACTIVE. One of: `ACTIVE`, `ARCHIVED`.

Example input: `{}`

### `chaser_invoice_get`

Get Invoice · Read-only

Get one invoice by Chaser ID or external invoice_id.
Returns the invoice's number, status, amounts, dates, customer and chasing state.
Use chaser_invoice_get when you know the ID. Use chaser_invoices_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001

Example input: `{"invoice_id":"<invoice_id>"}`

### `chaser_invoice_history_get`

Get Invoice History · Read-only

Get the chasing history of one invoice: the chasers sent and other events.
Returns the history entries with date, channel and content.
Use chaser_invoice_history_get for one invoice. Use chaser_invoices_history_list across invoices.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001

Example input: `{"invoice_id":"<invoice_id>"}`

### `chaser_invoices_history_list`

List Invoice History · Read-only

List chasing history entries across invoices, optionally for given invoices or a contact.
Returns a page of history entries with invoice, date, channel and content.
Use chaser_invoices_history_list to audit chasers sent. Use chaser_invoice_history_get for one invoice.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_id` (`string`, optional): Only history for this contact ID. Example: cust_123
- `invoice_ids` (`string`, optional): Only history of these invoice_id values, comma-separated. Example: INV-1001,INV-1002
- `invoice_number` (`string`, optional): Only history of these invoice numbers, comma-separated. Example: INV-1001
- `limit` (`number`, optional): Items per page, at most 100. Example: 50. Default: `100`.
- `page` (`number`, optional): Page number, starting from 0. Example: 0. Default: `0`.

Example input: `{}`

### `chaser_invoices_list`

List Invoices · Read-only

List invoices, filtered by customer, status, number, currency, invoice date, due date or amount due.
Returns a page of invoices with ID, invoice_id, number, status, amounts, dates and customer.
Use chaser_invoices_list to find overdue or unpaid invoices. Use chaser_invoice_get to read one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `amount_due_min` (`number`, optional): Only invoices with an amount due greater than this; use 0 for unpaid invoices. Example: 0
- `currency_code` (`string`, optional): Only invoices in this currency. Example: GBP
- `customer_external_id` (`string`, optional): Only invoices of the customer with this external_id. Example: CUST-001
- `date_from` (`string`, optional): Only invoices dated on or after this date (ISO 8601). Example: 2026-10-01
- `date_to` (`string`, optional): Only invoices dated on or before this date (ISO 8601). Example: 2026-10-31
- `due_date_from` (`string`, optional): Only invoices due on or after this date (ISO 8601). Example: 2026-11-01
- `due_date_to` (`string`, optional): Only invoices due on or before this date (ISO 8601); use today's date to find overdue invoices. Example: 2026-11-16
- `invoice_ids` (`string`, optional): Only these invoice_id values (your external IDs), comma-separated. Example: INV-1001,INV-1002
- `invoice_number` (`string`, optional): Only these invoice numbers, comma-separated. Example: INV-1001,INV-1002
- `limit` (`number`, optional): Items per page, at most 100. Example: 50. Default: `100`.
- `page` (`number`, optional): Page number, starting from 0. Example: 0. Default: `0`.
- `status` (`string`, optional): Only invoices with these statuses, comma-separated: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED

Example input: `{}`

### `chaser_organisation_get`

Get Current Organisation · Read-only

Get the organisation the API key belongs to.
Returns the organisation's ID, name, base currency and settings.
Use chaser_organisation_get to check the connection. Use chaser_organisations_list when the key can reach several organisations.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `chaser_organisations_list`

List Organisations · Read-only

List the organisations the API key can access.
Returns each organisation's ID and name.
Use chaser_organisations_list to see every organisation. Use chaser_organisation_get for the current one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `chaser_overpayment_get`

Get Overpayment · Read-only

Get one overpayment by Chaser ID or external overpayment_id.
Returns the overpayment's remaining credit, total, status, date and customer.
Use chaser_overpayment_get when you know the ID. Use chaser_overpayments_list to search.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `overpayment_id` (`string`, required): Overpayment ID: the Chaser ID or your overpayment_id prefixed with ext_. Example: ext_OP-3001

Example input: `{"overpayment_id":"<overpayment_id>"}`

### `chaser_overpayments_list`

List Overpayments · Read-only

List overpayments, filtered by customer, currency or date.
Returns a page of overpayments with ID, remaining credit, total, status and customer.
Use chaser_overpayments_list to find unallocated payments. Use chaser_overpayment_get to read one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `currency_code` (`string`, optional): Only overpayments in this currency. Example: GBP
- `customer_external_id` (`string`, optional): Only overpayments of the customer with this external_id. Example: CUST-001
- `date_from` (`string`, optional): Only overpayments dated on or after this date (ISO 8601). Example: 2026-10-01
- `date_to` (`string`, optional): Only overpayments dated on or before this date (ISO 8601). Example: 2026-10-31
- `limit` (`number`, optional): Items per page, at most 100. Example: 50. Default: `100`.
- `page` (`number`, optional): Page number, starting from 0. Example: 0. Default: `0`.

Example input: `{}`

### `chaser_schedule_get`

Get Schedule · Read-only

Get one chasing schedule by ID.
Returns the schedule's name and steps (when and which template is sent).
Use chaser_schedule_get to inspect a schedule. Use chaser_schedules_list to list them.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `schedule_id` (`string`, required): Schedule ID (sch_...), from chaser_schedules_list. Example: sch_8f2k1

Example input: `{"schedule_id":"<schedule_id>"}`

### `chaser_schedules_list`

List Schedules · Read-only

List the chasing schedules of the organisation.
Returns each schedule's ID and name and its steps.
Use chaser_schedules_list to find a schedule ID for chaser_schedule_assign.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `chaser_tasks_list`

List Tasks · Read-only

List tasks (follow-ups and reminders), filtered by type, status, source, category or due date.
Returns a page of tasks with ID, type, category, status, due date and assignee.
Use chaser_tasks_list to review open work. Use chaser_task_create to add a task.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `category` (`string`, optional): Only tasks in this category. One of: settings, schedule, customer, invoice, custom. Example: customer. One of: `settings`, `schedule`, `customer`, `invoice`, `custom`.
- `due_date_to` (`string`, optional): Only tasks due on or before this date (ISO 8601). Example: 2026-11-30
- `limit` (`number`, optional): Items per page, at most 100. Example: 50. Default: `100`.
- `page` (`number`, optional): Page number, starting from 0. Example: 0. Default: `0`.
- `source` (`string`, optional): Only tasks from this source. One of: manual, scheduled. Example: manual. One of: `manual`, `scheduled`.
- `status` (`string`, optional): Only these statuses, comma-separated: COMPLETED, IN_PROGRESS, PENDING, CANCELLED, OPEN. Example: OPEN,PENDING
- `type` (`string`, optional): Only tasks of this type, for example follow_up. Example: follow_up

Example input: `{}`

### `chaser_template_get`

Get Template · Read-only

Get one message template by ID.
Returns the template's name, channel, subject, text and attachment settings.
Use chaser_template_get before chaser_template_update.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Template ID (tmpl_...), from chaser_templates_list. Example: tmpl_4h7d2

Example input: `{"template_id":"<template_id>"}`

### `chaser_templates_list`

List Templates · Read-only

List the message templates (email, SMS, letter) of the organisation.
Returns each template's ID, name, channel, subject and text.
Use chaser_templates_list to find a template. Use chaser_template_get to read one.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `chaser_contact_person_create`

Create Contact Person · Write

Add a contact person to a customer.
Returns the created contact person.
Use chaser_contact_person_create for one contact. Use chaser_contact_persons_bulk_upsert to sync several.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `external_id` (`string`, required): Your ID for the contact person; used as contact_person_id in other calls. Example: CP-001
- `contact_email_address` (`string`, optional): Email address. Example: sam.lee@acme.example
- `contact_first_name` (`string`, optional): First name. Example: Sam
- `contact_last_name` (`string`, optional): Last name. Example: Lee
- `mobile_number` (`string`, optional): Mobile number. Example: +447700900124
- `phone_number` (`string`, optional): Phone number. Example: +442071234568
- `status` (`string`, optional): ACTIVE or ARCHIVED. One of: ACTIVE, ARCHIVED. Example: ACTIVE. One of: `ACTIVE`, `ARCHIVED`.

Example input: `{"customer_id":"<customer_id>","external_id":"<external_id>"}`

### `chaser_contact_person_update`

Update Contact Person · Write

Update a customer's contact person.
Returns the updated contact person.
Use chaser_contact_person_update to change details or archive a contact.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `contact_person_id` (`string`, required): Contact person external_id. Example: CP-001
- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `contact_email_address` (`string`, optional): Email address. Example: sam.lee@acme.example
- `contact_first_name` (`string`, optional): First name. Example: Sam
- `contact_last_name` (`string`, optional): Last name. Example: Lee
- `external_id` (`string`, optional): Your ID for the contact person; used as contact_person_id in other calls. Example: CP-001
- `mobile_number` (`string`, optional): Mobile number. Example: +447700900124
- `phone_number` (`string`, optional): Phone number. Example: +442071234568
- `status` (`string`, optional): ACTIVE or ARCHIVED. One of: ACTIVE, ARCHIVED. Example: ACTIVE. One of: `ACTIVE`, `ARCHIVED`.

Example input: `{"contact_person_id":"<contact_person_id>","customer_id":"<customer_id>"}`

### `chaser_contact_persons_bulk_upsert`

Bulk Upsert Contact Persons · Write

Create or update several contact persons of one customer in one call, matching by external_id.
Returns the result for each entry.
Use chaser_contact_persons_bulk_upsert to sync a customer's contacts. Use chaser_contact_person_create for one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `entries` (`array`, required): Contact persons to create or update, each shaped like the chaser_contact_person_create body (external_id required). Example: [{"external_id": "CP-001", "contact_first_name": "Sam", "contact_email_address": "sam.lee@acme.example"}]

Example input: `{"customer_id":"<customer_id>","entries":[{"external_id":"CP-001","contact_first_name":"Sam","contact_email_address":"sam.lee@acme.example"}]}`

### `chaser_credit_note_create`

Create Credit Note · Write

Create a credit note for a customer.
Returns the created credit note.
Use chaser_credit_note_create for one credit note. Use chaser_credit_notes_bulk_upsert to sync many.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `credit_note_id` (`string`, required): Your ID for the credit note; unique per organisation. Example: CN-2001
- `credit_note_number` (`string`, required): Credit note number shown to the customer. Example: CN-2001
- `currency_code` (`string`, required): ISO 4217 currency code. Example: GBP
- `customer_external_id` (`string`, required): external_id of the customer the credit note belongs to. Example: CUST-001
- `date` (`string`, required): Credit note date, ISO 8601 date-time. Example: 2026-11-10T00:00:00Z
- `remaining_credit` (`number`, required): Credit not yet allocated to invoices. Example: 150.0
- `status` (`string`, required): Credit note status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED. One of: `DRAFT`, `SUBMITTED`, `AUTHORISED`, `PAID`, `VOIDED`, `DELETED`.
- `total` (`number`, required): Credit note total. Example: 150.0

Example input: `{"credit_note_id":"<credit_note_id>","credit_note_number":"<credit_note_number>","currency_code":"<currency_code>","customer_external_id":"<customer_external_id>","date":"<date>","remaining_credit":150,"status":"DRAFT","total":150}`

### `chaser_credit_note_update`

Update Credit Note · Write

Update a credit note's remaining credit, status or other fields.
Returns the updated credit note.
Use chaser_credit_note_update to change one credit note.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `credit_note_id` (`string`, required): Your ID for the credit note; unique per organisation. Example: CN-2001
- `credit_note_number` (`string`, optional): Credit note number shown to the customer. Example: CN-2001
- `currency_code` (`string`, optional): ISO 4217 currency code. Example: GBP
- `customer_external_id` (`string`, optional): external_id of the customer the credit note belongs to. Example: CUST-001
- `date` (`string`, optional): Credit note date, ISO 8601 date-time. Example: 2026-11-10T00:00:00Z
- `remaining_credit` (`number`, optional): Credit not yet allocated to invoices. Example: 150.0
- `status` (`string`, optional): Credit note status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED. One of: `DRAFT`, `SUBMITTED`, `AUTHORISED`, `PAID`, `VOIDED`, `DELETED`.
- `total` (`number`, optional): Credit note total. Example: 150.0

Example input: `{"credit_note_id":"<credit_note_id>"}`

### `chaser_credit_notes_bulk_upsert`

Bulk Upsert Credit Notes · Write

Create or update up to 100 credit notes in one call. Matches each entry by credit_note_id (or Chaser id) and creates or updates it; up to 100 entries per call.
Returns the result for each entry.
Use chaser_credit_notes_bulk_upsert for a sync. Use chaser_credit_note_create for one record.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `entries` (`array`, required): Credit notes to create or update, each shaped like the chaser_credit_note_create body. Example: [{"credit_note_id": "CN-2001", "credit_note_number": "CN-2001", "remaining_credit": 150, "date": "2026-11-10T00:00:00Z", "status": "AUTHORISED", "total": 150, "currency_code": "GBP", "customer_external_id": "CUST-001"}]

Example input: `{"entries":[{"credit_note_id":"CN-2001","credit_note_number":"CN-2001","remaining_credit":150,"date":"2026-11-10T00:00:00Z","status":"AUTHORISED","total":150,"currency_code":"GBP","customer_external_id":"CUST-001"}]}`

### `chaser_customer_chasing_pause`

Pause Customer Chasing · Write

Pause chasing for a customer; none of their invoices are chased until resumed.
Returns a confirmation.
Use chaser_customer_chasing_pause during a dispute or payment plan. Use chaser_invoice_chasing_pause to pause one invoice only.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001

Example input: `{"customer_id":"<customer_id>"}`

### `chaser_customer_chasing_resume`

Resume Customer Chasing · Write

Resume chasing for a customer; all their invoices are chased again.
Returns a confirmation.
Use chaser_customer_chasing_resume to undo chaser_customer_chasing_pause.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001

Example input: `{"customer_id":"<customer_id>"}`

### `chaser_customer_create`

Create Customer · Write

Create a customer (debtor) to chase.
Returns the created customer with its Chaser ID.
Use chaser_customer_create for one customer. Use chaser_customers_bulk_upsert to sync many at once.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `company_name` (`string`, required): Customer company name. Example: Acme Ltd
- `external_id` (`string`, required): Your ID for the customer, typically the accounting system's contact ID; unique per organisation. Example: CUST-001
- `addresses` (`array`, optional): Addresses, each with address_type (POBOX, Unknown, Delivery or Billing), country, region, city, postal_code and address_line1 to address_line4. Example: [{"address_type": "Billing", "address_line1": "1 High St", "city": "London", "postal_code": "EC1A 1AA", "country": "GB"}]
- `contact_email_address` (`string`, optional): Main contact's email, where chasers are sent. Example: accounts@acme.example
- `contact_first_name` (`string`, optional): Main contact's first name. Example: Jane
- `contact_last_name` (`string`, optional): Main contact's last name. Example: Doe
- `groups` (`array`, optional): Customer groups, each with a name and optional id and status (ACTIVE or ARCHIVED). Example: [{"name": "Key accounts"}]
- `mobile_number` (`string`, optional): Mobile number, used for SMS chasers. Example: +447700900123
- `phone_number` (`string`, optional): Phone number. Example: +442071234567
- `status` (`string`, optional): ACTIVE or ARCHIVED. Defaults to ACTIVE. One of: ACTIVE, ARCHIVED. Example: ACTIVE. One of: `ACTIVE`, `ARCHIVED`.

Example input: `{"company_name":"<company_name>","external_id":"<external_id>"}`

### `chaser_customer_note_create`

Create Customer Note · Write

Add a note to a customer, optionally with a reminder date.
Returns the created note with its ID.
Use chaser_customer_note_create to log a call or promise to pay. Use chaser_customer_note_update to edit a note.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `message` (`string`, required): Note text. Example: Customer promised payment by Friday.
- `reminder_date` (`string`, optional): When to be reminded about the note, ISO 8601 date-time. Example: 2026-11-20T09:00:00Z
- `type` (`string`, optional): Note type label. Example: call

Example input: `{"customer_id":"<customer_id>","message":"<message>"}`

### `chaser_customer_note_update`

Update Customer Note · Write

Update a note's message, type or reminder date.
Returns the updated note.
Use chaser_customer_note_update to edit an existing note. Use chaser_customer_note_create for a new one.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `message` (`string`, required): Note text; send the current text again if you only change the reminder or type. Example: Customer promised payment by Friday.
- `note_id` (`string`, required): Note ID (note_...), from chaser_customer_notes_list. Example: note_aGVsbG8
- `reminder_date` (`string`, optional): When to be reminded about the note, ISO 8601 date-time. Example: 2026-11-20T09:00:00Z
- `type` (`string`, optional): Note type label. Example: call

Example input: `{"customer_id":"<customer_id>","message":"<message>","note_id":"<note_id>"}`

### `chaser_customer_update`

Update Customer · Write

Update a customer's details, contact, status, groups or addresses.
Returns the updated customer.
Use chaser_customer_update to change one customer. Use chaser_customers_bulk_upsert to sync many.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `addresses` (`array`, optional): Addresses, each with address_type (POBOX, Unknown, Delivery or Billing), country, region, city, postal_code and address_line1 to address_line4. Example: [{"address_type": "Billing", "address_line1": "1 High St", "city": "London", "postal_code": "EC1A 1AA", "country": "GB"}]
- `company_name` (`string`, optional): Customer company name. Example: Acme Ltd
- `contact_email_address` (`string`, optional): Main contact's email, where chasers are sent. Example: accounts@acme.example
- `contact_first_name` (`string`, optional): Main contact's first name. Example: Jane
- `contact_last_name` (`string`, optional): Main contact's last name. Example: Doe
- `external_id` (`string`, optional): Your ID for the customer, typically the accounting system's contact ID; unique per organisation. Example: CUST-001
- `groups` (`array`, optional): Customer groups, each with a name and optional id and status (ACTIVE or ARCHIVED). Example: [{"name": "Key accounts"}]
- `mobile_number` (`string`, optional): Mobile number, used for SMS chasers. Example: +447700900123
- `phone_number` (`string`, optional): Phone number. Example: +442071234567
- `status` (`string`, optional): ACTIVE or ARCHIVED. Defaults to ACTIVE. One of: ACTIVE, ARCHIVED. Example: ACTIVE. One of: `ACTIVE`, `ARCHIVED`.

Example input: `{"customer_id":"<customer_id>"}`

### `chaser_customers_bulk_upsert`

Bulk Upsert Customers · Write

Create or update up to 100 customers in one call. Matches each entry by external_id (or Chaser id) and creates or updates it; up to 100 entries per call.
Returns the result for each entry.
Use chaser_customers_bulk_upsert for an initial or periodic sync. Use chaser_customer_create or chaser_customer_update for one record.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `entries` (`array`, required): Customers to create or update, each shaped like the chaser_customer_create body (external_id and company_name required). Example: [{"external_id": "CUST-001", "company_name": "Acme Ltd", "contact_email_address": "accounts@acme.example"}]

Example input: `{"entries":[{"external_id":"CUST-001","company_name":"Acme Ltd","contact_email_address":"accounts@acme.example"}]}`

### `chaser_invoice_chasing_pause`

Pause Invoice Chasing · Write

Pause chasing on one invoice until it is resumed.
Returns a confirmation.
Use chaser_invoice_chasing_pause for a disputed invoice. Use chaser_customer_chasing_pause for all of a customer's invoices.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001

Example input: `{"invoice_id":"<invoice_id>"}`

### `chaser_invoice_chasing_resume`

Resume Invoice Chasing · Write

Resume chasing on one invoice.
Returns a confirmation.
Use chaser_invoice_chasing_resume to undo chaser_invoice_chasing_pause.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001

Example input: `{"invoice_id":"<invoice_id>"}`

### `chaser_invoice_create`

Create Invoice · Write

Create an invoice for Chaser to chase.
Returns the created invoice with its Chaser ID.
Use chaser_invoice_create for one invoice. Use chaser_invoices_bulk_upsert to sync many. The customer must exist first (chaser_customer_create).

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `amount_due` (`number`, required): Amount still owed. Example: 1200.0
- `currency_code` (`string`, required): ISO 4217 currency code, three capital letters. Example: GBP
- `customer_external_id` (`string`, required): external_id of the customer the invoice belongs to. Example: CUST-001
- `date` (`string`, required): Invoice date, ISO 8601 date-time. Example: 2026-11-01T00:00:00Z
- `due_date` (`string`, required): Due date, ISO 8601 date-time. Example: 2026-12-01T00:00:00Z
- `invoice_id` (`string`, required): Your ID for the invoice, typically the accounting system's invoice ID; unique per organisation. Example: INV-1001
- `invoice_number` (`string`, required): Invoice number shown to the customer. Example: INV-1001
- `status` (`string`, required): Invoice status; Chaser chases AUTHORISED invoices with an amount due. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED. One of: `DRAFT`, `SUBMITTED`, `AUTHORISED`, `PAID`, `VOIDED`, `DELETED`.
- `total` (`number`, required): Invoice total including tax. Example: 1200.0
- `amount_paid` (`number`, optional): Amount already paid. Example: 0
- `expect_payment_date` (`string`, optional): Date the customer promised to pay, ISO 8601 date-time. Example: 2026-12-10T00:00:00Z
- `fully_paid_date` (`string`, optional): Date the invoice was fully paid, ISO 8601 date-time. Example: 2026-12-05T00:00:00Z
- `invoice_pdf_link_source` (`string`, optional): Public URL of the invoice PDF, which Chaser fetches and attaches to chasers. Example: https://example.com/invoices/INV-1001.pdf
- `sub_total` (`number`, optional): Invoice total before tax. Example: 1000.0

Example input: `{"amount_due":1200,"currency_code":"<currency_code>","customer_external_id":"<customer_external_id>","date":"<date>","due_date":"<due_date>","invoice_id":"<invoice_id>","invoice_number":"<invoice_number>","status":"DRAFT","total":1200}`

### `chaser_invoice_update`

Update Invoice · Write

Update an invoice's status, amounts, dates or PDF link, for example to record a payment.
Returns the updated invoice.
Use chaser_invoice_update to change one invoice. Use chaser_invoices_bulk_upsert to sync many.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `invoice_id` (`string`, required): Your ID for the invoice, typically the accounting system's invoice ID; unique per organisation. Example: INV-1001
- `amount_due` (`number`, optional): Amount still owed. Example: 1200.0
- `amount_paid` (`number`, optional): Amount already paid. Example: 0
- `currency_code` (`string`, optional): ISO 4217 currency code, three capital letters. Example: GBP
- `customer_external_id` (`string`, optional): external_id of the customer the invoice belongs to. Example: CUST-001
- `date` (`string`, optional): Invoice date, ISO 8601 date-time. Example: 2026-11-01T00:00:00Z
- `due_date` (`string`, optional): Due date, ISO 8601 date-time. Example: 2026-12-01T00:00:00Z
- `expect_payment_date` (`string`, optional): Date the customer promised to pay, ISO 8601 date-time. Example: 2026-12-10T00:00:00Z
- `fully_paid_date` (`string`, optional): Date the invoice was fully paid, ISO 8601 date-time. Example: 2026-12-05T00:00:00Z
- `invoice_number` (`string`, optional): Invoice number shown to the customer. Example: INV-1001
- `invoice_pdf_link_source` (`string`, optional): Public URL of the invoice PDF, which Chaser fetches and attaches to chasers. Example: https://example.com/invoices/INV-1001.pdf
- `status` (`string`, optional): Invoice status; Chaser chases AUTHORISED invoices with an amount due. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED. One of: `DRAFT`, `SUBMITTED`, `AUTHORISED`, `PAID`, `VOIDED`, `DELETED`.
- `sub_total` (`number`, optional): Invoice total before tax. Example: 1000.0
- `total` (`number`, optional): Invoice total including tax. Example: 1200.0

Example input: `{"invoice_id":"<invoice_id>"}`

### `chaser_invoices_bulk_upsert`

Bulk Upsert Invoices · Write

Create or update up to 100 invoices in one call. Matches each entry by invoice_id (or Chaser id) and creates or updates it; up to 100 entries per call.
Returns the result for each entry.
Use chaser_invoices_bulk_upsert for an initial or periodic sync. Use chaser_invoice_create or chaser_invoice_update for one invoice.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `entries` (`array`, required): Invoices to create or update, each shaped like the chaser_invoice_create body. Example: [{"invoice_id": "INV-1001", "invoice_number": "INV-1001", "status": "AUTHORISED", "currency_code": "GBP", "amount_due": 1200, "total": 1200, "date": "2026-11-01T00:00:00Z", "due_date": "2026-12-01T00:00:00Z", "customer_external_id": "CUST-001"}]
- `options` (`object`, optional): Upsert options. invoice_pdf_link.force_refetch makes Chaser download the PDFs again. Example: {"invoice_pdf_link": {"force_refetch": false}}

Example input: `{"entries":[{"invoice_id":"INV-1001","invoice_number":"INV-1001","status":"AUTHORISED","currency_code":"GBP","amount_due":1200,"total":1200,"date":"2026-11-01T00:00:00Z","due_date":"2026-12-01T00:00:00Z","customer_external_id":"CUST-001"}]}`

### `chaser_organisation_chasing_pause`

Pause Organisation Chasing · Write

Pause all chasing for the whole organisation; no invoice is chased until resumed.
Returns a confirmation.
Use chaser_organisation_chasing_pause only to stop every chaser, for example during a system migration. Use the customer or invoice pause tools for narrower pauses.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `chaser_organisation_chasing_resume`

Resume Organisation Chasing · Write

Resume chasing for the whole organisation.
Returns a confirmation.
Use chaser_organisation_chasing_resume to undo chaser_organisation_chasing_pause.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `chaser_organisation_sync`

Sync Organisation · Write

Start a sync of the organisation's data and optionally run recalculation tasks afterwards. Limited to 5 calls per hour.
Returns a confirmation that the sync was queued.
Use chaser_organisation_sync after a bulk upsert so next chase dates and balances are recalculated.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `tasks` (`array`, optional): Tasks to run after the sync, each {"task": NAME} where NAME is CALCULATE_NEXT_CHASES, UPDATE_INVOICE_INSTALMENTS, CALCULATE_CONTACT_BALANCES, VERIFY_CONTACT_CREDIT_LIMIT, CALCULATE_TASK_REMINDERS or CALCULATE_TOTAL_REVENUE. Example: [{"task": "CALCULATE_NEXT_CHASES"}]

Example input: `{}`

### `chaser_overpayment_create`

Create Overpayment · Write

Record an overpayment for a customer.
Returns the created overpayment.
Use chaser_overpayment_create for one record. Use chaser_overpayments_bulk_upsert to sync many.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `currency_code` (`string`, required): ISO 4217 currency code. Example: GBP
- `customer_external_id` (`string`, required): external_id of the customer who overpaid. Example: CUST-001
- `date` (`string`, required): Overpayment date, ISO 8601 date-time. Example: 2026-11-12T00:00:00Z
- `overpayment_id` (`string`, required): Your ID for the overpayment; unique per organisation. Example: OP-3001
- `remaining_credit` (`number`, required): Overpaid amount not yet allocated. Example: 50.0
- `status` (`string`, required): Overpayment status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED. One of: `DRAFT`, `SUBMITTED`, `AUTHORISED`, `PAID`, `VOIDED`, `DELETED`.
- `total` (`number`, required): Overpayment total. Example: 50.0

Example input: `{"currency_code":"<currency_code>","customer_external_id":"<customer_external_id>","date":"<date>","overpayment_id":"<overpayment_id>","remaining_credit":50,"status":"DRAFT","total":50}`

### `chaser_overpayment_update`

Update Overpayment · Write

Update an overpayment's remaining credit, status or other fields.
Returns the updated overpayment.
Use chaser_overpayment_update to change one overpayment.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `overpayment_id` (`string`, required): Your ID for the overpayment; unique per organisation. Example: OP-3001
- `currency_code` (`string`, optional): ISO 4217 currency code. Example: GBP
- `customer_external_id` (`string`, optional): external_id of the customer who overpaid. Example: CUST-001
- `date` (`string`, optional): Overpayment date, ISO 8601 date-time. Example: 2026-11-12T00:00:00Z
- `remaining_credit` (`number`, optional): Overpaid amount not yet allocated. Example: 50.0
- `status` (`string`, optional): Overpayment status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED. One of: `DRAFT`, `SUBMITTED`, `AUTHORISED`, `PAID`, `VOIDED`, `DELETED`.
- `total` (`number`, optional): Overpayment total. Example: 50.0

Example input: `{"overpayment_id":"<overpayment_id>"}`

### `chaser_overpayments_bulk_upsert`

Bulk Upsert Overpayments · Write

Create or update up to 100 overpayments in one call. Matches each entry by overpayment_id (or Chaser id) and creates or updates it; up to 100 entries per call.
Returns the result for each entry.
Use chaser_overpayments_bulk_upsert for a sync. Use chaser_overpayment_create for one record.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `entries` (`array`, required): Overpayments to create or update, each shaped like the chaser_overpayment_create body. Example: [{"overpayment_id": "OP-3001", "remaining_credit": 50, "date": "2026-11-12T00:00:00Z", "status": "AUTHORISED", "total": 50, "currency_code": "GBP", "customer_external_id": "CUST-001"}]

Example input: `{"entries":[{"overpayment_id":"OP-3001","remaining_credit":50,"date":"2026-11-12T00:00:00Z","status":"AUTHORISED","total":50,"currency_code":"GBP","customer_external_id":"CUST-001"}]}`

### `chaser_schedule_assign`

Assign Schedule · Write

Assign a chasing schedule to customers, and optionally to all their invoices.
Returns a confirmation.
Use chaser_schedule_assign to change how customers are chased. Get customer IDs (cust_...) from chaser_customers_list.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `customer_ids` (`array`, required): Chaser customer IDs (cust_...) to assign the schedule to. Example: ["cust_123", "cust_456"]
- `schedule_id` (`string`, required): Schedule ID (sch_...), from chaser_schedules_list. Example: sch_8f2k1
- `update_customer_invoices` (`boolean`, optional): Also switch every invoice of these customers to the new schedule. Example: true

Example input: `{"customer_ids":["cust_123","cust_456"],"schedule_id":"<schedule_id>"}`

### `chaser_schedule_create`

Create Schedule · Write

Create an empty chasing schedule with a name.
Returns the created schedule with its ID.
Use chaser_schedule_create to add a schedule, then configure its steps in the Chaser app and assign it with chaser_schedule_assign.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Schedule name. Example: Large accounts

Example input: `{"name":"<name>"}`

### `chaser_task_create`

Create Task · Write

Create a task, such as a follow-up call reminder, and optionally assign it.
Returns the created task with its ID.
Use chaser_task_create to schedule work for the credit team. Use chaser_task_update to change or complete it.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `category` (`string`, required): Task category. One of: settings, schedule, customer, invoice, custom. Example: customer. One of: `settings`, `schedule`, `customer`, `invoice`, `custom`.
- `type` (`string`, required): Task type, for example follow_up or call_reminder. Example: follow_up
- `assignee` (`string`, optional): Email address of the Chaser user the task is assigned to. Example: ar@yourcompany.example
- `due_date` (`string`, optional): Due date, ISO 8601 date-time. Example: 2026-11-25T09:00:00Z
- `metadata` (`object`, optional): Free-form key-value data stored on the task. Example: {"customer_id": "cust_123"}
- `source` (`string`, optional): manual or scheduled. Defaults to manual. One of: manual, scheduled. Example: manual. One of: `manual`, `scheduled`.
- `status` (`string`, optional): Task status. Defaults to OPEN. One of: COMPLETED, IN_PROGRESS, PENDING, CANCELLED, OPEN. Example: OPEN. One of: `COMPLETED`, `IN_PROGRESS`, `PENDING`, `CANCELLED`, `OPEN`.

Example input: `{"category":"settings","type":"<type>"}`

### `chaser_task_update`

Update Task · Write

Update a task's status, assignee, due date or metadata.
Returns the updated task.
Use chaser_task_update to complete, cancel or reassign a task.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `task_id` (`string`, required): Task ID (task_...), from chaser_tasks_list. Example: task_9x3m1
- `assignee` (`string`, optional): Email address of the Chaser user the task is assigned to. Example: ar@yourcompany.example
- `due_date` (`string`, optional): Due date, ISO 8601 date-time. Example: 2026-11-25T09:00:00Z
- `metadata` (`object`, optional): Free-form key-value data stored on the task. Example: {"customer_id": "cust_123"}
- `status` (`string`, optional): Task status. Defaults to OPEN. One of: COMPLETED, IN_PROGRESS, PENDING, CANCELLED, OPEN. Example: OPEN. One of: `COMPLETED`, `IN_PROGRESS`, `PENDING`, `CANCELLED`, `OPEN`.

Example input: `{"task_id":"<task_id>"}`

### `chaser_template_create`

Create Template · Write

Create a message template for chasers.
Returns the created template with its ID.
Use chaser_template_create to add wording for a schedule step. Use chaser_template_update to change one.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Template name. Example: Friendly reminder
- `attach_invoice` (`boolean`, optional): Attach the invoice PDF. Example: true
- `attach_statement` (`boolean`, optional): Attach a statement of account. Example: false
- `channel` (`string`, optional): Channel the template is sent on: email, sms or letter. Defaults to email. One of: email, sms, letter. Example: email. One of: `email`, `sms`, `letter`.
- `date_format` (`string`, optional): Date format used in the message. Example: DD/MM/YYYY
- `is_multi` (`boolean`, optional): Whether the template covers several invoices at once. Example: false
- `subject` (`string`, optional): Email subject line. Example: Invoice INV-1001 is overdue
- `text` (`string`, optional): Message body; Chaser placeholders such as customer and invoice fields are filled in when sent. Example: Hi, invoice INV-1001 is now overdue. Please pay at your earliest convenience.

Example input: `{"name":"<name>"}`

### `chaser_template_update`

Update Template · Write

Update a message template's name, subject, text, channel or attachments.
Returns the updated template.
Use chaser_template_update to change the wording of chasers.

Read only: no. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Template ID (tmpl_...), from chaser_templates_list. Example: tmpl_4h7d2
- `attach_invoice` (`boolean`, optional): Attach the invoice PDF. Example: true
- `attach_statement` (`boolean`, optional): Attach a statement of account. Example: false
- `channel` (`string`, optional): Channel the template is sent on: email, sms or letter. Defaults to email. One of: email, sms, letter. Example: email. One of: `email`, `sms`, `letter`.
- `date_format` (`string`, optional): Date format used in the message. Example: DD/MM/YYYY
- `is_multi` (`boolean`, optional): Whether the template covers several invoices at once. Example: false
- `name` (`string`, optional): Template name. Example: Friendly reminder
- `subject` (`string`, optional): Email subject line. Example: Invoice INV-1001 is overdue
- `text` (`string`, optional): Message body; Chaser placeholders such as customer and invoice fields are filled in when sent. Example: Hi, invoice INV-1001 is now overdue. Please pay at your earliest convenience.

Example input: `{"template_id":"<template_id>"}`

### `chaser_contact_person_delete`

Delete Contact Person · Destructive

Delete a contact person from a customer.
Returns a confirmation.
Use chaser_contact_person_delete to remove a contact. Use chaser_contact_person_update with status ARCHIVED to keep the record.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `contact_person_id` (`string`, required): Contact person external_id. Example: CP-001
- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001

Example input: `{"contact_person_id":"<contact_person_id>","customer_id":"<customer_id>"}`

### `chaser_customer_note_delete`

Delete Customer Note · Destructive

Delete a note from a customer.
Returns a confirmation.
Use chaser_customer_note_delete to remove a note permanently.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `customer_id` (`string`, required): Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
- `note_id` (`string`, required): Note ID (note_...), from chaser_customer_notes_list. Example: note_aGVsbG8

Example input: `{"customer_id":"<customer_id>","note_id":"<note_id>"}`

### `chaser_template_delete`

Delete Template · Destructive

Delete a message template. A template used in a schedule cannot be deleted.
Returns a confirmation.
Use chaser_template_delete to remove an unused template.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `template_id` (`string`, required): Template ID (tmpl_...), from chaser_templates_list. Example: tmpl_4h7d2

Example input: `{"template_id":"<template_id>"}`

## Related

Other Accounting & Finance connectors ([all 82](/agentkit/connectors/?category=accounting-finance)):

- [QuickBooks](/agentkit/connectors/quickbooks/): Scalekit connector, OAuth, 117 tools
- [Xero](/agentkit/connectors/xero/): Scalekit connector, OAuth, 94 tools
- [Stripe](/agentkit/connectors/stripe/): Scalekit connector, Access token, 178 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
