Integration

Aliaddo integration

Aliaddo is a Colombian cloud ERP and CRM with DIAN electronic invoicing. An agent can manage contacts, CRM leads, deals and activities; products, stock and price lists; sales invoices, quotes, sales orders and delivery notes (remisiones); purchase invoices and support documents; taxes, withholdings and journal entries; and read branches, warehouses, cost centers, document types, ledger accounts, users and CRM settings. Creating a sales invoice or a support document issues a fiscal document to the DIAN, and voiding, payments and journal entries change the company's books. Not included: paying a purchase invoice (the docs give it the sales-invoice route), the full ledger account list (only the search by code answers), the stages-by-pipeline route (stages come with list_pipelines) and an internal Zapier route. Field values are Spanish (Vigente, Pagada...); a call the company's plan does not allow answers 402, one the user lacks permission for 403. Authentication is the user's API token, generated in Aliaddo under My data, Integration, sent as a Bearer token; 50 to 150 requests per minute per company depending on the plan.

Connect Aliaddo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Aliaddo

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Bill, 5 operations

create_billCreate billPOSTAgents: ask firstCreates a purchase invoice, or a Documento soporte (electronic support document for a purchase from a seller not obliged to invoice): a legal tax document reported to the DIAN, undone only by void_bill. Returns id, consecutive and DIAN state.
get_billGet billGETAgents: ask firstReturns one purchase invoice or support document by id: kind, supplier, branch, lines, taxes, withholdings, totals, payments, balance, status and DIAN state.
list_billsList billsGETAgents: ask firstLists purchase invoices and support documents: supplier, branch, lines, taxes, totals, balance, status and DIAN state. page and itemsPerPage are required (at most 50); filter by status, consecutive, contact, product, dates.
update_billUpdate billPUTAgents: ask firstUpdates a purchase invoice by id; returns id, consecutive, status and DIAN state. Fields are optional and the docs do not say whether one left out is kept: read it with get_bill first and send every field to keep.
void_billVoid billPATCHAgents: ask firstVoids (anula) a purchase invoice by id, with no undo in the API. For a paid or partly paid one pass accountCode, the bank or cash account the money returns to. The documented answer is empty.

Contact, 5 operations

create_contactCreate contactPOSTAgents: ask firstCreates a contact (a person or a company) with identification, names, phones, emails, addresses and roles, and returns its id and name. kind, identificationType and identification are required.
delete_contactDelete contactDELETEAgents: ask firstDeletes a contact by id. The answer is empty.
get_contactGet contactGETAgents: ask firstReturns one contact by id: kind, identification type and number, names or company name, phones, emails and roles (customer, supplier, employee, seller). Personal data.
list_contactsList contactsGETAgents: ask firstLists contacts (people and companies: customers, suppliers, employees, sellers) with identification number, names, phones and emails: personal data. Filter by kind, identification, phone or email; at most 50 per page.
update_contactUpdate contactPUTAgents: ask firstUpdates a contact by id and returns the contact record (personal data). Fields are optional and the docs do not say whether one left out is kept: read the contact with get_contact first and send every field it should keep.

Delivery note, 5 operations

create_delivery_noteCreate delivery notePOSTAgents: ask firstCreates a sales delivery note (remision) with product lines and returns its id, consecutive, createdAt and status. Required: personId, date, dueDate, paymentFormCode, paymentMeanCode, personIdSeller, branchId.
get_delivery_noteGet delivery noteGETAgents: ask firstReturns one delivery note (remision) by id: customer, seller, branch, addresses, lines, taxes, withholdings, totals and status.
list_delivery_notesList delivery notesGETAgents: ask firstLists sales delivery notes (remisiones): customer, seller, branch, lines, taxes, totals and status. page and itemsPerPage are required (at most 50); filter by status, consecutive, customer, seller, product, dates.
update_delivery_noteUpdate delivery notePUTAgents: ask firstUpdates a delivery note by id (dates MM/DD/YYY in the docs); empty answer. Fields are optional and the docs do not say whether one left out is kept: read it with get_delivery_note first and send every field to keep.
void_delivery_noteVoid delivery notePUTAgents: ask firstVoids (anula) a delivery note by id; the API offers no undo. The documented answer is empty.

