Integration

Splynx integration

Splynx is billing and network management software for internet service providers, installed on the ISP's own server or hosted by Splynx. An agent can list, create and update customers and read their billing settings, online sessions, notes and contacts; create and read internet and recurring services; read tariffs; create and read invoices, payments and transactions and read credit notes and proforma invoices; create CRM leads, convert them to customers and read quotes; open, update and reply to support tickets; and read scheduling tasks, inventory, locations, partners and taxes. Customer, lead, session and ticket records are personal data. Left out: deletions, network and router configuration, voice, vouchers, customer payment accounts, documents and file uploads, administrators, API tokens and the customer portal; stored customer and service passwords are never returned. Connect with your Splynx address as instance_url (for example https://splynx.example.net, without /api/2.0) and an API key and secret (Administration > Main > API keys); the key needs Unsecure access enabled, which turns on the Basic authentication this integration uses, and permissions for the modules called.

Connect Splynx How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Splynx

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.

Customer, 4 operations

create_customerCreate customerPOSTCreates a customer in Splynx and returns its id. name, category (person or company), partner_id and location_id are required; status defaults to new.
get_customerGet customerGETReturns one customer by id: login, status, partner and location, name, email, billing email, phone, address, labels, contacts, monthly recurring revenue and last online time. Personal data.
list_customersList customersGETLists customers (subscribers) with login, status, partner, location, name, email, phone, address, labels and contacts. Filter with main_attributes (for example status or login) and page with limit and offset. Personal data.
update_customerUpdate customerPUTUpdates a customer: only the fields sent change (name, status, email, phone, address, labels, contacts...). Status acts on the live subscriber: blocked suspends their service, disabled makes the account inactive.

Lead, 4 operations

convert_lead_to_customerConvert lead to customerPUTConverts a CRM lead into a customer, with the status (new, active, blocked or disabled; default active) and category (person or company; default person) given.
create_leadCreate leadPOSTCreates a CRM lead (a prospect not yet a customer) and returns its id. name, category, partner_id and location_id are required.
get_leadGet leadGETReturns one CRM lead by id: status, name, email, phone, address, partner, location, labels and contacts. Personal data.
list_leadsList leadsGETLists CRM leads (prospects): name, email, phone, address, partner, location, billing type, labels and contacts. Filter with main_attributes, for example {"name": ["LIKE", "smith"]}. Personal data.

Ticket, 4 operations

create_ticketCreate ticketPOSTOpens a support ticket (subject, priority and type_id required) for a customer or lead and returns its id. Add the first message with create_ticket_message.
get_ticketGet ticketGETReturns one support ticket by id: customer, reporter, subject, priority, status, group, type, assignee, closed and unread flags, source, note, labels and dates.
list_ticketsList ticketsGETLists support tickets: customer, subject, priority, status, group, type, assignee, closed and unread flags, source and dates. Filter with main_attributes, for example {"customer_id": 1, "closed": 0}.
update_ticketUpdate ticketPUTUpdates a support ticket: change its subject, or close it with status closed. Updates send the configured email and SMS notifications unless preventNotification is true.

Invoice, 3 operations

create_invoiceCreate invoicePOSTCreates an invoice on a real customer's account with its line items and returns its id; status not_paid leaves it due. customer_id, number, status and items are required.
get_invoiceGet invoiceGETReturns one invoice by id: customer, number, status, created, due and payment dates, total, amount due, note, memo and line items (description, quantity, price, tax, period).
list_invoicesList invoicesGETLists invoices: customer, number, status (not_paid, paid, pending, deleted), dates, total, amount due, payment and line items. Filter with main_attributes, for example {"customer_id": 1, "status": "not_paid"}.

Payment, 3 operations

create_paymentCreate paymentPOSTRecords a payment received from a customer and returns its id; it can be linked to an invoice. It is a record in Splynx only: no card or payment account is charged.
get_paymentGet paymentGETReturns one payment by id: customer, invoice or credit note it pays, payment method, receipt number, date, amount, comment, the five additional fields and whether it was voided.
list_paymentsList paymentsGETLists payments received: customer, invoice, payment method, receipt number, date, amount, comment and whether it was voided. Filter with main_attributes, for example {"customer_id": 1}.

