Bind ERP

Connect AI agents to Bind ERP, a Mexican cloud ERP for small and medium businesses. Agents raise sales orders and quotes, maintain the product catalog, issue purchase orders, and keep inventory and contact records aligned.

48 actions API key available

Platform Documentation ↗

An order is confirmed in the storefront, or a scheduled order sweep runs

List Clients with an OData filter on RFC resolves the buyer, or Create Client registers a new one

List Products With Price And Inventory returns the price list and warehouse stock behind each line

Create Order records the pedido against the client's delivery address

The numeric fiscal codes on the document are checked against what the client record carries

The finance owner receives the assembled document with its lines, totals, and codes

A person approves before Create Invoice stamps the CFDI

What This Integration Enables

Bind ERP is a Mexican cloud ERP, and the single fact that shapes every flow built against it is that a sales invoice here is not a document you print. Setting Is Fiscal Invoice to true on Create Invoice stamps a CFDI, and Download Invoice XML only returns content for invoices that have been stamped. Once that has happened the document has left the building in a way a draft never does: the correction path in this connector is Create Credit Note against the existing invoice, or Delete Invoice, which permanently deletes and cancels it and cannot be undone. There is no edit. That is why an integration to Bind should be judged less on how quickly it can raise a document and more on how well it holds the line before one gets stamped.

What the connector covers is the whole commercial cycle around that moment. Sales orders and quotes, the product and service catalog, clients, prospects and providers, purchase orders, inventory by warehouse with manual adjustments, and the account profile. Every list action speaks OData, exposing $filter, $orderby, $top, and $skip as Filter, Order By, Top, and Skip, and returning an envelope of { value, nextLink, count }, which makes precise server-side queries the normal way to work rather than a client-side filter over a full pull. Authentication is a single API key sent as an Authorization: Bearer token against https://api.bind.com.mx/api, generated inside Bind under Configuracion, API, with no separate login or token-exchange step; be aware that the failure shape is inconsistent, since a missing header returns 401 while a wrong key returns HTTP 500 with a body saying the API Key is invalid, and this connector surfaces both as a Bind ERP API error rather than letting a 500 read as an outage. Several fields are numeric catalog codes, including CFDI use, payment method, payment term, tax regime, credit note type, and purchase order status; Bind publishes no enumeration for them, so they are plain number or string inputs and the correct value comes from your own configuration rather than from a dropdown. Update Product and Update Client are full-replacement PUTs, so send the complete object or omitted fields may be cleared. This connector ships no triggers. Bind does offer webhook subscriptions, and Create WebHook Subscription registers a target URL of your choosing, but that subscribes an external endpoint rather than creating a FlowRunner trigger, and Bind publishes no signature or verification scheme for the payloads it delivers. Change detection is a scheduled list action, for example List Invoices ordered by date. Agents assemble the document. Stamping it is where human-in-the-loop orchestration belongs.

Without FlowRunner

The storefront and the ERP reconciled by hand Orders are retyped into Bind, and the invoice waits until somebody has an afternoon free

Fiscal codes copied from the last document CFDI use, payment method, and payment term are carried across from whatever was issued before

Stock trusted rather than read A purchase order goes to a provider against a number nobody checked against the warehouse

With FlowRunner

Orders arrive as records Client, address, price list, warehouse, and lines are all resolved before a document is created

Codes checked against the client record The numeric codes on a document are compared with the client's own setup before anything is stamped

Purchasing reads the warehouse first Inventory by warehouse and the applicable price list are read before a purchase order is raised

Use Case Scenarios

A storefront order that becomes a properly addressed document

An order is confirmed in Shopify or WooCommerce. The agent runs List Clients with an OData filter on the buyer's RFC to find whether they already exist, since a duplicate client record in Bind splits credit terms and price list across two entries and both will look plausible. Where the buyer is new, Create Client registers them with the legal name, commercial name, RFC, credit days, credit amount, price list, and accounting number Bind requires. Get Client Addresses returns the delivery and billing addresses, and the address ids from that call are what Create Order actually needs. List Products With Price And Inventory resolves each line against the right warehouse and price list, so the document is priced from the catalog rather than from the storefront's own idea of the price. Create Order writes the pedido. Everything up to this point is reversible. What comes next is not, and it waits for a person.

Restocking that reads the warehouse before it commits to a provider

On a schedule the agent calls List Warehouses and Get Inventory By Warehouse with an OData filter on the products that matter, comparing on-hand quantities against reorder points held in Google Sheets. Where a line falls short, List Providers resolves the supplier, or Create Provider registers a new one with its legal name, RFC, credit days, credit amount, and SAT company account. Create Purchase Order raises the orden de compra against that provider with its warehouse, currency, status code, and product lines. When the merchandise arrives, Add Inventory Adjustment records the movement with a positive quantity, and the same action handles shrinkage and count corrections with a negative one. The purchasing summary posts to Slack so the person who owns supplier relationships sees what was raised in their name before the provider calls about it.

