# Chaser AI integration on Definable

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

## What this connects

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

Vendor: https://www.chaserhq.com/

## Tools available

**30** tools available. First 12:

- `CHASER_CREATE_CONTACT_PERSON` — 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.
- `CHASER_CREATE_INVOICE` — Create Invoice — Tool to create a new invoice record in the organization. Use after ensuring the customer exists in Chaser.
- `CHASER_CREATE_OVERPAYMENT` — 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.
- `CHASER_DELETE_CONTACT_PERSON` — 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.
- `CHASER_GET_CONTACT_PERSON` — Get Contact Person by ID — 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.
- `CHASER_GET_CREDIT_NOTE_BY_ID` — 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.
- `CHASER_GET_CREDIT_NOTES` — 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.
- `CHASER_GET_CURRENT_ORGANISATION` — 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.
- `CHASER_GET_CUSTOMER_BY_ID` — 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.
- `CHASER_GET_CUSTOMERS` — 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.
- `CHASER_GET_INVOICE` — Get Invoice by ID — 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.
- `CHASER_GET_ORGANIZATION` — Get Organization — Tool to retrieve information about the connected organizations. Use when you need organization IDs, currency, timezone, or legal details before other operations.

## Auth

Auth schemes: `API_KEY`.

## How agents use Chaser

Inside a Definable workflow, Chaser is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Chaser** — the Researcher (GPT-5.5) pulls context from Chaser (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Chaser** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Chaser (create record, post message, draft email).
- **Designer / Engineer → Distributor → Chaser** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Chaser (attach file, open PR comment, post status).

The Verifier checks every Chaser call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- accounting — https://definable.ai/apps/category/accounting/
- proposal & invoice management — https://definable.ai/apps/category/proposal-&-invoice-management/

## Related

- HTML page: https://definable.ai/apps/chaser/
- Same category (accounting): https://definable.ai/apps/category/accounting/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt