Robin connectors allow you to interact directly with the platform's data and objects — assets, forms, IoT devices — from a workflow. They are divided into two categories: triggers (triggers) which initiate the workflow, and the actions which execute in response.
¶ Triggers
¶ Asset Modified
Role : Triggers the workflow as soon as an asset is created, modified or checked in in Robin.
Configuration
- Select the type of asset concerned: only modifications to this type will trigger the workflow.
- Select a specific asset (optional): leave empty to trigger on all assets of the type.
This connector is particularly useful for reacting in real time to a change in business status, for example to update a work order on the ERP side as soon as a maintenance phase changes status, or to alert a quality manager when a batch is modified during manufacturing. It returns the modification date, the current fields of the asset, and, for modified fields, their previous value.
¶ Form Submitted
Role : Triggers the workflow when a Robin form is submitted by an operator.
Prerequisites: the relevant form widget must have the option “Trigger flows on submission” activated on the Robin side.
Configuration
- Select the targeted form in the list of forms with the activated trigger.
This connector allows you to connect an automated process directly to an operator action, for example to launch a quality control task upon submission of an end of inspection form, or to create a traceability asset upon validation of a weighing form at the start of the batch. It returns the asset created or edited by the form, with all its fields as well as the submission date.
¶ Robin Stocks
Note common to Robin shares: Fields marked in red in the control panel are mandatory. The options Continue on Failure et Retry on Failure (up to 4 attempts) are available for all actions and make it possible to manage the resilience of the workflow in the event of a one-off error (timeout, missing data, etc.).
¶ Create Asset
Role : Creates a new Robin asset of a given type, with the possibility of directly populating its fields upon creation.
Configuration
- Select the type of asset to create.
- Enter a Custom ID : mandatory if the asset type is not configured as auto-increment, optional otherwise.
- Complete the asset fields, organized by type:
- Text fields : text values.
- Number fields : numerical values.
- Date fields : date and time values, entered via the native selector or in ISO8601 (see https://en.wikipedia.org/wiki/ISO_8601).
- Enum fields : values from a closed list — the options available for each field are listed directly in the field label.
- For each field, click on + Add Item, select the Field target and fill in the Value — static or dynamically mapped from a previous step via the Data Selector.
This action is typically used in response to a form submission, for example to automatically generate a pre-populated declaration of non-conformity upon receipt of a defective part in MRO, or to create a "Lot" asset with its location and product reference fields at the start of cosmetic production.
¶ Update Asset
Role : Updates one or more fields of an existing Robin asset.
Configuration
- Select the targeted asset type: the list of available assets is filtered according to this type.
- Identify the asset to modify (required): select a specific asset or dynamically map the identifier from a previous step (ex. : Loop on Items item id).
- Complete the fields to update, organized by type:
- Text fields : text values.
- Number fields : numerical values.
- Date fields : date and time values, entered via the native selector or in ISO8601 (see https://en.wikipedia.org/wiki/ISO_8601).
- Enum fields : values from a closed list — the options available for each field are listed directly in the field label.
- For each field to modify, click on + Add Item, select the Field target and fill in the Value — static or dynamically mapped from a previous step.
Only fields explicitly added via + Add Item will be modified. The other fields of the asset remain unchanged.
This is the most common action in a Robin workflow, used for example to update the status of a cosmetic bin after each manufacturing step, or to synchronize the actual end date of an MRO maintenance phase to a field usable by a third-party system.
¶ Archive Asset
Role : Archive a Robin asset (equivalent to a logical deletion: the asset is no longer active but remains traceable).
Configuration
- Select the type of asset to archive: the list of available assets is filtered according to this type.
- Identify the targeted asset (required).
This action makes it possible to automate the end of life of an asset without manual intervention, for example to archive an MRO tool as soon as it reaches its flight hours limit, or to remove a cosmetic container from the active pool after confirmation of its elimination at the end of the line.
¶ Pair Asset
Role : Associates an IoT device (tag, anchor) with a Robin asset.
Configuration
- Select the target asset type.
- Identify the asset to associate the device with.
- Choose it Pairing Mode : Determines whether the device is identified by its UID or serial number.
- Select the device to pair (list filtered according to pairing mode).
This connector is useful whenever an IoT device must be dynamically assigned to an asset, for example to automatically associate a BLE tag with a tool when it is received in the MRO workshop, or to pair a UWB tag to a cart when it is assigned to a cosmetic production line.
¶ Unpair Asset
Role : Unlinks the IoT device currently associated with a Robin asset.
Configuration
- Select the type of asset concerned.
- Identify the asset from which to unlink the device (required).
This action naturally complements Pair Asset in equipment rotation scenarios, for example to release the tag of a tool sent for external maintenance in order to reassign it to a replacement tool, or to dissociate the tag from a cosmetic container when it is archived.
¶ Filter Assets
Role : Retrieves a filtered list of Robin assets based on defined criteria, for use in subsequent workflow steps.
Configuration
- Select the type of asset to filter (VZO).
- Set archiving status:
False (active)= active assets,True= archived assets. - Inform the Field filters (expert mode) (optional): JSON object where each key is a field identifier and the value is the matching criterion. To leave
{}to filter only by type and status.
The field Field filters accepts a list with the following elements:
- Date (
date_X):{ "field", "from"?, "to"? }— at least one limit, ISO 8601 with time zone, both included. - Number (
num_X):{ "field", "min"?, "max"? }— at least one limit, both included. - Text (
text_X):{ "field", "operator", "value" }— operator ∈equals(equal) |contains(contains) |starts_with(starts with) |ends_with(ends with) |regex. Case insensitive by default.regexis validated on the server side; unsafe reasons are rejected. - Enumeration (
enum_X, more specialzoneetid):{ "field", "values": [...] }— at least one value.zone→ table of zone identifiers;id→ asset identifier table.
Example :
[
{
"field": "date_30",
"from": "2026-05-01T00:00:00Z",
"to": "2026-05-31T23:59:59Z"
},
{
"field": "num_1",
"min": 10,
"max": 50
},
{
"field": "text_86",
"operator": "contains",
"value": "BIN"
},
{
"field": "enum_1",
"values": [
"Container",
"Plateau"
]
},
{
"field": "zone",
"values": [
282,
315
]
},
{
"field": "id",
"values": [
"BIN-000154",
"BIN-000155"
]
}
]
This action is generally used before a loop Loop on Items, for example to retrieve all MRO tools whose status is "En attente de maintenance" in order to process them sequentially, or to list the active batches of a cosmetic line and calculate a load indicator in real time.
This page does not seem clear to you or do you need help? Do not hesitate to contact us at support@zozio.tech !