Collections, and the correction that is not an edit

On a schedule the agent runs List Invoices with an OData filter on date and status, List Invoice Payments for what has already been received against each one, and Download Invoice PDF to attach the document to a reminder sent through Gmail. When a payment clears in the bank feed, Register Invoice Payment records it against the invoice with the receiving bank account, amount, date, reference, and payment term code. The interesting case is the disputed invoice. Because a stamped document cannot be edited, the only instruments available are Create Credit Note against the original invoice, or Delete Invoice, which permanently cancels it. Both change what the customer owes and what the company has recorded, so the agent's job is to assemble the case rather than to close it: the original invoice through Get Invoice, its payments through List Invoice Payments, the CFDI itself through Download Invoice XML, and the customer's account through Get Client. The controller decides which instrument applies, and the agent runs the one they chose.

Human-in-Loop Highlight

Create Invoice with Is Fiscal Invoice set to true is the operation to gate, and the reason is not that an agent might invoice the wrong customer. It is that the document will be perfectly well formed and still wrong. Several of the fields on a Bind invoice are numeric catalog codes, including CFDI use, payment method, and payment term, and Bind publishes no enumeration for them, so they arrive at the API as plain numbers. Nothing validates that the number an agent supplied is the number this customer's setup calls for. A code carried over from the last document, or defaulted in a mapping written six months ago for a different kind of sale, produces a stamped CFDI whose totals are right, whose customer is right, and whose fiscal treatment is not. The correction is not an edit: this connector offers Create Credit Note against the invoice, or Delete Invoice, which permanently cancels it, and both of those are events the customer and the accountant both see. So the agent stops one step short of the stamp. It assembles the document, resolves every line against List Products With Price And Inventory so the price comes from the catalog, reads the buyer through Get Client so the credit days, credit amount, and price list on the record are visible next to the ones on the document, and posts to the finance owner in Slack: "Invoice ready for Ferretería del Norte, 6 lines, 42,300 MXN, warehouse Monterrey, price list Mayoreo. CFDI use is set to 3 and payment method to 3, both carried from the client record. Credit days on the client are 30, and the document is set to the same. Create Invoice with Is Fiscal Invoice true will stamp the CFDI, after which the only corrections available are a credit note or a permanent cancel. Stamp it, stamp it as a non fiscal invoice for now, or send it back?" A person answers, and the agent stamps only what was released. Delete Invoice, Delete Order, Delete Quote, Delete Product, and Delete Client sit behind the same gate because each is permanent, and Update Product and Update Client join them whenever a partial payload is in play, since both are full-replacement PUTs where an omitted field may be cleared. This is the digital andon cord placed on the one action in this connector that produces a document nobody can quietly take back.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

48 actions

Sales invoices

List Invoices Returns a paginated list of sales invoices, known as ventas, with OData filter, order, top, and skip options. The response is an envelope carrying a `value` array and a `count`.
Get Invoice Returns the full detail of a single sales invoice, looked up by its Bind ID or by its consecutive number.
Create Invoice Creates a sales invoice for a client. Requires the client, currency, location, warehouse, price list, and CFDI use, plus at least one product or service line. CFDI use, discount type, and payment term are numeric codes following the Bind ERP and SAT catalogs. Set Is Fiscal Invoice to true to stamp a CFDI, which is why this action runs behind a person.
Delete Invoice Permanently deletes and cancels a sales invoice, by Bind ID or consecutive number. Cannot be undone.
Register Invoice Payment Registers a payment against an existing invoice, requiring the invoice, the bank account receiving the payment, the amount, a date, a reference, and the payment term code.
List Invoice Payments Returns the payments already registered against an invoice, with OData filter, order, top, and skip options. The read behind any collections or dispute question.
Download Invoice PDF Downloads the PDF of a sales invoice, stores it in FlowRunner Files, and returns the stored file URL, ready to attach to an email or a ticket.
Download Invoice XML Downloads the CFDI XML and stores it in FlowRunner Files, returning the URL. Only returns content for invoices that have actually been stamped as fiscal CFDIs, which makes it a reliable check on whether a stamp happened.
Create Credit Note Creates a credit note against an existing sales invoice, optionally naming the specific product lines being credited. Payment method, payment terms, and type are numeric codes. This is the correction path for a document that has already been stamped.

Orders and quotes

