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.
- Tools
- 53
- What they doRead · write · destructive
- 20 · 30 · 320 read30 write3 destructive
- Users sign in with
- API key
Setup
Install the SDK
Terminal window npm install @scalekit-sdk/node dotenvTerminal window pip install scalekit-sdk-python python-dotenvSet your credentials
Add your Scalekit credentials to your
.envfile. Find values in app.scalekit.com > Developers > API Credentials..env SCALEKIT_ENVIRONMENT_URL=<your-environment-url>SCALEKIT_CLIENT_ID=<your-client-id>SCALEKIT_CLIENT_SECRET=<your-client-secret>Create the Chaser connection
In AgentKit > Connections, create a Chaser connection. The name you give it is the
connection_nameyour code passes. See Configure connections.
Tools
Pass the exact name toexecute_toolchaser_contact_person_getGet one contact person of a customer by its external ID.Read-onlyGet Contact Person
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.
Inputs
contact_person_idstringrequired- Contact person external_id. Example: CP-001
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
chaser_contact_persons_listList the additional contact persons of a customer.Read-onlyList Contact Persons
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.
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
chaser_credit_note_getGet one credit note by Chaser ID or external credit_note_id.Read-onlyGet Credit Note
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.
Inputs
credit_note_idstringrequired- Credit note ID: the Chaser ID or your credit_note_id prefixed with ext_. Example: ext_CN-2001
chaser_credit_notes_listList credit notes, filtered by customer, status, currency or date.Read-onlyList Credit Notes
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.
Inputs
currency_codestring- Only credit notes in this currency. Example: GBP
customer_external_idstring- Only credit notes of the customer with this external_id. Example: CUST-001
date_fromstring- Only credit notes dated on or after this date (ISO 8601). Example: 2026-10-01
date_tostring- Only credit notes dated on or before this date (ISO 8601). Example: 2026-10-31
limitnumber- Items per page, at most 100. Example: 50default
100 pagenumber- Page number, starting from 0. Example: 0default
0 statusstring- Only these statuses, comma-separated. Example: AUTHORISED
chaser_customer_getGet one customer by Chaser ID or external ID.Read-onlyGet Customer
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.
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
additional_fieldsarray- Extra fields to include: payment_portal_link, payer_rating and average_days_to_pay. Example: ["payment_portal_link"]
chaser_customer_notes_listList the notes on a customer.Read-onlyList Customer Notes
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.
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
chaser_customers_listList customers, filtered by external ID, company name, contact name or email, or status.Read-onlyList Customers
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.
Inputs
additional_fieldsarray- Extra fields to include: payment_portal_link, payer_rating and average_days_to_pay. Example: ["payer_rating", "average_days_to_pay"]
company_namestring- Only customers with exactly this company name. Example: Acme Ltd
contact_email_addressstring- Only customers whose main contact has exactly this email. Example: accounts@acme.example
contact_last_namestring- Only customers whose main contact has this last name. Example: Doe
external_idstring- Only these customers: one or more external IDs, comma-separated. Example: CUST-001,CUST-002
limitnumber- Items per page, at most 100. Example: 50default
100 pagenumber- Page number, starting from 0. Example: 0default
0 statusstring- Only customers with this status. One of: ACTIVE, ARCHIVED. Example: ACTIVEone of
ACTIVEARCHIVED
chaser_invoice_getGet one invoice by Chaser ID or external invoice_id.Read-onlyGet Invoice
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.
Inputs
invoice_idstringrequired- Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001
chaser_invoice_history_getGet the chasing history of one invoice: the chasers sent and other events.Read-onlyGet Invoice History
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.
Inputs
invoice_idstringrequired- Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001
chaser_invoices_history_listList chasing history entries across invoices, optionally for given invoices or a contact.Read-onlyList Invoice History
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.
Inputs
contact_idstring- Only history for this contact ID. Example: cust_123
invoice_idsstring- Only history of these invoice_id values, comma-separated. Example: INV-1001,INV-1002
invoice_numberstring- Only history of these invoice numbers, comma-separated. Example: INV-1001
limitnumber- Items per page, at most 100. Example: 50default
100 pagenumber- Page number, starting from 0. Example: 0default
0
chaser_invoices_listList invoices, filtered by customer, status, number, currency, invoice date, due date or amount due.Read-onlyList Invoices
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.
Inputs
amount_due_minnumber- Only invoices with an amount due greater than this; use 0 for unpaid invoices. Example: 0
currency_codestring- Only invoices in this currency. Example: GBP
customer_external_idstring- Only invoices of the customer with this external_id. Example: CUST-001
date_fromstring- Only invoices dated on or after this date (ISO 8601). Example: 2026-10-01
date_tostring- Only invoices dated on or before this date (ISO 8601). Example: 2026-10-31
due_date_fromstring- Only invoices due on or after this date (ISO 8601). Example: 2026-11-01
due_date_tostring- Only invoices due on or before this date (ISO 8601); use today's date to find overdue invoices. Example: 2026-11-16
invoice_idsstring- Only these invoice_id values (your external IDs), comma-separated. Example: INV-1001,INV-1002
invoice_numberstring- Only these invoice numbers, comma-separated. Example: INV-1001,INV-1002
limitnumber- Items per page, at most 100. Example: 50default
100 pagenumber- Page number, starting from 0. Example: 0default
0 statusstring- Only invoices with these statuses, comma-separated: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISED
chaser_organisation_getGet the organisation the API key belongs to.Read-onlyGet Current Organisation
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.
Inputs
This tool takes no inputs.
chaser_organisations_listList the organisations the API key can access.Read-onlyList Organisations
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.
Inputs
This tool takes no inputs.
chaser_overpayment_getGet one overpayment by Chaser ID or external overpayment_id.Read-onlyGet Overpayment
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.
Inputs
overpayment_idstringrequired- Overpayment ID: the Chaser ID or your overpayment_id prefixed with ext_. Example: ext_OP-3001
chaser_overpayments_listList overpayments, filtered by customer, currency or date.Read-onlyList Overpayments
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.
Inputs
currency_codestring- Only overpayments in this currency. Example: GBP
customer_external_idstring- Only overpayments of the customer with this external_id. Example: CUST-001
date_fromstring- Only overpayments dated on or after this date (ISO 8601). Example: 2026-10-01
date_tostring- Only overpayments dated on or before this date (ISO 8601). Example: 2026-10-31
limitnumber- Items per page, at most 100. Example: 50default
100 pagenumber- Page number, starting from 0. Example: 0default
0
chaser_schedule_getGet one chasing schedule by ID.Read-onlyGet Schedule
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.
Inputs
schedule_idstringrequired- Schedule ID (sch_...), from chaser_schedules_list. Example: sch_8f2k1
chaser_schedules_listList the chasing schedules of the organisation.Read-onlyList Schedules
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.
Inputs
This tool takes no inputs.
chaser_tasks_listList tasks (follow-ups and reminders), filtered by type, status, source, category or due date.Read-onlyList Tasks
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.
Inputs
categorystring- Only tasks in this category. One of: settings, schedule, customer, invoice, custom. Example: customerone of
settingsschedulecustomerinvoicecustom due_date_tostring- Only tasks due on or before this date (ISO 8601). Example: 2026-11-30
limitnumber- Items per page, at most 100. Example: 50default
100 pagenumber- Page number, starting from 0. Example: 0default
0 sourcestring- Only tasks from this source. One of: manual, scheduled. Example: manualone of
manualscheduled statusstring- Only these statuses, comma-separated: COMPLETED, IN_PROGRESS, PENDING, CANCELLED, OPEN. Example: OPEN,PENDING
typestring- Only tasks of this type, for example follow_up. Example: follow_up
chaser_template_getGet one message template by ID.Read-onlyGet Template
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.
Inputs
template_idstringrequired- Template ID (tmpl_...), from chaser_templates_list. Example: tmpl_4h7d2
chaser_templates_listList the message templates (email, SMS, letter) of the organisation.Read-onlyList Templates
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.
Inputs
This tool takes no inputs.
chaser_contact_person_createAdd a contact person to a customer.WriteCreate Contact Person
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.
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
external_idstringrequired- Your ID for the contact person; used as contact_person_id in other calls. Example: CP-001
contact_email_addressstring- Email address. Example: sam.lee@acme.example
contact_first_namestring- First name. Example: Sam
contact_last_namestring- Last name. Example: Lee
mobile_numberstring- Mobile number. Example: +447700900124
phone_numberstring- Phone number. Example: +442071234568
statusstring- ACTIVE or ARCHIVED. One of: ACTIVE, ARCHIVED. Example: ACTIVEone of
ACTIVEARCHIVED
chaser_contact_person_updateUpdate a customer's contact person.WriteUpdate Contact Person
Update a customer's contact person. Returns the updated contact person. Use chaser_contact_person_update to change details or archive a contact.
- Idempotent
Inputs
contact_person_idstringrequired- Contact person external_id. Example: CP-001
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
contact_email_addressstring- Email address. Example: sam.lee@acme.example
contact_first_namestring- First name. Example: Sam
contact_last_namestring- Last name. Example: Lee
external_idstring- Your ID for the contact person; used as contact_person_id in other calls. Example: CP-001
mobile_numberstring- Mobile number. Example: +447700900124
phone_numberstring- Phone number. Example: +442071234568
statusstring- ACTIVE or ARCHIVED. One of: ACTIVE, ARCHIVED. Example: ACTIVEone of
ACTIVEARCHIVED
chaser_contact_persons_bulk_upsertCreate or update several contact persons of one customer in one call, matching by external_id.WriteBulk Upsert Contact Persons
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.
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
entriesarrayrequired- 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"}]
chaser_credit_note_createCreate a credit note for a customer.WriteCreate Credit Note
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.
Inputs
credit_note_idstringrequired- Your ID for the credit note; unique per organisation. Example: CN-2001
credit_note_numberstringrequired- Credit note number shown to the customer. Example: CN-2001
currency_codestringrequired- ISO 4217 currency code. Example: GBP
customer_external_idstringrequired- external_id of the customer the credit note belongs to. Example: CUST-001
datestringrequired- Credit note date, ISO 8601 date-time. Example: 2026-11-10T00:00:00Z
remaining_creditnumberrequired- Credit not yet allocated to invoices. Example: 150.0
statusstringrequired- Credit note status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISEDone of
DRAFTSUBMITTEDAUTHORISEDPAIDVOIDEDDELETED totalnumberrequired- Credit note total. Example: 150.0
chaser_credit_note_updateUpdate a credit note's remaining credit, status or other fields.WriteUpdate Credit Note
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.
- Idempotent
Inputs
credit_note_idstringrequired- Your ID for the credit note; unique per organisation. Example: CN-2001
credit_note_numberstring- Credit note number shown to the customer. Example: CN-2001
currency_codestring- ISO 4217 currency code. Example: GBP
customer_external_idstring- external_id of the customer the credit note belongs to. Example: CUST-001
datestring- Credit note date, ISO 8601 date-time. Example: 2026-11-10T00:00:00Z
remaining_creditnumber- Credit not yet allocated to invoices. Example: 150.0
statusstring- Credit note status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISEDone of
DRAFTSUBMITTEDAUTHORISEDPAIDVOIDEDDELETED totalnumber- Credit note total. Example: 150.0
chaser_credit_notes_bulk_upsertCreate or update up to 100 credit notes in one call.WriteBulk Upsert Credit Notes
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.
Inputs
entriesarrayrequired- 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"}]
chaser_customer_chasing_pausePause chasing for a customer; none of their invoices are chased until resumed.WritePause Customer Chasing
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.
- Idempotent
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
chaser_customer_chasing_resumeResume chasing for a customer; all their invoices are chased again.WriteResume Customer Chasing
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.
- Idempotent
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
chaser_customer_createCreate a customer (debtor) to chase.WriteCreate Customer
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.
Inputs
company_namestringrequired- Customer company name. Example: Acme Ltd
external_idstringrequired- Your ID for the customer, typically the accounting system's contact ID; unique per organisation. Example: CUST-001
addressesarray- 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_addressstring- Main contact's email, where chasers are sent. Example: accounts@acme.example
contact_first_namestring- Main contact's first name. Example: Jane
contact_last_namestring- Main contact's last name. Example: Doe
groupsarray- Customer groups, each with a name and optional id and status (ACTIVE or ARCHIVED). Example: [{"name": "Key accounts"}]
mobile_numberstring- Mobile number, used for SMS chasers. Example: +447700900123
phone_numberstring- Phone number. Example: +442071234567
statusstring- ACTIVE or ARCHIVED. Defaults to ACTIVE. One of: ACTIVE, ARCHIVED. Example: ACTIVEone of
ACTIVEARCHIVED
chaser_customer_note_createAdd a note to a customer, optionally with a reminder date.WriteCreate Customer Note
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.
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
messagestringrequired- Note text. Example: Customer promised payment by Friday.
reminder_datestring- When to be reminded about the note, ISO 8601 date-time. Example: 2026-11-20T09:00:00Z
typestring- Note type label. Example: call
chaser_customer_note_updateUpdate a note's message, type or reminder date.WriteUpdate Customer Note
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.
- Idempotent
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
messagestringrequired- Note text; send the current text again if you only change the reminder or type. Example: Customer promised payment by Friday.
note_idstringrequired- Note ID (note_...), from chaser_customer_notes_list. Example: note_aGVsbG8
reminder_datestring- When to be reminded about the note, ISO 8601 date-time. Example: 2026-11-20T09:00:00Z
typestring- Note type label. Example: call
chaser_customer_updateUpdate a customer's details, contact, status, groups or addresses.WriteUpdate Customer
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.
- Idempotent
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
addressesarray- 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_namestring- Customer company name. Example: Acme Ltd
contact_email_addressstring- Main contact's email, where chasers are sent. Example: accounts@acme.example
contact_first_namestring- Main contact's first name. Example: Jane
contact_last_namestring- Main contact's last name. Example: Doe
external_idstring- Your ID for the customer, typically the accounting system's contact ID; unique per organisation. Example: CUST-001
groupsarray- Customer groups, each with a name and optional id and status (ACTIVE or ARCHIVED). Example: [{"name": "Key accounts"}]
mobile_numberstring- Mobile number, used for SMS chasers. Example: +447700900123
phone_numberstring- Phone number. Example: +442071234567
statusstring- ACTIVE or ARCHIVED. Defaults to ACTIVE. One of: ACTIVE, ARCHIVED. Example: ACTIVEone of
ACTIVEARCHIVED
chaser_customers_bulk_upsertCreate or update up to 100 customers in one call.WriteBulk Upsert Customers
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.
Inputs
entriesarrayrequired- 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"}]
chaser_invoice_chasing_pausePause chasing on one invoice until it is resumed.WritePause Invoice Chasing
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.
- Idempotent
Inputs
invoice_idstringrequired- Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001
chaser_invoice_chasing_resumeResume chasing on one invoice.WriteResume Invoice Chasing
Resume chasing on one invoice. Returns a confirmation. Use chaser_invoice_chasing_resume to undo chaser_invoice_chasing_pause.
- Idempotent
Inputs
invoice_idstringrequired- Invoice ID: the Chaser ID (inv_...) or your invoice_id prefixed with ext_ (for example ext_INV-1001). Example: ext_INV-1001
chaser_invoice_createCreate an invoice for Chaser to chase.WriteCreate Invoice
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).
Inputs
amount_duenumberrequired- Amount still owed. Example: 1200.0
currency_codestringrequired- ISO 4217 currency code, three capital letters. Example: GBP
customer_external_idstringrequired- external_id of the customer the invoice belongs to. Example: CUST-001
datestringrequired- Invoice date, ISO 8601 date-time. Example: 2026-11-01T00:00:00Z
due_datestringrequired- Due date, ISO 8601 date-time. Example: 2026-12-01T00:00:00Z
invoice_idstringrequired- Your ID for the invoice, typically the accounting system's invoice ID; unique per organisation. Example: INV-1001
invoice_numberstringrequired- Invoice number shown to the customer. Example: INV-1001
statusstringrequired- Invoice status; Chaser chases AUTHORISED invoices with an amount due. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISEDone of
DRAFTSUBMITTEDAUTHORISEDPAIDVOIDEDDELETED totalnumberrequired- Invoice total including tax. Example: 1200.0
amount_paidnumber- Amount already paid. Example: 0
expect_payment_datestring- Date the customer promised to pay, ISO 8601 date-time. Example: 2026-12-10T00:00:00Z
fully_paid_datestring- Date the invoice was fully paid, ISO 8601 date-time. Example: 2026-12-05T00:00:00Z
invoice_pdf_link_sourcestring- Public URL of the invoice PDF, which Chaser fetches and attaches to chasers. Example: https://example.com/invoices/INV-1001.pdf
sub_totalnumber- Invoice total before tax. Example: 1000.0
chaser_invoice_updateUpdate an invoice's status, amounts, dates or PDF link, for example to record a payment.WriteUpdate Invoice
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.
- Idempotent
Inputs
invoice_idstringrequired- Your ID for the invoice, typically the accounting system's invoice ID; unique per organisation. Example: INV-1001
amount_duenumber- Amount still owed. Example: 1200.0
amount_paidnumber- Amount already paid. Example: 0
currency_codestring- ISO 4217 currency code, three capital letters. Example: GBP
customer_external_idstring- external_id of the customer the invoice belongs to. Example: CUST-001
datestring- Invoice date, ISO 8601 date-time. Example: 2026-11-01T00:00:00Z
due_datestring- Due date, ISO 8601 date-time. Example: 2026-12-01T00:00:00Z
expect_payment_datestring- Date the customer promised to pay, ISO 8601 date-time. Example: 2026-12-10T00:00:00Z
fully_paid_datestring- Date the invoice was fully paid, ISO 8601 date-time. Example: 2026-12-05T00:00:00Z
invoice_numberstring- Invoice number shown to the customer. Example: INV-1001
invoice_pdf_link_sourcestring- Public URL of the invoice PDF, which Chaser fetches and attaches to chasers. Example: https://example.com/invoices/INV-1001.pdf
statusstring- Invoice status; Chaser chases AUTHORISED invoices with an amount due. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISEDone of
DRAFTSUBMITTEDAUTHORISEDPAIDVOIDEDDELETED sub_totalnumber- Invoice total before tax. Example: 1000.0
totalnumber- Invoice total including tax. Example: 1200.0
chaser_invoices_bulk_upsertCreate or update up to 100 invoices in one call.WriteBulk Upsert Invoices
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.
Inputs
entriesarrayrequired- 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"}]
optionsobject- Upsert options. invoice_pdf_link.force_refetch makes Chaser download the PDFs again. Example: {"invoice_pdf_link": {"force_refetch": false}}
chaser_organisation_chasing_pausePause all chasing for the whole organisation; no invoice is chased until resumed.WritePause Organisation Chasing
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.
- Idempotent
Inputs
This tool takes no inputs.
chaser_organisation_chasing_resumeResume chasing for the whole organisation.WriteResume Organisation Chasing
Resume chasing for the whole organisation. Returns a confirmation. Use chaser_organisation_chasing_resume to undo chaser_organisation_chasing_pause.
- Idempotent
Inputs
This tool takes no inputs.
chaser_organisation_syncStart a sync of the organisation's data and optionally run recalculation tasks afterwards.WriteSync Organisation
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.
Inputs
tasksarray- 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"}]
chaser_overpayment_createRecord an overpayment for a customer.WriteCreate Overpayment
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.
Inputs
currency_codestringrequired- ISO 4217 currency code. Example: GBP
customer_external_idstringrequired- external_id of the customer who overpaid. Example: CUST-001
datestringrequired- Overpayment date, ISO 8601 date-time. Example: 2026-11-12T00:00:00Z
overpayment_idstringrequired- Your ID for the overpayment; unique per organisation. Example: OP-3001
remaining_creditnumberrequired- Overpaid amount not yet allocated. Example: 50.0
statusstringrequired- Overpayment status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISEDone of
DRAFTSUBMITTEDAUTHORISEDPAIDVOIDEDDELETED totalnumberrequired- Overpayment total. Example: 50.0
chaser_overpayment_updateUpdate an overpayment's remaining credit, status or other fields.WriteUpdate Overpayment
Update an overpayment's remaining credit, status or other fields. Returns the updated overpayment. Use chaser_overpayment_update to change one overpayment.
- Idempotent
Inputs
overpayment_idstringrequired- Your ID for the overpayment; unique per organisation. Example: OP-3001
currency_codestring- ISO 4217 currency code. Example: GBP
customer_external_idstring- external_id of the customer who overpaid. Example: CUST-001
datestring- Overpayment date, ISO 8601 date-time. Example: 2026-11-12T00:00:00Z
remaining_creditnumber- Overpaid amount not yet allocated. Example: 50.0
statusstring- Overpayment status. One of: DRAFT, SUBMITTED, AUTHORISED, PAID, VOIDED, DELETED. Example: AUTHORISEDone of
DRAFTSUBMITTEDAUTHORISEDPAIDVOIDEDDELETED totalnumber- Overpayment total. Example: 50.0
chaser_overpayments_bulk_upsertCreate or update up to 100 overpayments in one call.WriteBulk Upsert Overpayments
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.
Inputs
entriesarrayrequired- 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"}]
chaser_schedule_assignAssign a chasing schedule to customers, and optionally to all their invoices.WriteAssign Schedule
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.
- Idempotent
Inputs
customer_idsarrayrequired- Chaser customer IDs (cust_...) to assign the schedule to. Example: ["cust_123", "cust_456"]
schedule_idstringrequired- Schedule ID (sch_...), from chaser_schedules_list. Example: sch_8f2k1
update_customer_invoicesboolean- Also switch every invoice of these customers to the new schedule. Example: true
chaser_schedule_createCreate an empty chasing schedule with a name.WriteCreate Schedule
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.
Inputs
namestringrequired- Schedule name. Example: Large accounts
chaser_task_createCreate a task, such as a follow-up call reminder, and optionally assign it.WriteCreate Task
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.
Inputs
categorystringrequired- Task category. One of: settings, schedule, customer, invoice, custom. Example: customerone of
settingsschedulecustomerinvoicecustom typestringrequired- Task type, for example follow_up or call_reminder. Example: follow_up
assigneestring- Email address of the Chaser user the task is assigned to. Example: ar@yourcompany.example
due_datestring- Due date, ISO 8601 date-time. Example: 2026-11-25T09:00:00Z
metadataobject- Free-form key-value data stored on the task. Example: {"customer_id": "cust_123"}
sourcestring- manual or scheduled. Defaults to manual. One of: manual, scheduled. Example: manualone of
manualscheduled statusstring- Task status. Defaults to OPEN. One of: COMPLETED, IN_PROGRESS, PENDING, CANCELLED, OPEN. Example: OPENone of
COMPLETEDIN_PROGRESSPENDINGCANCELLEDOPEN
chaser_task_updateUpdate a task's status, assignee, due date or metadata.WriteUpdate Task
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.
- Idempotent
Inputs
task_idstringrequired- Task ID (task_...), from chaser_tasks_list. Example: task_9x3m1
assigneestring- Email address of the Chaser user the task is assigned to. Example: ar@yourcompany.example
due_datestring- Due date, ISO 8601 date-time. Example: 2026-11-25T09:00:00Z
metadataobject- Free-form key-value data stored on the task. Example: {"customer_id": "cust_123"}
statusstring- Task status. Defaults to OPEN. One of: COMPLETED, IN_PROGRESS, PENDING, CANCELLED, OPEN. Example: OPENone of
COMPLETEDIN_PROGRESSPENDINGCANCELLEDOPEN
chaser_template_createCreate a message template for chasers.WriteCreate Template
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.
Inputs
namestringrequired- Template name. Example: Friendly reminder
attach_invoiceboolean- Attach the invoice PDF. Example: true
attach_statementboolean- Attach a statement of account. Example: false
channelstring- Channel the template is sent on: email, sms or letter. Defaults to email. One of: email, sms, letter. Example: emailone of
emailsmsletter date_formatstring- Date format used in the message. Example: DD/MM/YYYY
is_multiboolean- Whether the template covers several invoices at once. Example: false
subjectstring- Email subject line. Example: Invoice INV-1001 is overdue
textstring- 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.
chaser_template_updateUpdate a message template's name, subject, text, channel or attachments.WriteUpdate Template
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.
- Idempotent
Inputs
template_idstringrequired- Template ID (tmpl_...), from chaser_templates_list. Example: tmpl_4h7d2
attach_invoiceboolean- Attach the invoice PDF. Example: true
attach_statementboolean- Attach a statement of account. Example: false
channelstring- Channel the template is sent on: email, sms or letter. Defaults to email. One of: email, sms, letter. Example: emailone of
emailsmsletter date_formatstring- Date format used in the message. Example: DD/MM/YYYY
is_multiboolean- Whether the template covers several invoices at once. Example: false
namestring- Template name. Example: Friendly reminder
subjectstring- Email subject line. Example: Invoice INV-1001 is overdue
textstring- 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.
chaser_contact_person_deleteDelete a contact person from a customer.DestructiveDelete Contact Person
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.
- Idempotent
Inputs
contact_person_idstringrequired- Contact person external_id. Example: CP-001
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
chaser_customer_note_deleteDelete a note from a customer.DestructiveDelete Customer Note
Delete a note from a customer. Returns a confirmation. Use chaser_customer_note_delete to remove a note permanently.
- Idempotent
Inputs
customer_idstringrequired- Customer ID: the Chaser ID (cust_...) or your external ID prefixed with ext_ (for example ext_1234). Example: ext_CUST-001
note_idstringrequired- Note ID (note_...), from chaser_customer_notes_list. Example: note_aGVsbG8
chaser_template_deleteDelete a message template.DestructiveDelete Template
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.
- Idempotent
Inputs
template_idstringrequired- Template ID (tmpl_...), from chaser_templates_list. Example: tmpl_4h7d2
No tools match.