New customers from the dispatch system onto the board each night, each only once
Each night, a Make scenario reads the customer list from a courier company's dispatch system through its web-service API, compares it with the accounts already on a monday.com board, and creates only the new ones, fetching each one's details first. The follow-up update runs only when exactly one matching item is found.
Where this applies
Any team that tracks accounts on a board and needs new customers from a dispatch, ERP or billing system to appear there without a native integration.
- nightly runs, no errors
- 33
- duplicate checks before a create
- 2
- exact match required before an update
- 1
The problem
When a courier company opens a new customer account in its dispatch system, the account-management side needs to see it, to follow up and track activation. The dispatch system has no integration with the board, so the copy is done by hand, late, or not at all.
A nightly copy is easy to write badly: re-create every customer each night and the board fills with duplicates; update by a loose match and the wrong account is overwritten.
What we built
Read both lists, compare in memory
The scenario fetches the customer list from the dispatch system over HTTP and lists the items already on the board. A text aggregator turns the board's customer ids into one string, and a filter after the iterator lets through only customers whose id is not in it.
Details only for the new
For each new customer, a second API call fetches the full account details, so the heavier request is made only for accounts that will actually be created.
Search before create
Before creating, the board is searched once more for the customer, and the item is created only if nothing is found.
Exactly one, or nothing
After creating, the scenario searches again and fills the remaining columns only when exactly one item matches. If it finds two, it does nothing rather than guess.
The outcome
Live since September 2026. From 18 September to 20 October it ran 33 times without an error, using 132 credits.
Where it stops
It adds new customers and does not carry later changes to existing accounts across. It runs once a night, so an account opened in the morning appears the next day.
Built with
- Make.com
- monday.com
- HTTP
- REST API
Patterns used
- Set difference by id
- Fetch details only for the new
- Search before create
- Exactly-one guard
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no