Invoice, 5 operations

create_invoiceCreate invoicePOSTAgents: ask firstCreates a sales invoice; the documented answer carries its DIAN electronic-invoice state and CUFE, so treat it as a legal tax document issued to the DIAN (undone only by void_invoice). accountCodePayment also records its payment.
get_invoiceGet invoiceGETAgents: ask firstReturns one sales invoice by id: customer, branch, addresses, lines, taxes, withholdings, totals, payments and balance, status, DIAN state, CUFE and QR data.
list_invoicesList invoicesGETAgents: ask firstLists sales invoices: customer, seller, branch, lines, taxes, totals, balance, status and DIAN electronic-invoice state. page and itemsPerPage are required (at most 50); filter by status, consecutive, customer, seller, product, dates.
update_invoiceUpdate invoicePUTAgents: ask firstUpdates a sales invoice by id (dates written MM/DD/YYY in the docs); empty answer. Fields are optional and the docs do not say whether one left out is kept: read it with get_invoice first and send every field to keep.
void_invoiceVoid invoicePATCHAgents: ask firstVoids (anula) a sales invoice by id: a fiscal act on a document issued to the DIAN, with no undo in the API. For a paid or partly paid invoice pass accountCode, the account the money leaves from. Empty answer.

Product, 5 operations

create_productCreate productPOSTAgents: ask firstCreates a product or service (code, name, categoryId and unitMeasurementId required) with optional taxes, withholdings, prices and initial stock per warehouse, and returns its id and name.
delete_productDelete productDELETEAgents: ask firstDeletes a product by id. The answer is empty.
get_productGet productGETAgents: ask firstReturns one product by id: code, name, image, description, category, unit of measure, taxes, withholdings, buy and sell flags, cost, prices, inventory control and stock.
list_productsList productsGETAgents: ask firstLists products and services: code, name, category, unit, taxes, withholdings, cost, buy and sell prices, inventory control and stock. Filter by code (SKU, barcode or supplier code) or tracked only; at most 50 per page.
update_productUpdate productPUTAgents: ask firstUpdates a product by id and returns its id and name. Fields are optional and the docs do not say whether one left out is kept: read the product with get_product first and send every field it should keep.

Quote, 5 operations

create_quoteCreate quotePOSTAgents: ask firstCreates a quote for a customer with product lines and returns its id, consecutive, createdAt and status. Required: personId, date, dueDate, paymentFormCode, paymentMeanCode, personIdSeller and branchId.
get_quoteGet quoteGETAgents: ask firstReturns one quote by id: customer, seller, branch, addresses, lines, taxes, withholdings, totals and status.
list_quotesList quotesGETAgents: ask firstLists quotes: customer, seller, branch, lines, taxes, totals and status. page and itemsPerPage are required (at most 50); filter by status, consecutive, customer, seller, product or dates.
update_quoteUpdate quotePUTAgents: ask firstUpdates a quote by id (dates written MM/DD/YYY in the docs); empty answer. Fields are optional and the docs do not say whether one left out is kept: read it with get_quote first and send every field to keep.
void_quoteVoid quotePUTAgents: ask firstVoids (anula) a quote by id; the API offers no undo. The documented answer is empty.

Sales order, 5 operations

create_sales_orderCreate sales orderPOSTAgents: ask firstCreates a sales order for a customer with product lines and returns its id, consecutive, createdAt and status. Required: personId, date, dueDate, paymentFormCode, paymentMeanCode, personIdSeller and branchId.
get_sales_orderGet sales orderGETAgents: ask firstReturns one sales order by id: customer, seller, branch, addresses, lines, taxes, withholdings, totals and status.
list_sales_ordersList sales ordersGETAgents: ask firstLists sales orders: customer, seller, branch, lines, taxes, totals and status. page and itemsPerPage are required (at most 50); filter by status, consecutive, customer, seller, product or dates.
update_sales_orderUpdate sales orderPUTAgents: ask firstUpdates a sales order by id (dates written MM/DD/YYY in the docs); empty answer. Fields are optional and the docs do not say whether one left out is kept: read it with get_sales_order first and send every field to keep.
void_sales_orderVoid sales orderPUTAgents: ask firstVoids (anula) a sales order by id; the API offers no undo. The documented answer is empty.

