Configure Monday.com triggers
Route supported Monday.com changes into CopyHero workflows.
Monday.com triggers route supported Monday.com changes into a CopyHero workflow. This guide covers only the released Triggers tab; it does not cover unreleased folder-sync behavior.
Prerequisites
Connect Monday.com and create the target CopyHero workflow first.
Steps
- Open Settings → Integrations → Monday.com.
- Select Triggers.
- Choose the new-trigger action.
- Select the available Monday.com source, event, and CopyHero workflow.
- Save and confirm the trigger appears in the list.
Options
The form presents the sources and event options supported by the connected workspace. Select only values available in the interface.
Import settings
The Import tab sets what every run imports with, the same way the Import dialog does:
- Import profile fills the tab from a saved import profile. Changes you make afterwards apply only to this trigger. Later edits to the profile do not change a saved trigger.
- Store and Workflow choose where each product goes and which workflow runs.
- The import options (tags, collections, sales channels, product status, inventory, vendor and product type, image handling, slideshow, and metafield set) apply to every product the trigger imports.
Collections, sales channels, and inventory locations belong to one store. If you switch the store, they are cleared and you pick them again for the new store.
Field mapping
The Field mapping tab reads each Monday.com item:
- Product tells the workflow which product the item imports: a Product URL or an Internal product ID, taken from a board column, a fixed value, or an expression. It is required.
- Custom fields map any other workflow input per item. A value from a custom field overrides the matching import option for that item. When the item's column is empty, the import option applies instead.
Each workflow input can be mapped once. To combine values, such as a fixed tag and a column, use one Expression row.
Expressions
Choose Expression as the mode of a custom field to compute its value per item. An expression is a short formula without {{ }}, for example upper(item.name). Select Insert variable to add a board column, a trigger variable, a helper, or an operator; each column shows its type and a sample value from the board. In the expression, each column reference shows as a chip with the column title, and a column that is not on the board is flagged as Not on this board.
The Preview below the field mapping renders the mapping while you type, against the board's first item or an item ID you enter. Each mapping row shows its previewed value, or that the import option applies because the result is empty. Errors show under the expression before you save.
You can use these variables:
item.nameanditem.id: the Monday.com item.columns["<column_id>"].text: a column's value as Monday.com shows it, for example a status label. An empty column reads as"". A date column reads as2026-10-08, or2026-10-08 14:30with a time, in your Monday.com time zone.columns["<column_id>"].value: the column's raw value as JSON text.import_options: the options from the Import tab, for exampleimport_options.tags.event: the Monday.com event, for exampleevent.columnIdfor a column-change trigger. Only a real run has an event, so the Preview and the Test preview skip a field whose expression readseventand mark it Not previewable. A real run evaluates it.
Fixed text needs quotes: write "Spendora", not Spendora. A word without quotes is read as a variable, and the expression fails. For a value that is the same on every item, the Static value mode is simpler.
Operators
| Operator | Use | Example |
|---|---|---|
"…" | Fixed text | "Spendora" |
[a, b] | A list | ["comp-test", "summer"] |
+ | Joins two lists, or adds one value to a list | ["comp-test"] + columns["date_col"].text |
~ | Joins text | item.name ~ " (Monday)" |
x if condition else y | Picks a value | "Sale" if columns["status"].text == "Top" else "" |
==, != | Equal, not equal | columns["status"].text != "" |
in | Contains | "Top" in columns["status"].text |
and, or, not | Combine conditions | columns["a"].text == "x" and not columns["b"].text |
Helpers
You can call these helpers: upper, lower, title, trim, replace, split, join, first, last, length, round, sum, avg, min, max, format_price, and format_number.
Methods such as .split() or .strip() are not available. Use the helper instead, for example split(columns["date_col"].text, "-") or trim(item.name).
Add tags
A mapped Tags value replaces the tags from the Import tab. Tags accept a list or a comma-separated text. An empty entry in the list is dropped, and a number becomes text.
- A fixed tag plus a date column:
["comp-test"] + columns["date_col"].text. When the date is empty, onlycomp-testis added. - The same, keeping the import tags:
import_options.tags + ["comp-test"] + columns["date_col"].text. bestsellerwhen the Status column isTop, and only the import tags otherwise:
import_options.tags + ["bestseller"] if columns["status"].text == "Top" else import_options.tagsEmpty results and errors
- If an expression returns nothing, such as an empty text or an empty list, the import option applies instead.
- If an expression fails for an item, for example because it names a column the item doesn't have, that run fails. Activity shows the field and the reason. No workflow starts, and the trigger stays enabled.
- In a Monday recipe, a failed expression fails that recipe run too, and no workflow starts. Monday shows the reason, Field mapping failed, in the automation's activity, does not retry the run, and keeps the automation on.
- An expression that takes longer than 1 second, uses too much memory, or builds a very large value fails the same way.
- CopyHero checks every expression when you save the trigger: it must be valid, use only the variables above, and be at most 2,000 characters long.
Duplicate a trigger
To reuse an existing setup instead of filling the form again:
- Select the copy action on the trigger's row.
- Review the copied settings. The copy opens with the original's board, event, conditions, import settings, field mapping, and enabled state.
- Adjust what differs, then select Create copy.
A copy of an enabled trigger is enabled. Change the board, column, or conditions before you save it, or an unedited copy runs the workflow a second time on the same event. To park the copy instead, turn Enabled off in the form.
Expected result
An eligible Monday.com event can start the selected CopyHero workflow.
When your administrator turns on trigger grouping, runs a trigger starts in quick succession appear as one import in workflow history. Each run still starts right away.
If something goes wrong
Check the connection, selected source, and workflow. Delete or edit a trigger from the list if it was configured incorrectly.
If a product URL is invalid, CopyHero rejects that run before creating a workflow. The error appears in Activity. It is not retried automatically, and the trigger stays enabled even if several items contain invalid URLs. Correct the URL and send a new matching event to try again.
Once an item's column conditions match, an invalid product URL is reported as an error even when a platform filter is configured. Valid URLs from a different platform are still skipped.
The Test preview uses an item's existing library product when folder sync is enabled and the item is already linked to that product. It previews the board event without starting a workflow or creating a new library product.
Product URLs must be complete http:// or https:// URLs. This check only
validates the URL's format; it does not open the page or check whether the
product exists. A Monday recipe reports invalid URLs in Monday's automation
activity with an error, without disabling the automation.