Integration · Collect and manage
Siigo and Meteor AI agents
Connect Siigo Nube to Meteor: a Met sends quotes with a public link, checks prices and stock and works receivables from WhatsApp. 12 real tools.
How does Siigo connect to Meteor?
Meteor connects to Siigo Nube through its official API and gives your Met 12 tools to run the commercial side of your books from a live conversation: find and create parties by tax ID, look up products with their price lists and availability by warehouse, create quotes that come back with a public link you can paste into the chat, list the ones already sent, open invoices with their total, balance and filing status, and resolve the catalogs Siigo requires in order to invoice. The invoice, the credit note, the accounting voucher and the cash receipt stay with the operator on the web: the connector refuses those four tools when the request comes from a channel Met. Quotes, credit notes and vouchers exist only in Siigo Colombia, and you generate the credentials yourself from your own account.
Where it applies: Colombia, Mexico. The same integration serves both countries by swapping one credential: Colombia identifies the registered app with the Partner-Id header and Mexico with SiigoAPI-Application-Id.
What it automates
What a Meteor Met does with Siigo
Quote over WhatsApp while the rep sleeps
A customer asks for a price on several products and your Met builds the quote in Siigo with the real codes, taxes and sales rep. It returns the public link Siigo publishes for that quote, and the link goes straight into the chat: the customer opens it with no account and no install. If they ask for changes, you send another one. A quote is never stamped and burns no DIAN sequence number.
Answer price and availability without opening Siigo
A customer asks about a product and your Met looks it up in the Siigo catalog. One call returns the code, the unit, the taxes that apply, the price on each list and the quantity available by warehouse whenever that product tracks inventory.
Answer how much do I owe with the real balance
Your Met identifies the customer by tax ID, lists their invoices for the period and says which ones still carry a balance, for how much and since when. If the customer wants the document, the operator opens its PDF in Siigo Nube; this tool does not download or link it.
Have the party ready before anyone invoices
When a customer writes for the first time, your Met checks whether they already exist in Siigo and, if not, registers them with their document type, verification digit and city code. The sales rep opens Siigo and the invoice already has someone to be issued to.
Invoice from the desk, with the catalogs resolved
A rep working on the web can ask their Met for the invoice. The Met verifies an active customer, products, sales rep, taxes, an electronic document with automatic numbering and the FV payment methods. It then shows the complete detail, including the positive-integer documento_id, and ends the turn. Only explicit approval in a new message enables the call with confirmar set to true. There is no fallback to the first FV; enviar_dian and enviar_email are literal booleans, and fiscal status comes from Siigo's response.
12 tools
Everything your Met can ask Siigo for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
siigo_buscar_cliente | Finds a customer, supplier or party by tax ID, with their branch and status. |
siigo_crear_cliente | Registers a new party when the search comes up empty, with document type and city. |
siigo_consultar_producto | Finds products by code or name and returns taxes, price lists and availability by warehouse. |
siigo_crear_factura | Creates a sales invoice only after operator approval, with an explicit documento_id and verified sales rep, items, and payments. Filing and email switches accept literal booleans only; the tool never selects a document automatically. |
siigo_listar_facturas | Lists invoices by customer, document type or date range, with total, balance and status. |
siigo_consultar_factura | Returns invoice items, payments and filing status. The PDF stays in Siigo Nube because this tool does not call the download endpoint. |
siigo_crear_cotizacion | Creates a quote and returns the public Siigo link, which is what you paste to the customer in the chat. |
siigo_listar_cotizaciones | Lists quotes by customer, name or creation date, each one with the public link you can resend. |
siigo_crear_nota_credito | Issues the credit note that refunds, voids or reduces an electronic invoice, with its DIAN reason code. |
siigo_crear_comprobante_contable | Records a manual accounting entry with its debit and credit lines, which have to add up to the same figure. |
siigo_crear_recibo | Records a cash receipt against invoice installments, a customer advance or other income. |
siigo_listar_catalogo | Returns the catalogs an invoice is built from: document types, payment methods, taxes, warehouses, price lists, reps. |
The limits
What the Siigo integration does NOT do
We would rather say it here than have you find out during rollout.
-
It does not issue invoices, credit notes, accounting vouchers or receipts from a channel Met. This is not a setting you can flip: the connector refuses those four tools when the request arrives over WhatsApp, Instagram or Messenger, because all four are either stamped or written into the ledger. A quote does go through a channel, and that is the line: it is never stamped.
-
It does not file the invoice with the tax authority on its own. Filing in Colombia and CFDI stamping in Mexico are a separate flag that ships switched off, and you have to ask for it.
-
It does not work with Aspel SAE, COI or NOI. This API belongs to Siigo Nube; the Aspel desktop products do not expose it, so connecting them means moving to the cloud first.
-
It does not record cash receipts in Mexico. There that document is the SAT payment receipt and it has a different structure, so the connector refuses rather than record something else.
-
It does not invent availability. A product returns a quantity only when the account tracks inventory for it; a service returns none, and that is not the same as being out of stock.
-
It does not quote, issue credit notes or record accounting vouchers in Mexico. Those three resources exist only in the Siigo Colombia API: on a Mexican account the connector turns them down before any request leaves, rather than calling an endpoint that is not there.
-
It does not close books, produce financial statements or file returns. It is an operating window into Siigo, not accounting judgment, and that part is not going to change.
Before you start
What you need to connect Siigo
- 1
A Siigo API username and access key
In Siigo Nube, under Settings, Partners and integrations, "Integration credentials for digital platforms (Siigo API)", Add application. Only the administrator role can create them, and each company is capped at five applications.
- 2
The identifier of the registered application
Siigo hands it to you on that same screen when you add the application. Colombia sends it as Partner-Id and Mexico as SiigoAPI-Application-Id. Without it, Siigo rejects the login.
- 3
The country of the account
You declare it when configuring the integration. Colombia and Mexico are two separate APIs, with a different host and a different header, and one credential does not work on the other.
Frequently asked questions
Questions about Siigo and Meteor
No, and it is not a setting you can change. The connector refuses invoices, credit notes, accounting vouchers and receipts when the request comes from a channel. Quoting is allowed, and that is exactly where the line sits: a quote is never stamped and burns no DIAN sequence number, so the worst case is a badly quoted price, fixed by sending another quote.
It is a URL Siigo publishes for every quote, and the tool hands it back the moment the quote is created. You paste it to the customer in the chat and they open it with no account and no install. If they lose it, the tool that lists quotes returns the same link for each one. When the customer says yes, the quote does not turn into an invoice by itself: somebody still has to issue it.
Not directly. The API Meteor uses belongs to Siigo Nube, and Aspel SAE, COI and NOI are desktop products that do not expose it. If your operation runs on Aspel, the path is moving to Siigo Nube, and from there this integration behaves the same in Mexico as in Colombia.
In which set of books you keep, not in what you can do. The rule is simple: pick the sheet for the system you already run, and nobody needs both. Both connectors quote with a public link, invoice and read receivables. What differs is the edge of each platform. Alegra adds expenses, orders and bank accounts, and Siigo adds the credit note, the accounting voucher, the cash receipt and the tax catalogs of both countries.
Filing is only requested when you explicitly approve it. Siigo distinguishes Draft, saved without being filed and with no CUFE; Accepted, accepted by DIAN; and Rejected, sent but rejected and requiring correction and resubmission in Siigo Nube. Setting enviar_dian to true does not prove acceptance; the Met reads and reports the exact status Siigo returned.
Because Siigo does not filter the catalog by name. The connector walks the pages and compares on the Meteor side, so on large catalogs the sweep can end up incomplete. When that happens the answer says so instead of claiming the product does not exist.
Step by step
Automations that use Siigo
Complete tasks, with the steps and the tools that run at each one.
Collect and manage
Other integrations in the same family
Want to see a Met running Siigo?
We will show you with your own account connected, not with a canned demo.