Transaction, 3 operations

create_transactionCreate transactionPOSTAdds a billing transaction to a customer's account and returns its id: type credit is a charge (minus), debit is an income (plus). It changes the customer's account balance.
get_transactionGet transactionGETReturns one billing transaction by id: type, customer, quantity, unit, price, VAT, total, date, category, period, description, linked service, payment and invoice.
list_transactionsList transactionsGETLists billing transactions (charges and incomes on customer accounts): type, customer, quantity, price, VAT, total, date, category, period, service and invoice. Filter with main_attributes.

Customer contact, 2 operations

create_customer_contactCreate customer contactPOSTAdds an email address or phone number to a customer's contacts, with a label (primary, billing, work...). Setting is_primary demotes the existing primary contact of the same type and label.
list_customer_contactsList customer contactsGETLists the email and phone contacts stored for customers. Pass customer_id to read one customer's contacts (optionally contact_type email or phone). Personal data.

Customer note, 2 operations

create_customer_noteCreate customer notePOSTAdds a comment or note to a customer's record and returns its id. customer_id and comment are required; type (comment, finance, service, support...) and class set how it is shown.
list_customer_notesList customer notesGETLists comments and notes written on customers (type, class, title, text, author, assignee, pinned and done flags). Filter by customer with main_attributes, for example {"customer_id": 1}.

Internet, 2 operations

get_internet_tariffGet internet tariffGETReturns one internet tariff plan by id: title, price, VAT, speeds, burst and speed-limit settings, billing types, tax, availability and labels.
list_internet_tariffsList internet tariffsGETLists internet tariff plans: title, price, VAT, download and upload speeds, burst and speed-limit settings, billing types, availability by partner and location, and labels.

Internet service, 2 operations

create_internet_serviceCreate internet servicePOSTAdds an internet service (an internet tariff with its service login and IP assignment) to a real customer and returns its id. Status active bills it to them from start_date. Use end_date 0000-00-00 for no end.
list_internet_servicesList internet servicesGETLists a customer's internet services: tariff, status, price and dates, discount, router and sector, service login, IP assignment (IPv4, IPv6), MAC and speeds. Service passwords are not returned.

Item, 2 operations

get_inventory_itemGet inventory itemGETReturns one inventory item by id: product, barcode, serial number, status, stock, assigned customer, service and invoice, cost price, notes and linked monitoring devices.
list_inventory_itemsList inventory itemsGETLists inventory items (individual pieces of equipment): product, barcode, serial number, status, stock, the customer or service it is assigned to, cost price and linked monitoring devices.

Leads note, 2 operations

create_lead_noteCreate lead notePOSTAdds a comment or note to a lead's record and returns its id. customer_id is the lead id; comment is required.
list_lead_notesList lead notesGETLists comments and notes written on leads (type, class, title, text, author, assignee, pinned and done flags). Filter by lead with main_attributes, for example {"customer_id": 12}.

Proforma invoice, 2 operations

get_proforma_invoiceGet proforma invoiceGETReturns one proforma invoice by id: customer, number, status, created, due and payment dates, payment and line items.
list_proforma_invoicesList proforma invoicesGETLists proforma invoices (payment requests issued before an invoice): customer, number, status, dates, payment and line items. Filter with main_attributes, for example {"customer_id": 1}.

Quote, 2 operations

get_quoteGet quoteGETReturns one quote by id: customer, number, status, created, decision and valid-until dates, total, linked invoice, note, memo and line items.
list_quotesList quotesGETLists quotes sent to leads and customers: number, status, dates, total, linked invoice, note and line items. Filter with main_attributes, for example {"customer_id": 1}.

Recurring service, 2 operations

create_recurring_serviceCreate recurring servicePOSTAdds a recurring service (a recurring tariff charged every billing period) to a customer and returns its id.
list_recurring_servicesList recurring servicesGETLists a customer's recurring services (services billed on a recurring tariff): tariff, status, description, quantity, price, dates, discount and billing period.

Task, 2 operations

get_taskGet taskGETReturns one scheduling task by id: title, description, address, GPS, related customer, lead, service or ticket, project, priority, assignee, schedule, duration, workflow status and watchers.
list_tasksList tasksGETLists scheduling tasks (field jobs): title, description, address, GPS, related customer, lead or service, project, priority, assignee, schedule, workflow status and closed flag. Filter with main_attributes.