Tax, 5 operations

create_taxCreate taxPOSTAgents: ask firstCreates a tax in the company's settings (name and categoryCode required; rate, rateKind, includedInPrice optional) and returns its id and name. It can then be set on products and document lines.
delete_taxDelete taxDELETEAgents: ask firstDeletes a tax by id from the company's settings (the docs say this route deletes a tax or a withholding). The answer is empty.
get_taxGet taxGETAgents: ask firstReturns one tax by id: name, category code and name, rate, rate kind and whether it is included in the product price.
list_taxesList taxesGETAgents: ask firstLists the company's taxes (IVA, INC and other categories): name, category code and name, rate, rate kind (percent, per thousand or fixed) and whether the tax is included in the price. Paged, at most 50 per page.
update_taxUpdate taxPUTAgents: ask firstUpdates a tax by id (name, categoryCode, rate, rateKind, includedInPrice) and returns its id and name. The docs do not say whether a field left out is kept: read it with get_tax first and send every field it should keep.

Withholding, 5 operations

create_withholdingCreate withholdingPOSTAgents: ask firstCreates a withholding (name and categoryCode 05, 06 or 07 required; rate, rateKind and minimumBase optional) and returns its id and name.
delete_withholdingDelete withholdingDELETEAgents: ask firstDeletes a withholding by id from the company's settings. The answer is empty.
get_withholdingGet withholdingGETAgents: ask firstReturns one withholding by id: name, category code and name, rate and rate kind.
list_withholdingsList withholdingsGETAgents: ask firstLists the company's withholdings (IVA, income tax at source and ICA withholdings): name, category code and name, rate and rate kind.
update_withholdingUpdate withholdingPUTAgents: ask firstUpdates a withholding by id. The docs require name and categoryCode on every update: read them with get_withholding and send them back with the change. Returns its id and name.

Activity, 4 operations

create_activityCreate activityPOSTAgents: ask firstCreates a CRM activity (activityTypeId, title, endDate, endHour, userIdOwner and isDone required; start date and hour for appointments), optionally linked to a deal and a contact. Returns its id and name.
delete_activityDelete activityDELETEAgents: ask firstDeletes an activity by id. The answer is empty.
list_activitiesList activitiesGETAgents: ask firstLists CRM activities; filter by status (false pending, true done), deal, contact or a date range. The docs describe no answer fields: each activity comes back whole under activities.
update_activityUpdate activityPUTAgents: ask firstUpdates an activity by id, for example to mark it done; empty answer. Fields are optional and the docs do not say whether one left out is kept: read it with list_activities first and send every field to keep.

Deal, 4 operations

create_dealCreate dealPOSTAgents: ask firstCreates a CRM deal (dealName, itemId, amount, userIdOwner, pipelineId, pipelineStageId and expectedCloseDate required) and returns its id and name.
delete_dealDelete dealDELETEAgents: ask firstDeletes a deal by id. The answer is empty.
list_dealsList dealsGETAgents: ask firstLists CRM deals; page and itemsPerPage are required (at most 50); filter by name (4+ characters), contact, stages or a date range. The docs describe no answer fields: each deal comes back whole under deals.
update_dealUpdate dealPUTAgents: ask firstUpdates a deal by id, for example to move it to another stage; empty answer. Fields are optional and the docs do not say whether one left out is kept: read it with list_deals first and send every field to keep.

Journal entry, 4 operations

create_journal_entryCreate journal entryPOSTAgents: ask firstCreates a journal entry in the company's books (currency, document type, dates and at least 2 movements, each with a debit or a credit) and returns its id and consecutive.
get_journal_entryGet journal entryGETAgents: ask firstReturns one journal entry by id: consecutive, currency, status, document type, dates, description and movements.
list_journal_entriesList journal entriesGETAgents: ask firstLists journal entries with currency, status, document type, dates, description and movements (account, contact, cost center, base, rate, debit, credit). page, itemsPerPage and status are required.
void_journal_entriesVoid journal entriesPATCHAgents: ask firstVoids (anula) one or more journal entries in the company's books, by id; the API offers no undo. The documented answer is empty.

Lead, 4 operations

