Ignition

Set or clear the category of a service in the practice's service library. Provide exactly one of category_slug or category_name. Assigning a category to a new (draft) service also makes it active

Check whether a client can be removed from its group before calling remove_client_group_member. Reports what blocks the removal outright (the Primary Client, or a draft group proposal that routes services to this member), what only warns (sent proposals referencing the member, which `force` can override), and whether the member still has active services or unarchived invoices. Read-only — it changes nothing.

Create a new client with contacts, optional addresses, and optional tags. Supply the contacts array, or - for a single contact - the flat contact_name, contact_email, contact_phone and contact_mobile fields

Create a client group from existing clients, so a group proposal can be built against it. Supply the Primary Client — it is the group's billing anchor and default signatory source, and a group that has members must have one. The Primary must already have a default contact, so create its clients with a contact first. Every member client must already exist; this tool does not create clients.

Create a new email template. Only type new_proposal is supported (additional templates for new proposal notifications). Content is HTML that may include Liquid placeholders (e.g. {{ client.name }}, {{ practice.name }}). Use list_terms_placeholders to discover available placeholders.

Create a Standard form for a client. Migrated Standard slugs retain their original questionnaire; Advanced slugs are unsupported.

Create a safe internal invoice draft for review in the Ignition invoice editor. This does not create, issue, send, deploy, number, or collect payment for a real invoice. The user must open the returned app_path and click Create in Ignition.

Create an intro or next steps message template. Content is HTML with optional Liquid placeholders using the same message placeholders as the UI.

Create a proposal from a full proposal document (options, projects, service groups, billing schedules, proposed services, deposits, recipients, and signable documents). Prefer create_proposal_using_template when an existing template covers the requested proposal; reach for this tool when the agent needs full control over the proposal structure. Document shape mirrors the proposal template encoder format with slug-only identifiers. Supply client_slug or client_group_slug and you get a draft. Omit both and you get an unfinished proposal in `new` state, for building one before its client is settled. Its editor_url opens it and the service-line tools still work on it, but update_proposal needs a draft and answers not_editable until it has a client; it does not appear in list_proposals until then either (get_proposal by slug still finds it); and one left without a client for 7 days is deleted.

Create a proposal from a proposal template. The template defines services, options, billing, and default settings. You can override top-level settings via optional arguments. For personalised_message and next_steps_message, first check list_message_templates for an appropriate existing template to use as content. If none is suitable, craft a custom HTML message. Supply client_slug (or client_group_slug for a multi-entity proposal, whose services start with no member assigned until the firm chooses in the editor) and you get a draft. Omit both and you get an unfinished proposal in `new` state, for building one before its client is settled. Its editor_url opens it and the service-line tools still work on it, but update_proposal needs a draft and answers not_editable until it has a client; it does not appear in list_proposals until then either (get_proposal by slug still finds it); and one left without a client for 7 days is deleted.

Create a new service in the practice's service library

Create a new terms template. Content is HTML that may include Liquid placeholders (e.g. {{ client.name }}, {{ practice.name }}). Use list_terms_placeholders to discover available placeholders.

End an agreed service on a client. An enabled service is ended now and stops billing; an upcoming service that has not started yet is cancelled. If a renewal or change order has already queued an upcoming service to replace this one, that second service is cancelled too unless you pass cancel_upcoming_replacement false. A service that is already disabled or cancelled is rejected rather than ended again. The service is recorded as "ended", never as "replaced by" another proposal — MCP cannot link a replacement after the fact, so consolidating engagements onto a new proposal leaves the old services ended. Find candidates with list_agreed_services filtered to state enabled for services that have started, or state upcoming for ones that have not.

Get full billing item detail by slug, including client embed, service, billable service, billing group, payment method, tax, and the invoice it was billed onto when applicable.

Get a change order by slug (co_*) with its line-level changes to the accepted proposal: changes.added_services, changes.cancelled_services, and changes.updated_services whose fields map each changed field (including price_rule, quantity_rule and discount_rule) to its before and after value. Also returns added projects, service group billing changes, signatory changes and the added, edited and cancelled service counts. Price rules are the stored rules with integer cents in the proposal currency, not computed totals. app_path opens the parent proposal.

Get full client detail including contacts, services summary, and invoices summary

Get full client group detail including members, the Primary Client, tags, and whether the group can be the subject of a multi-entity proposal. Archived groups are returned.

Roll-up Client NPS metrics for the practice: average score (0-10), traditional NPS (-100 to 100, % promoters minus % detractors), and the number of submitted responses.

Get full detail for a single form including questions, responses, client, and form template