Ticket message, 2 operations

create_ticket_messageCreate ticket messagePOSTAdds a message to a support ticket and returns its id (ticket_id and message required). The customer can read it (this tool cannot hide it or attach files) and Splynx may email or text them per its ticket notifications.
list_ticket_messagesList ticket messagesGETLists ticket messages: ticket, author, date and time, text, attached files and whether hidden from the customer. Filter by ticket with main_attributes, for example {"ticket_id": 1}. Personal data.

Bundle, 1 operation

list_bundle_tariffsList bundle tariffsGETLists bundle tariffs: title, price, VAT, activation and cancellation fees, contract duration, renewal, discounts and the internet, voice and custom tariffs each bundle includes.

Bundle service, 1 operation

list_bundle_servicesList bundle servicesGETLists a customer's bundle services (packages that group internet, voice and custom services), with their fees, dates, renewal settings and the services each bundle contains.

Credit note, 1 operation

list_credit_notesList credit notesGETLists credit notes: customer, number, status, dates, total, remaining amount, payment and line items. Filter with main_attributes, for example {"customer_id": 1}.

Customer billing, 1 operation

get_customer_billingGet customer billingGETReturns a customer's billing settings: billing type, deposit, billing day and due days, blocking and grace periods, payment method, minimum balance, reminders and billing address.

Customers online, 1 operation

list_online_sessionsList online sessionsGETLists the network sessions online right now: customer, service and tariff ids, router (NAS), session login, IP and MAC addresses, bytes in and out and session start. Personal data.

Internet services service id, 1 operation

get_internet_serviceGet internet serviceGETReturns one internet service of a customer: tariff, status, price, dates, discount, router, login, IP assignment, MAC, geo data and speeds. The service password is not returned.

Location, 1 operation

list_locationsList locationsGETLists locations (id, name and the tax applied to each tariff type). Use an id as location_id when creating customers and leads.

One time, 1 operation

list_one_time_tariffsList one time tariffsGETLists one-time tariffs (charges billed once): title, description, price, VAT, enabled flag, availability by partner and location, and labels.

Partner, 1 operation

list_partnersList partnersGETLists partners (id and name). Every customer and lead belongs to a partner: use an id as partner_id when creating them.

Payment method, 1 operation

list_payment_methodsList payment methodsGETLists the payment methods configured on the instance (id, name, active flag and the names of its five additional fields). Use an id as payment_type in create_payment.

Product, 1 operation

list_inventory_productsList inventory productsGETLists inventory products (equipment models): name, vendor, category, rent price and sale price.

Project, 1 operation

list_projectsList projectsGETLists scheduling projects (id, title, description, type, category, workflow, archive flag, partners).

Recurring, 1 operation

list_recurring_tariffsList recurring tariffsGETLists recurring tariffs (custom periodic charges): title, price, VAT, billing types and period, availability by partner and location, and labels.

Recurring services service id, 1 operation

get_recurring_serviceGet recurring serviceGETReturns one recurring service of a customer: tariff, status, description, quantity, price, dates, discount and billing period.

Tax, 1 operation

list_taxesList taxesGETLists the taxes configured on the instance (id, name, rate, type, archived flag).

Tickets group, 1 operation

list_ticket_groupsList ticket groupsGETLists ticket groups (id, title, description, agent ids). Use an id as group_id in create_ticket.

Tickets status, 1 operation

list_ticket_statusesList ticket statusesGETLists ticket statuses (id, agent and customer titles, label, icon). Use an id as status_id in create_ticket.

Tickets type, 1 operation

list_ticket_typesList ticket typesGETLists ticket types (id, title, colour). Use an id as type_id in create_ticket.

Transaction category, 1 operation

list_transaction_categoriesList transaction categoriesGETLists transaction categories (id and name). Use an id as category in create_transaction.

Use Splynx from Claude Code, Cursor or Codex

Connect Splynx in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Splynx 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 Splynx

Create your workspace
Sign up free. Nothing to install.
Connect Splynx once
Add your Splynx 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.