> 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/pro/automation/workflows.md). # Workflows Create, start, share and monitor workflows (flows) in Equipme Pro: triggers, actions, variables, modifiers, filters, webhooks, error notification and typical provider examples. **Path:** "Automation" → "Workflows" A **flow** consists of a **trigger** (what starts the process), **actions** (what happens) and optionally **conditions** (when something happens). You build flows via drag & drop in the **flow designer**. Operation in Equipme Pro is the same as in the customer portal; the difference lies in the available components: in Pro, you mainly use the **"Equipme Pro"** module of the equipme connector (see [equipme connector – Pro modules](/pro/automation/connectors/equipme-pro.md)). ## The flow list * **"Create Flow"** creates a new flow. * Filters: "Running flows", "Stopped flows", "My flows", "Shared with others", "Shared with me". Sort by modification or creation date, list or tile view. * Menu per flow: "Open", "Rename", "Insights" (logs), "Clone" (copy), "Share" and "Remove" (delete; **deleted flows cannot be restored**). * When **sharing**, you choose with whom (by email, scope or domain) and which rights apply: "Read", "Start", "Stop". ## Building a flow 1. **"Create Flow"** → open the flow. The designer opens in full screen. 2. On the left, you choose components: * **Utilities**, e.g. Filter, Converter, Timer, Scheduler, Webhook, HTTP and Tasks, * **Applications**, e.g. Equipme Pro, Equipme, Microsoft, email and many more. 3. Drag a **trigger** onto the canvas, e.g. *New Sales Order* from the "Equipme Pro" module, a schedule (Scheduler) or a webhook. 4. Add actions and connect the components. 5. On the right, you configure the selected component. You connect accounts via **"Connect account"**. 6. **Start** the flow. A flow that has been saved but not started does not run. In the designer you will also find undo/redo, zoom, align, logs and, in the menu, "Rename", "Share", "Change Description" and export as SVG/PNG or print. ## Passing data between components * **Variables:** Use the variable picker to use values from previous components, e.g. the order number of a new customer order in an email. * **Modifiers:** Click an inserted variable to transform it, e.g. convert text to uppercase, shift a date, divide a number, filter, join or sum lists. Modifiers can be chained. ## Logic * **Filters:** Only let data through if a condition is met, e.g. "Contains", "Equal", "Not Equal", "Greater/Less Than", "Range" or "Is Not Empty". You combine multiple conditions with "And". * **Scheduling:** Start flows once, recurringly or at fixed times – e.g. update prices from a distributor catalog every night. * **Webhooks:** A webhook trigger provides a URL through which other systems start the flow, e.g. your warehouse management system when goods are issued. If you respond later with your own response component, turn off "Immediate Response". * **HTTP:** Call any interface with GET, POST, PUT or DELETE. * **Follow-up questions:** You integrate human input via web forms ("Forms" module), e.g. a follow-up question to the warehouse manager before shipping. ## Finding errors * **Logs** in the designer or **"Insights"** show every execution with status, components, timestamp, message and error. * **Getting notified of errors:** Add the **"OnError"** trigger and connect it, e.g., with "SendEmail". The trigger checks regularly and only reports errors that were actually logged. The flow must be started. {% hint style="warning" %} Flows that change the status of fulfillment positions or purchase orders immediately affect what your customers see (e.g. status messages and emails). Test such flows with a test customer first. {% endhint %} ## Examples for providers ### Passing new customer orders to the ERP 1. **Trigger:** *Equipme Pro › New Sales Order*, optionally restricted to specific customers ("Customers"). 2. **Action:** Create the order in the ERP (ERP connector or HTTP). 3. **Action:** Save the ERP order number as metadata on the service instance (*Set Service Instance Metadata Entry*) or remember it in a table ("Tables"). 4. **Email › Send Email:** Confirmation to sales. ### Taking over a distributor's shipping status 1. **Trigger:** *Scheduler* (e.g. hourly). 2. **Action:** Retrieve open purchase orders (*List Dropshipping Orders*, filtered by status). 3. **Action:** Query the shipment status at the distributor (distributor connector or HTTP). 4. **Action:** Set the status in Pro (*Update Dropshipping Order Status*, e.g. "Dispatch Delivery"). ### Creating parcels from the shipping system 1. **Trigger:** *Equipme Pro › New Fulfillment Order*, filtered by transaction type "Order". 2. **Action:** Create the shipment in the shipping system. 3. **Action:** *Add Fulfillment Parcel* with tracking number ("Tracking number"), tracking link, shipping carrier ("Carrier") and the affected fulfillment positions. You can find more components and examples under [equipme connector – Pro modules](/pro/automation/connectors/equipme-pro.md). ## Frequently asked questions **My flow doesn't trigger.** Check whether the flow has been started and whether the trigger's filters (e.g. "Customers", "After", "Transaction types") match the expected data. **Can I see a customer's flow in Pro?** No. Flows that a customer builds in their customer portal belong to their workspace. In Pro, you only see your own company's flows. --- # 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/pro/automation/workflows.md?ask=&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.