Integration

Chaser integration

Chaser automates accounts-receivable credit control: it chases unpaid invoices with scheduled email, SMS and letter reminders. Read and create or upsert customers, contact persons, invoices, credit notes and overpayments (singly or 100 at a time), read invoice chase and email history, pause or resume chasing for an invoice, a customer or the whole organisation, manage customer notes, tasks, reminder templates and chasing schedules, and attach invoice PDFs. Authentication is HTTP Basic with the API key as username and the API secret as password, both from Chaser, Organisation settings, Integrations, Get API keys.

Connect Chaser How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Chaser.Built from the 54 Chaser tools below, on the connection you add once.

What you can do with Chaser

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Contact person, 6 operations

create_contact_personCreate contact personPOSTAdds a contact person to a customer (external_id required). Returns the created contact person.
delete_contact_personDelete contact personDELETEDeletes a contact person from a customer. There is no tool to restore it; the docs do not say whether the deletion is permanent.
get_contact_personGet contact personGETReturns one contact person of a customer by its external_id. Contains personal data (name, email, phone).
list_contact_personsList contact personsGETLists the contact persons of a customer (names, emails, phone numbers: personal data).
update_contact_personUpdate contact personPUTUpdates a contact person of a customer. Send every field you want the record to keep: the docs do not say whether a field left out is kept or cleared, so read the record first and send its values back with your change.
upsert_contact_personsUpsert contact personsPUTInserts or updates up to 100 contact persons in one call, matched by external_id. Returns inserted, modified and omitted counts, the new ids and why each omitted entry was skipped.

Credit note, 5 operations

create_credit_noteCreate credit notePOSTCreates a credit note for a customer (customer_external_id). All fields are required. Returns it with its Chaser id.
get_credit_noteGet credit noteGETReturns one credit note by Chaser id or ext_<credit_note_id>.
list_credit_notesList credit notesGETLists credit notes, 100 per page (page starts at 0), with filters (object operators) on id, number, remaining credit, total, status, currency, customer and date.
update_credit_noteUpdate credit notePUTUpdates a credit note. Send every field you want the record to keep: the docs do not say whether a field left out is kept or cleared, so read the record first and send its values back with your change.
upsert_credit_notesUpsert credit notesPUTInserts or updates up to 100 credit notes in one call, matched by credit_note_id (or id). Returns inserted, modified and omitted counts, the new ids and why each omitted entry was skipped.

Customer, 5 operations

create_customerCreate customerPOSTCreates a customer (external_id and company_name required) with its main contact, groups and addresses. Returns the customer with its Chaser id.
get_customerGet customerGETReturns one customer by Chaser id or ext_<external_id>, with contact details, addresses and whether it is being chased. Contains personal data (contact names, email, phone).
list_customersList customersGETLists customers, 100 per page (page starts at 0), with filters on external_id, names, email and status. Contains contact names, emails and phone numbers. additional_fields adds payment portal link and payer rating.
update_customerUpdate customerPUTUpdates a customer. Send every field you want the record to keep: the docs do not say whether a field left out is kept or cleared, so read the record first and send its values back with your change.
upsert_customersUpsert customersPUTInserts or updates up to 100 customers in one call, matched by external_id (or id). Returns inserted, modified and omitted counts, the new ids and why each omitted entry was skipped.

Invoice, 5 operations

create_invoiceCreate invoicePOSTCreates an invoice for an existing customer (customer_external_id). Chaser chases unpaid invoices with reminders to the customer per the organisation's schedules; use pause_invoice_chasing to hold one.
get_invoiceGet invoiceGETReturns one invoice by Chaser id or ext_<invoice_id>: amounts, dates, payments, PDF link, customer name and whether it is being chased.
list_invoicesList invoicesGETLists invoices, 100 per page (page starts at 0), with filters (object operators) on ids, number, status, currency, amounts, dates and customer_external_id. Each invoice says whether it is being chased.
update_invoiceUpdate invoicePUTUpdates an invoice (status, amounts, dates, customer). Send every field you want the record to keep: the docs do not say whether a field left out is kept or cleared, so read the record first and send its values back with your change.
upsert_invoicesUpsert invoicesPUTInserts or updates up to 100 invoices in one call, matched by invoice_id (or id). Returns inserted, modified and omitted counts, the new ids and why each omitted entry was skipped.

Overpayment, 5 operations