List Orders Returns a paginated list of sales orders, known as pedidos, with OData options.
Get Order Returns the full detail of a single sales order by its Bind ID.
Create Order Creates a sales order for a client. Requires the client, delivery address, currency, location, warehouse, price list, and order date, plus at least one product or service line. Address ids come from Get Client Addresses.
Delete Order Permanently deletes a sales order. Cannot be undone.
List Quotes Returns a paginated list of quotes, known as cotizaciones, with OData options.
Get Quote Returns the full detail of a single quote by its Bind ID.
Create Quote Creates a quote, addressed either to an existing client or to an existing prospect, requiring the location, currency, price list, and at least one item.
Delete Quote Permanently deletes a quote. Cannot be undone.

Catalog

List Products Returns a paginated list of products with OData filter, order, top, and skip options.
Get Product Returns the full detail of a single product by its Bind ID.
Create Product Creates a product, requiring a title, cost, price, currency, and code.
Update Product Updates a product. This is a full replacement, so send the complete product state: fields omitted from the request may be cleared.
Delete Product Permanently deletes a product. Cannot be undone.
List Products With Price And Inventory Returns products with their price and inventory levels for a specific warehouse and price list. This is the action that puts a real price and a real stock figure behind a document line.
List Services Returns a paginated list of services, known as conceptos de venta, with OData options.
Create Service Creates a service, requiring a code, title, currency, SAT company account, and measurement unit.

Clients, prospects, and providers

List Clients Returns a paginated list of clients with OData options. Filter on RFC to resolve a buyer before writing anything.
Get Client Returns the full detail of a single client by its Bind ID, including the credit terms and price list a document should agree with.
Create Client Creates a client, requiring legal name, commercial name, RFC, credit days, credit amount, price list, and accounting number. Payment method and payment term are numeric SAT catalog codes.
Update Client Updates a client. A full replacement, so send the complete client state or omitted fields may be cleared.
Delete Client Permanently deletes a client. Cannot be undone.
Get Client Addresses Returns the delivery and billing addresses registered for a client. Use the returned address ids when creating orders.
List Prospects Returns a paginated list of prospects, known as prospectos, with OData options.
Create Prospect Creates a sales prospect. Only a name is required; company, email, and phone are optional.
List Providers Returns a paginated list of providers, known as proveedores, with OData options.
Create Provider Creates a provider, requiring legal name, commercial name, RFC, credit days, credit amount, and SAT company account.

Purchasing

List Purchase Orders Returns a paginated list of purchase orders, known as ordenes de compra, with OData options.
Get Purchase Order Returns the full detail of a single purchase order by its Bind ID.
Create Purchase Order Creates a purchase order for a provider, requiring the provider, warehouse, RFC, credit days, currency, status code, and one or more product lines. Status is a numeric code from the Bind ERP catalog.

Inventory

Get Inventory By Warehouse Returns the inventory of a specific warehouse with OData filter, order, top, and skip options. The read that should precede any restock decision.
Add Inventory Adjustment Registers a manual inventory adjustment for a product in a warehouse. A positive quantity increases stock and a negative quantity decreases it, so goods received and shrinkage both go through the same action with opposite signs.
List Warehouses Returns the list of warehouses, known as almacenes, with OData options.

Account

Get Company Profile Returns the profile of the Bind ERP company the API key belongs to.
Get User Profile Returns the profile of the Bind ERP user that owns the API key. Useful for confirming which account a run is about to write into.

Webhooks

List Available WebHooks Returns the catalog of webhook events Bind ERP can send, each with its ID, name, and description. The IDs from this call are what a subscription needs.
Get WebHook Sample Data Returns an example of the data model a given webhook event delivers, so the flow that consumes it can be designed before anything is registered.
List WebHook Subscriptions Returns the subscriptions currently registered for the account, with OData options. Worth auditing before adding another.
Create WebHook Subscription Subscribes a target URL to a Bind ERP webhook event, after which Bind POSTs to that URL each time the event occurs. This registers an external endpoint of your choosing; it does not create a FlowRunner trigger, and Bind publishes no signature scheme for the deliveries, so treat an arriving payload as a prompt to re-read the record.
Delete WebHook Subscription Deletes a webhook subscription by its ID, stopping delivery of that event to the target URL.

Frequently Asked Questions

What can FlowRunner do with Bind ERP?

FlowRunner agents can run List Invoices, Get Invoice, and Create Invoice in Bind ERP, plus 45 more actions.

Does connecting Bind ERP to FlowRunner require OAuth?

No. Bind ERP connects to FlowRunner with an API key, no OAuth flow required.

Can Bind ERP trigger a FlowRunner workflow automatically?

Bind ERP doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Bind ERP

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us