Get full invoice detail by identifier, including line items, money totals, client embed, issued_by user, latest payment (with collection and disbursal), latest ledger deployment, latest reconciliation, and days_overdue. Accepts an invoice slug (inv_*), Ignition reference number (INV-####), or the ledger invoice number from Xero/QuickBooks (stored as deployment.external_number).

Get full payment detail by slug, including client, linked invoices, payment method, and the latest collection, disbursal, refund, and dispute where present.

Get practice info including name, country, currency, timezone, and active client count

Get top-level proposal metadata and settings by identifier. Accepts a proposal slug (prop_*) or user-facing reference number (PROP-####). Use get_proposal_document for service lines and pricing.

Get a proposal's full document tree, including options, projects, service groups, schedules, services, current library category names/slugs, and pricing.

Count and total proposal value in one call, over the same filter as list_proposals (e.g. accepted_at on_or_after a date with state accepted or completed). Returns one row per currency and group with proposal_count, valued_count, total_cents, mean_cents and median_cents of minimum_contract_value_cents (tax-exclusive; accepted option once accepted or completed, otherwise cheapest option). Mean and median cover valued proposals only. group_by partner (the client's assigned partner; null when unassigned, inactive or support), sender_user, accepted_month or created_month (practice-local months); omit it for a single total per currency. Reads at most 20000 matching proposals; narrow the filter (e.g. by accepted_at) beyond that.

Get the workflow (job deployment) configuration for a proposal. Returns the per-app `workflow_settings` — `deploy_strategy` is `automatic` or `manual` — and the `workflows` that become jobs in the connected workflow app when the proposal is accepted. A proposal with no workflows creates no jobs at all. Accepts a proposal slug (prop_*) or reference number (PROP-####). Use add_proposal_workflow to add a workflow, update_proposal_workflow_settings to stop jobs deploying automatically, or remove_proposal_workflow to drop a workflow entirely.

Get full detail for a single service including price, tax rate, and billing mode

Get full detail for a single tax rate

Get full detail for a single terms template including its raw content with Liquid placeholders

Get a single active user in the practice by slug. Useful for resolving a client's partner or manager (both are users)

What happened to work in progress during a reporting period: opening balance, source movements, work cleared onto Ignition invoices, releases, holds and closing balance, for the whole period and per calendar month. Period dates are the movement history's own dates, unrelated to the work-date filters the other WIP tools apply, and ownership is the Manager and Partner captured on each movement rather than the client's current ones. The period is inclusive and can span at most 12 months. Time-based basis only: figures cover work that bills through WIP in the practice billing currency, and exclude work a fixed fee covers, work whose commercial evidence is ambiguous, and work the source sent in another currency. `clearance_percentage` is null rather than zero whenever `coverage.complete` is false or no WIP was available to clear — an unknown is never reported as a zero.

How much work in progress the practice currently holds, and where it sits. Reports open and held totals, ageing, top contributors and data-quality exceptions from the practice's elected WIP source. Populations differ on purpose and do not reconcile: `open_totals` and `ageing_buckets` cover the client/service/month groups whose commercial treatment is actionable now (billable through WIP), while every `breakdowns` entry is the whole review scope narrowed to the practice billing currency. Breakdowns are the top 10 rows by open value, not an export: read `total_available_count` for how many rows exist. Work-date filters narrow today's balance; they never produce an "as at" historical balance — use get_wip_performance for what moved during a period. Ownership is the client's current Manager and Partner. Ageing buckets are calendar buckets (current month, one to two months, three months or more), not 30/60/90-day buckets. Omitting both work-date filters applies a rolling one-year window, which list_wip_entries does not. Work dated before the practice's WIP start date is never included, and `work_date_on_or_after` reports that date when it is the later bound. `exception_counts` always reports `stale_source` with a null count: staleness needs a threshold no tool here accepts, so it is unavailable rather than zero. A breakdown row whose `id` is null is work with no client, no service or no owner of that kind; it cannot be sent back as a filter.

Apply a single bulk percentage increase across every proposed service in a draft proposal, with an optional round-up to the nearest $1, $5, or $10. A price increase can be applied AT MOST ONCE per proposal and ONLY while the proposal is editable (draft). Subsequent calls on the same proposal return { error: "already_applied" }. Set preview: true to see the resulting minimum-contract-value deltas without committing; preview does not count toward the one-shot limit.

List agreed services using structured filters. Use state select equals enabled for active/current services. Lifecycle dates are current stored facts, not an immutable event history.

List unbilled and billed billing items using structured filters. Billing dates and due flags use the practice timezone. Billed history remains visible for archived clients; unbilled work for archived recipients or payers is excluded.

List change orders to accepted proposals using structured filters and optional total counts. Returns issued change orders (sent, accepted, declined, expired, or voided after sending); unsent drafts and change orders voided before they were sent are excluded unless include_drafts is true. Use accepted_at or sent_at date filters to find change orders accepted or issued since a point in time. Each row counts the services added, edited and cancelled; use get_change_order for the line-level changes. Use list_proposals with accepted_at and is_renewal for newly accepted proposals and renewals. app_path opens the parent proposal.

List the clients that belong to a client group, cursor-paginated and ordered by default by name. `get_client_group` embeds only a bounded preview of members and sets `members_truncated` when there are more — use this tool for the rest, and for any group large enough that the whole membership should not arrive in one response. Archived members are included; `is_primary` marks the group's Primary Client.

List client groups using structured filters. Archived groups require include_archived: true. Filter multi_entity_eligible to true to exclude legacy import buckets.

List submitted Client NPS responses using structured date, score, bucket, client and comment filters. Archived or removed clients are excluded, so totals may differ from get_client_nps_summary.

List clients for the practice, with optional filters by state, tag, partner, manager, or name (case-insensitive partial match)