> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/connectors/weclapp.md).

# weclapp connector

The weclapp connector: exchange purchase orders, supplier invoices, articles and serial numbers between equipme and your weclapp ERP – connection, triggers, actions, examples.

**Path:** sidebar → **"Automation" → "Workflows"** → flow designer → connector **"Weclapp"**

With the **weclapp connector**, you connect equipme in [workflows](https://hub.equipme.io/dokumentation/automation/workflows.md) with your **weclapp** ERP. Orders and invoices from equipme reach your accounting without retyping, and article or serial number data from weclapp becomes available in equipme.

## What for?

* **Orders into the ERP:** Create an approved order from equipme as a purchase order with your supplier in weclapp.
* **Invoices into accounting:** Record new invoices from equipme as supplier invoices in weclapp – including cost center and cost type.
* **Serial numbers for devices:** Retrieve serial numbers from weclapp and write them to the matching assets in equipme.
* **Keep the article master in sync:** When a new article is created in weclapp, notify the team or update data in equipme.
* **Track shipments:** Retrieve shipments from weclapp and pass the status on to employees or purchasing.

## Prerequisites

* The activated [Automation module](https://hub.equipme.io/dokumentation/automation.md)
* A **weclapp account** (tenant) with a user who may read and edit the required areas (e.g. purchasing, accounting, warehouse)
* The **API token** of this user (in weclapp under the user's personal settings)
* For the triggers: the user must be allowed to create webhooks in weclapp

## Setting up the connection

1. Copy the user's **API token** in weclapp and note the **tenant name** – the first part of your weclapp address (for `mycompany.weclapp.com` it is `mycompany`).
2. In the flow designer, drag a component of the weclapp connector onto the canvas (e.g. *ListArticles*).
3. Click **Connect account** and enter:
   * **Tenant** – the tenant name
   * **Token** – the API token
4. The connection is checked against weclapp and saved under the tenant name. It is then available in all weclapp components and appears under **"Accounts"**.

{% hint style="info" %}
In the flow designer, the components carry their technical name (e.g. *AddPurchaseOrder*). Select fields such as "Sales channel", "Warehouse", "Payment method" or "Cost center" load their values directly from your weclapp tenant.
{% endhint %}

## Triggers

| Component         | Fires when …                                                       |
| ----------------- | ------------------------------------------------------------------ |
| NewArticle        | a new article is created in weclapp. Returns the complete article. |
| ChangedSalesOrder | a sales order is changed in weclapp. Returns the complete order.   |

Neither trigger has settings. Once the flow is started, weclapp reports the event to equipme immediately; there is no periodic polling.

## Actions

### Customers and articles

| Component     | Purpose                          | Key options                                                                                                                                         |
| ------------- | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddCustomer   | Create a customer (organization) | Required: "Company", "Country code", "Sales channel"; optional email, "Customer number", address, contacts, "Additional fields" (custom attributes) |
| ListCustomers | List customers                   | "Filter"                                                                                                                                            |
| GetArticle    | Read an article                  | "Article ID"                                                                                                                                        |
| ListArticles  | List articles                    | "Filter"                                                                                                                                            |

### Purchasing

| Component          | Purpose                                 | Key options                                                                                                                                                                       |
| ------------------ | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddPurchaseOrder   | Create a purchase order with a supplier | Required: "Supplier", "Warehouse"; items, shipping costs, payment type and terms, "Delivery conditions", planned delivery dates, service period, tracking number and tracking URL |
| AddPurchaseInvoice | Record a supplier invoice               | Required: "Supplier"; "Invoice number", "Invoice date", "Due date", items, shipping costs, "Cost center", "Cost type", "Booking date", "Booking text", "Payment block"            |

### Sales and contracts

| Component                       | Purpose                                | Key options                                                                                                                          |
| ------------------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| AddSalesOrder                   | Create a sales order                   | Required: "Customer ID", "Sales channel"; differing delivery and billing address, items, payment method, "Warehouse", delivery dates |
| GetSalesOrder / ListSalesOrders | Read sales orders                      | "Order ID"                                                                                                                           |
| CancelSalesOrder                | Cancel or manually close a sales order | "Order ID"                                                                                                                           |
| AddSalesInvoice                 | Create a sales invoice                 | Required: "Customer ID", "Sales channel"; items, due date, dunning block, cost center                                                |
| AddContract                     | Create a contract                      | Required: "Label", "Sales channel"; contract partner, term, status, items, billing type, reminder                                    |

### Warehouse and logistics

| Component                           | Purpose             | Key options                    |
| ----------------------------------- | ------------------- | ------------------------------ |
| GetShipment / ListShipments         | Read shipments      | "Shipment ID" or "Filter"      |
| GetSerialNumber / ListSerialNumbers | Read serial numbers | "Serial Number ID" or "Filter" |

### Specifying items

Orders, invoices, sales orders and contracts accept items in two ways:

* **"Items (static)"** – enter items one by one in the form: "Article ID", "Position title", "Description", "Quantity", "Unit" and price. Items with quantity 0 are skipped.
* **"Items (dynamic)"** – pass a ready-made item list from a previous step, e.g. the items of an order from equipme.

Shipping costs work the same way ("Shipping costs (static)" / "Shipping costs (dynamic)").

### Filters in list actions

*ListArticles*, *ListCustomers*, *ListShipments* and *ListSerialNumbers* offer a **"Filter"** made of conditions: "Property" (field name in weclapp, e.g. `articleNumber`), "Operator" (e.g. "equals", "like expression", "is null") and value. Conditions can be combined with AND and OR.

## Examples

### Create an order from equipme as a purchase order

1. **Trigger:** *Equipme › New Order Request* or a step from the "Equipme Approval" module after approval (see [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md)).
2. **Weclapp › ListArticles** with the filter `articleNumber` "equals" part number to find the matching "Article ID".
3. **Weclapp › AddPurchaseOrder** with supplier, warehouse and items.
4. **Email › Send Email:** order number to purchasing.

### Invoices from equipme into accounting

1. **Trigger:** *Equipme › New Invoice*.
2. **Weclapp › AddPurchaseInvoice** with supplier, invoice number, invoice and due date and the **"Cost center"** matching the cost center in equipme.
3. Optionally set "Payment block" until the invoice has been checked.

### Write serial numbers to assets

1. **Trigger:** scheduler (e.g. daily).
2. **Weclapp › ListSerialNumbers** with a filter for new entries.
3. **Equipme › List Service Instances** to find the matching asset.
4. **Equipme › Set Service Instance Metadata:** save the serial number as metadata – visible in equipme under ["Additional information"](https://hub.equipme.io/dokumentation/organization/additional-information.md).

## Notes and limitations

* The triggers only react to **new articles** and **changed sales orders**. For other events, combine a scheduler with a list action.
* List actions return the **first result page** from weclapp, not necessarily all entries. Use filters to keep the result small.
* *ListSalesOrders* has no filter.
* A differing delivery or billing address is only applied if a "Country code" is entered there.
* All actions work with the permissions of the weclapp user whose token you use.

## Troubleshooting

| Problem                      | Cause / solution                                                                                                                        |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| "Connect account" fails      | Check the tenant name (only the first part of the address, without `.weclapp.com`) and the token.                                       |
| Select field stays empty     | The connection is missing or the user may not read the area (e.g. warehouse, cost centers).                                             |
| Trigger does not fire        | Is the flow started? May the user create webhooks in weclapp? After changes, stop and restart the flow.                                 |
| Error when creating a record | Required fields are missing or IDs do not match (e.g. "Customer ID", "Article ID"). Determine IDs beforehand with a list or get action. |
| List incomplete              | Use filters; without a filter only the first page is returned.                                                                          |

The logs under **"Insights"** help with errors. For assistance, contact [Support](https://hub.equipme.io/dokumentation/help/support.md) and include the flow name, component and error message.

## Frequently asked questions

**Where do I find the "Article ID" or "Customer ID"?**

It is the internal ID of the record in weclapp, not the article or customer number. Determine it with *ListArticles* or *ListCustomers* and a filter on the number.

**Do I need a separate connection for each flow?**

No. One connection per weclapp tenant is enough; it is available to all flows under "Accounts".

**Can I fill custom fields from weclapp?**

For *AddCustomer* and *AddSalesOrder* via "Additional fields (dynamic)". You pass the values as a list from a previous step.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/dokumentation/automation/connectors/weclapp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