create_leadCreate leadPOSTAgents: ask firstCreates a CRM lead (stateId and firstName required, plus phoneMobile or email) with its source, territory and product of interest, and returns its id and name.
delete_leadDelete leadDELETEAgents: ask firstDeletes a lead by id. The answer is empty.
list_leadsList leadsGETAgents: ask firstLists CRM leads: identification, name, phones and emails (personal data), lifecycle stage, product of interest, source and territory. page and itemPerPage are required; filter by identification, phone or email.
update_leadUpdate leadPUTAgents: ask firstUpdates a lead by id and returns it as a contact record (personal data). Fields are optional and the docs do not say whether one left out is kept: read the lead with list_leads first and send every field it should keep.

Document type, 2 operations

get_document_typeGet document typeGETAgents: ask firstReturns the document (voucher) type matching a code of at least 4 characters: id, code, name and status.
list_document_typesList document typesGETAgents: ask firstLists the accounting document (voucher) types: id, code, name and status, for the documentTypeId of a journal entry. page and itemPerPage are required.

Activity type, 1 operation

list_activity_typesList activity typesGETAgents: ask firstLists activity types (id, name, icon, color, order and flags): the activityTypeId of an activity.

Branch, 1 operation

list_branchesList branchesGETAgents: ask firstLists the company's branches (id, name, isDefault, status): the branchId of sales and purchase documents.

Cost center, 1 operation

list_cost_centersList cost centersGETAgents: ask firstLists cost centers (id, code, name, isDefault, enabled): the costCenterId of documents and journal lines. At most 100 per page.

Lead source, 1 operation

list_lead_sourcesList lead sourcesGETAgents: ask firstLists lead sources (id, name, order, isDeleted, isSystem): the originId of deals and leads.

Ledger account, 1 operation

search_ledger_accountsSearch ledger accountsGETAgents: ask firstReturns the ledger accounts (id, code, name, enabled) whose code matches the given code of at least 4 characters. Use it to find the accountCode of journal lines and payments.

Lifecycle stage, 1 operation

list_lifecycle_stagesList lifecycle stagesGETAgents: ask firstLists the contact lifecycle stages (id, name): the stateId of a lead.

Owner, 1 operation

list_ownersList ownersGETAgents: ask firstLists the users who can own deals and activities: id, role name, first and last name.

Payment, 1 operation

record_invoice_paymentRecord invoice paymentPOSTAgents: ask firstRecords a payment received on a sales invoice (amount, paidAt date, code of the bank or cash account receiving it) in the company's books and returns the payment consecutive. It charges nobody.

Pipeline, 1 operation

list_pipelinesList pipelinesGETAgents: ask firstLists sales pipelines with their stages (id, name, order, probability, won and lost flags): the pipelineId and pipelineStageId of a deal.

Price list, 1 operation

list_product_price_listsList product price listsGETAgents: ask firstLists the price lists of a product: id, name, isFor (sell or buy), isForMargin and amount.

Product category, 1 operation

list_product_categoriesList product categoriesGETAgents: ask firstLists product categories (id, name, image, enabled): the categoryId of a product.

Product stock, 1 operation

get_product_stockGet product stockGETAgents: ask firstReturns a product's stock per warehouse: stockPerWarehouse, each with the warehouse id, code, name and stock.

Seller, 1 operation

list_sellersList sellersGETAgents: ask firstLists the contacts marked as sellers (id, kind, name): the personIdSeller of sales documents.

Territory, 1 operation

list_territoriesList territoriesGETAgents: ask firstLists CRM territories (id, name, order, isDeleted): the territoryId of deals and leads.

Unit of measure, 1 operation

list_units_of_measureList units of measureGETAgents: ask firstLists units of measure (id, code, name, category, enabled): the unitMeasurementId of a product.

User, 1 operation

list_usersList usersGETAgents: ask firstLists the company's users: id, role name, first and last name, lockout flag. page and itemPerPage are required (at most 50).

Warehouse, 1 operation

list_warehousesList warehousesGETAgents: ask firstLists warehouses (id, code, name, isDefault, enabled): the warehouseId of document lines and stock. At most 100 per page.

Use Aliaddo from Claude Code, Cursor or Codex

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

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