create_overpaymentCreate overpaymentPOSTCreates an overpayment (a customer payment above what was owed) for a customer. All fields are required. Returns it with its Chaser id.
get_overpaymentGet overpaymentGETReturns one overpayment by Chaser id or ext_<overpayment_id>.
list_overpaymentsList overpaymentsGETLists overpayments, 100 per page (page starts at 0), with filters (object operators) on id, remaining credit, total, currency, customer and date.
update_overpaymentUpdate overpaymentPUTUpdates an overpayment. Send every field you want the record to keep: the docs do not say whether a field left out is kept or cleared, so read the record first and send its values back with your change.
upsert_overpaymentsUpsert overpaymentsPUTInserts or updates up to 100 overpayments in one call, matched by overpayment_id (or id). Returns inserted, modified and omitted counts, the new ids and why each omitted entry was skipped.

Template, 5 operations

create_templateCreate templatePOSTCreates a reminder template (name required) for email, SMS or letter. It sends nothing by itself: schedules use it. Returns it with its id.
delete_templateDelete templateDELETEDeletes a reminder template; refused while a schedule uses it. There is no tool to restore it.
get_templateGet templateGETReturns one reminder template: name, channel, subject, text and attachment options.
list_templatesList templatesGETLists the organisation's reminder templates (email, SMS or letter) with subject and text.
update_templateUpdate templatePUTUpdates a reminder template; changes reach every schedule that uses it. Send every field you want the record to keep: the docs do not say whether a field left out is kept or cleared, so read the record first and send its values back with your change.

Note, 4 operations

create_customer_noteCreate customer notePOSTAdds a note to a customer, with an optional reminder date. Returns the created note with its id.
delete_customer_noteDelete customer noteDELETEDeletes a note from a customer. There is no tool to restore it.
list_customer_notesList customer notesGETLists the notes on a customer: message, date, reminder date and type.
update_customer_noteUpdate customer notePATCHChanges a note on a customer: only the fields you send (message, reminder_date, type) are sent.

Pause, 3 operations

pause_customer_chasingPause customer chasingPOSTPauses chasing on a customer: none of its invoices is chased until resume_customer_chasing.
pause_invoice_chasingPause invoice chasingPOSTPauses chasing on one invoice: Chaser sends it no reminders until resume_invoice_chasing.
pause_organisation_chasingPause organisation chasingPOSTPauses chasing for the whole organisation: no invoice is chased until resume_organisation_chasing.

Resume, 3 operations

resume_customer_chasingResume customer chasingPOSTResumes chasing on a customer: Chaser starts sending scheduled reminders for all its invoices again.
resume_invoice_chasingResume invoice chasingPOSTResumes chasing on one invoice: Chaser starts sending its scheduled reminders to the customer again.
resume_organisation_chasingResume organisation chasingPOSTResumes chasing for the whole organisation: Chaser starts sending scheduled reminders for every chased invoice again.

Schedule, 3 operations

create_scheduleCreate schedulePOSTCreates an empty chasing schedule with a name. Returns it with its id.
get_scheduleGet scheduleGETReturns one chasing schedule: its chasers (days, template, repeat, escalation), reminders, late payment fees and early payment discounts.
list_schedulesList schedulesGETLists the organisation's chasing schedules with their chasers (days, template, repeat, escalation) and reminders.

Task, 3 operations

create_taskCreate taskPOSTCreates a credit-control task (type and category required), optionally assigned by email and with a due date. Returns it with its id.
list_tasksList tasksGETLists credit-control tasks, 100 per page (page starts at 0), with filters (object operators) on type, status, source, category and due date.
update_taskUpdate taskPATCHChanges a task's status, assignee, due date or metadata; only the fields you send are sent.

History, 2 operations

get_invoice_historyGet invoice historyGETReturns the history of one invoice: chases sent, emails (with their text), notes, status changes and dispute. Contains personal data (email addresses and message text).
list_invoice_historyList invoice historyGETLists invoice histories: chases sent, emails (with their text), notes, status changes and disputes, 100 per page. Contains personal data (email addresses and message text).

Organisation, 2 operations

get_organisationGet organisationGETReturns the organisation the API key belongs to: name, legal name, base currency, country, timezone, last sync date and whether chasing is on.
list_organisationsList organisationsGETLists the organisations the API key can reach, with name, currency, country, timezone and chasing state.

Assign, 1 operation

assign_scheduleAssign schedulePOSTSets the chasing schedule of the given customers; with update_customer_invoices true their invoices move to it too. Changes who gets which reminders.

Pdf, 1 operation

upload_invoice_pdfUpload invoice pdfPOSTAttaches a PDF to an invoice (multipart field file, a valid PDF document). Returns the invoice with its PDF link.

Sync, 1 operation

sync_organisationSync organisationPOSTAsks Chaser to recalculate the organisation after data changes, then run the listed tasks (next chases, balances, credit limits, reminders, revenue). Limited to 5 calls per hour.

Use Chaser from Claude Code, Cursor or Codex

Connect Chaser in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Chaser operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Chaser

Create your workspace
Sign up free. Nothing to install.
Connect Chaser once
Add your Chaser connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.