> 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).

# Managing workflows

Managing flows in Equipme Pro: flow list and filters, create, start and stop, change, rename, clone, share and remove flows, logs and examples for providers.

**Path:** "Automation" → "Workflows"

Under **"Workflows"** you find all flows you have access to. From here you create new flows, start and stop them and open them in the [flow designer](https://hub.equipme.io/pro/automation/flow-designer.md). Which flows you see depends on the selected area **"Personal"** or **"Team"** (see [Automation at a glance](https://hub.equipme.io/pro/automation.md#choosing-the-area-personal-or-team)).

## The flow list

Each flow shows its name, its state ("Running" or "Stopped"), whether it is shared ("Private", "Shared with others", "Shared with me") as well as its creation and modification date.

* **View:** tiles ("Grid view") or list ("List view").
* **Sort:** "Last Modified" or "Last Created".
* **Filter:** "Running flows" and "Stopped flows" (state) as well as "My flows", "Shared with others" and "Shared with me" (origin). Active filters appear at the top of the list and can be removed there.

## Creating a flow

1. Check the area at the top ("Team" for shared, productive flows).
2. Click **"Create Flow"**. The new flow opens in the [flow designer](https://hub.equipme.io/pro/automation/flow-designer.md); the Pro sidebar collapses.
3. Give the flow a meaningful name, add a trigger and actions and test it.
4. Use the back arrow in the Pro header to return to the list. Your changes are kept.

## Starting and stopping

A new flow is **stopped** and does nothing until you start it.

* **Start:** In the flow designer, click **"Start flow"** at the top. From now on, the flow reacts to its trigger.
* **Stop:** Click **"Stop flow"**. The flow no longer reacts; configuration and logs are kept.

{% hint style="warning" %}
Flows using the "Equipme Pro" module affect your customers immediately – for example when they change the status of fulfillment positions or purchase orders or create parcels. Test such flows with a test customer first.
{% endhint %}

## Changing a running flow

If the flow designer offers **"Edit"** for a running flow, this creates a **draft**: you change and test the draft while the previous version keeps running, and apply it with **"Publish changes"**. If this option is not available, stop the flow, change it and start it again.

Plan changes to productive flows (e.g. the ERP connection) for quiet times and afterwards check in [Insights](https://hub.equipme.io/pro/automation/insights.md) that the next executions run without errors.

## Menu of a flow

The menu of a flow in the list offers:

| Entry          | Effect                                                                                                                                 |
| -------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **"Open"**     | Opens the flow in the flow designer.                                                                                                   |
| **"Rename"**   | Renames the flow.                                                                                                                      |
| **"Insights"** | Opens this flow's logs (see [Insights](https://hub.equipme.io/pro/automation/insights.md)).                                            |
| **"Clone"**    | Creates a copy – handy as a template, e.g. one flow per customer tenant. The copy is stopped. Check the selected accounts in the copy. |
| **"Share"**    | Shares the flow with others (see below).                                                                                               |
| **"Remove"**   | Deletes the flow. **Deleted flows cannot be restored.**                                                                                |

### Sharing flows

With **"Share"** you share a flow with others – useful mainly for flows in the "Personal" area. Everyone with automation access already sees flows in the "Team" area.

1. Choose the type of sharing:
   * **"Email"** – a specific person by their email address,
   * **"Scope"** – a user group,
   * **"Domain"** – everyone whose sign-in email ends with this domain (e.g. `company.com`).
2. Choose the permissions: **"Read"** (view the setup), **"Start"**, **"Stop"**.
3. Save with **"Update"**. Use **"Remove"** to withdraw a share.

Shared flows appear for recipients under the "Shared with me" filter.

## Good practice

* **Meaningful names:** e.g. "ERP – new customer orders to weclapp" instead of "New flow". Rename the components in the flow as well.
* **Maintain a description:** In the flow designer, record via "Change Description" what the flow does and who looks after it.
* **One flow per task:** Several manageable flows are better than one very large one.
* **One flow per customer tenant:** With Microsoft Intune or Entra ID, an account applies to exactly one tenant. Build a template and clone it per customer.
* **Test with test data:** Actions are really executed during testing too (see [Testing](https://hub.equipme.io/pro/automation/flow-designer.md#testing)).
* **Notice errors:** Add an error notification to important flows (see [Insights](https://hub.equipme.io/pro/automation/insights.md#getting-notified-of-errors)).

## 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, e.g. with the [weclapp connector](https://hub.equipme.io/pro/automation/connectors/weclapp.md) or [Business Central](https://hub.equipme.io/pro/automation/connectors/microsoft-business-central.md).
3. **Action:** Save the ERP order number as metadata on the service instance (*Set Service Instance Metadata Entry*) or remember it in a [table](https://hub.equipme.io/pro/automation/files-and-tables.md).
4. **Action:** Confirmation email 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.

### PSA ticket per fulfillment position

1. **Trigger:** *Equipme Pro › New Fulfillment Order*.
2. **Action:** Create a ticket in [Autotask](https://hub.equipme.io/pro/automation/connectors/autotask.md) with customer, product and order number.

You can find more components and examples under [equipme connector – Pro modules](https://hub.equipme.io/pro/automation/connectors/equipme-pro.md) and on the [connector](https://hub.equipme.io/pro/automation/connectors.md) pages.

## Frequently asked questions

**My flow doesn't trigger.**

Check whether the flow has been started ("Running") and whether the trigger's filters (e.g. "Customers", "After", "Transaction types") match the expected data. Some triggers only check for new data at intervals – wait one or two minutes. [Insights](https://hub.equipme.io/pro/automation/insights.md) provides clues.

**I can't find a flow anymore.**

Check the area at the top ("Personal" or "Team") and remove active filters.

**Can I restore a deleted flow?**

No. Create a copy with "Clone" before larger changes.

**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=<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.
