Chaser is an accounts receivable automation software that helps businesses automate invoice reminders and get paid faster.
Chaser is an accounts receivable automation software that helps businesses automate invoice reminders and get paid faster. On Nagent, Chaser is exposed as a fully-configurable accounting integration that any agent can call — 30 actions, and API key authentication. No code is required to wire Chaser into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Chaser to automate the kinds of tasks accounting teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Chaser into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Chaser, with input parameters and output schema. Drop these into any step of an agent built in Helix.
CHASER_CREATE_CONTACT_PERSONTool 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
Contact person status: ACTIVE or ARCHIVED
Customer unique identifier. Both "id" and "external_id" can be used. In case of "external_id" please prepend "ext_" prefix (e.g., ext_1234)
Unique external (source system) ID for the contact person
Contact person's phone number (include country code)
Contact person's mobile number (include country code)
Contact person's last name
Contact person's first name
Email address for the contact person
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_CREATE_INVOICETool to create a new invoice record in the organization. Use after ensuring the customer exists in Chaser.
Input parameters
Date the invoice was issued (ISO 8601)
Total amount of the invoice
Status of the invoice
Date payment is due (ISO 8601)
Sub-total amount of the invoice
Amount left to pay on the invoice
External unique identifier for the invoice
Amount paid on the invoice
ISO 4217 currency code, 3 uppercase letters
Invoice reference number (not necessarily unique)
Date the invoice was fully paid (ISO 8601), if applicable
External ID of the associated customer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_CREATE_OVERPAYMENTCreates 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
ISO 8601 timestamp when the overpayment was made.
Total amount of the overpayment.
Status of the overpayment. Valid values: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED.
Three-letter ISO currency code for the overpayment (e.g., USD, EUR, GBP).
External unique identifier for the overpayment.
Remaining credit amount available on the overpayment.
External identifier of the customer linked to this overpayment.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_DELETE_CONTACT_PERSONTool 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
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 unique identifier (external_id)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_CONTACT_PERSONTool 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
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 unique identifier (external_id)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_CREDIT_NOTE_BY_IDRetrieve 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
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_CREDIT_NOTESRetrieves 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
Filter by credit note status.
Filter to credit notes issued on or before this date (YYYY-MM-DD).
Filter to credit notes issued on or after this date (YYYY-MM-DD).
Filter by the external ID of the customer associated with the credit note.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_CURRENT_ORGANISATIONTool 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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_CUSTOMER_BY_IDRetrieve 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
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_CUSTOMERSTool 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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_INVOICETool 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
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_ORGANIZATIONTool to retrieve information about the connected organizations. Use when you need organization IDs, currency, timezone, or legal details before other operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_OVERPAYMENTRetrieve 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
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_GET_STATUSTool to check the status of the Chaser API. Use when you need to verify if the API is operational before making other requests.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_LIST_CONTACT_PERSONSTool 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
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_LIST_INVOICESTool 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
Filter by invoice date. Supported operators: gt, lt, gte, lte, eq, ne. Use ISO date format (YYYY-MM-DD).
Page number, starts from 0.
Number of items per page (maximum 100).
Filter by total invoice amount. Supported operators: gt, lt, gte, lte, eq, ne.
Filter by invoice status. Supported operators: in, nin, eq, ne. Valid statuses: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED.
Filter by due date. Supported operators: gt, lt, gte, lte, eq, ne. Use ISO date format (YYYY-MM-DD).
Filter by subtotal amount. Supported operators: gt, lt, gte, lte, eq, ne.
Filter by amount due. Supported operators: gt, lt, gte, lte, eq, ne.
Filter by invoice ID. Supported operators: in, nin, eq, ne.
Filter by amount paid. Supported operators: gt, lt, gte, lte, eq, ne.
Filter by currency code (3-letter ISO code). Supported operators: in, nin, eq, ne.
Filter by invoice number. Supported operators: in, nin, eq, ne.
Filter by fully paid date. Supported operators: gt, lt, gte, lte, eq, ne. Use ISO date format (YYYY-MM-DD).
Filter by customer external ID. Supported operators: in, nin, eq, ne.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_LIST_OVERPAYMENTSTool 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
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 number to retrieve, starts from 0.
Number of items per page. Maximum is 100.
Filter by total overpayment amount. Supported operators: gt, lt, gte, lte, eq, ne. Example: 'gte:1000' for total >= 1000.
Filter by currency code (ISO 4217). Supported operators: in, nin, eq, ne. Example: 'eq:USD' or 'in:USD,GBP'.
Filter by overpayment external ID. Supported operators: in, nin, eq, ne. Example: 'eq:overpay123' or 'in:overpay1,overpay2'.
Filter by remaining credit amount. Supported operators: gt, lt, gte, lte, eq, ne. Example: 'gte:100' for credit >= 100.
Filter by customer external ID. Supported operators: in, nin, eq, ne. Example: 'eq:cust123' or 'in:cust1,cust2'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_POST_CREDIT_NOTECreates 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
ISO 8601 timestamp when the credit note was issued.
Total amount of the credit note.
Status of the credit note. Note: ACTIVE is not a valid status for creating credit notes.
Three-letter ISO currency code of the credit note.
Unique identifier for the credit note.
Unallocated credit amount remaining on the credit note.
Reference number assigned to the credit note.
External identifier of the customer linked to this credit note.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_POST_CUSTOMERTool to create a new customer record in Chaser. Use after obtaining Basic Auth credentials.
Input parameters
List of customer group objects
Customer visibility status (ACTIVE or ARCHIVED)
List of addresses to display on statements
Unique external (source system) ID for the customer
Name of the company for display in Chaser
Main phone number
Mobile number (include country code)
Contact person's last name
Contact person's first name
Email address to receive Chaser reminders
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_PUT_CREDIT_NOTEUpdate 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
ISO 8601 timestamp when the credit note was issued.
Total amount of the credit note. Must be non-negative.
Status of the credit note. Valid values: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED.
Three-letter ISO currency code of the credit note (e.g., USD, GBP, EUR).
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)
Unallocated credit amount remaining on the credit note. Must be non-negative.
Reference number assigned to the credit note.
External identifier of the customer linked to this credit note.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_PUT_CUSTOMERTool 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
Customer status; either 'ACTIVE' or 'ARCHIVED'
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.
Name of the company associated with the customer
The phone number of the customer
Mobile number including country code (e.g., +447261928377)
Last name of the primary contact
First name of the primary contact
Email address of the primary contact
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_PUT_INVOICEUpdate 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
Invoice issue date in ISO 8601 format
Total invoice amount
Invoice status
Payment due date in ISO 8601 format
List of payments applied to the invoice
Subtotal before tax
Remaining balance due
Internal Chaser invoice ID (e.g., 'inv_abc123'). Use the 'id' field from invoice creation/retrieval responses, NOT the external invoice_id.
Total amount paid
ISO-4217 currency code, e.g., 'USD'
Reference number assigned to the invoice
Date the invoice was fully paid in ISO 8601 format
External ID of the customer to associate
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPDATE_CONTACT_PERSONTool 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
Contact person status; either 'ACTIVE' or 'ARCHIVED'. Default is 'ACTIVE'
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)
External identifier for the contact person
Phone number of the contact person
Mobile number of the contact person including country code
Last name of the contact person (minimum 1 character)
Contact person unique identifier (external_id)
First name of the contact person (minimum 1 character)
Email address of the contact person
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPDATE_OVERPAYMENTTool 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
Date of the overpayment in ISO 8601 date-time format
Total amount of the overpayment
Status values for overpayments in Chaser.
Three-letter ISO 4217 currency code
Alternative field for overpayment ID (if updating this field)
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 amount on the overpayment
External identifier for the customer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPLOAD_INVOICE_PDFUpload 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
PDF file to upload. Must be a valid PDF document.
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
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPSERT_BULK_CUSTOMERSTool 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
Array of customer objects to upsert (max 100 items). Customers are matched by external_id (or id) for updates.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPSERT_CONTACT_PERSONSTool 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
List of contact person entries to insert or update. Maximum 100 entries per request. Matching is done by external_id.
Customer unique identifier. Both 'id' and 'external_id' can be used. For external_id, prepend 'ext_' prefix (e.g., ext_1234)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPSERT_CREDIT_NOTES_BULKTool 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
Array of credit note objects to upsert. Maximum 100 items per request.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPSERT_INVOICESTool 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
Array of invoice objects to upsert. Maximum 100 items. Invoices are matched by invoice_id for updates.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
CHASER_UPSERT_OVERPAYMENTS_BULKTool 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
Array of overpayment objects to upsert. Maximum 100 entries per request. Matching is performed by overpayment_id.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 36 agents privately built on Nagent that already use Chaser.
Build on Nagent
Connect Chaser to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Chaser, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Chaser is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Chaser is connected, you configure its 30 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Chaser steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Chaser event fires, the agent kicks off automatically.
Every Chaser action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Chaser ships with 30 pre-built accounting actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Chaser together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Chaser-based workflows tailored to your business.