Pull records from your ERP
Most checks depend on data you keep somewhere else. Matching an invoice to a supplier only works if Merchaint knows your suppliers.
- A walkthrough video, then three jobs a Pull step does well
- The eight steps, and which trigger to pair it with
- The loop that costs people an afternoon, and how to avoid it
- What happens to records that are already there
01 · Video
Feature walkthrough
02 · Why
Why do we have this?
Most checks depend on data you keep somewhere else. Matching an invoice to a supplier only works if Merchaint knows your suppliers. Pulling keeps that list current without anyone retyping it.
03 · Use cases
A schedule, every hour or overnight.
So they can be matched against invoices.
Use the On ERP Webhook trigger instead of a schedule.
04 · How
Build a Pull
- Create a workflow with an
On a Scheduletrigger. - Set the schedule — a cron time, or an interval in seconds (minimum 30).
- Press
ADD STEPand choosePull from ERPunder Data & Records. - Choose the Connection.
- Choose the Entity Type — Bill, Invoice, Vendor, Customer, and so on.
- Add Filters if you only want some of them.
- Choose Save to Module — where the pulled records should land.
- Wait for
FIELD MAPPINGSto finish analysing, then check what it guessed. See Map fields to your ERP.
05 · Expected result
Records arrive in the module you chose, on the schedule you set. The step summary reads something like entityType: Bill.
06 · Troubleshooting and notes
Pull is a batch fetch, not a reaction
It fetches many records at once. It does not react to one changed row, which is why the trigger you pair it with matters so much.
Which trigger to use
| Trigger | When it suits |
|---|---|
On a Schedule | Keeping a module in sync. The usual choice |
On ERP Webhook | Pulling when the accounting system itself says something changed |
Schedules are UTC
The cron box shows your own timezone underneath and works out what your expression means locally. Read it before saving.
Recurring sync is optional
Under the mappings there is Set up recurring sync template. You do not need it for a workflow — the step’s own mapping is enough. It is for the separate sync configurations in the Integrations area.
07 · FAQ
Common questions
For master data like suppliers, hourly or nightly is plenty. Pulling every 30 seconds mostly wastes effort.
They are updated rather than duplicated, matched on the ERP's own identifier.
Yes, but think about it first. Mixing pulled records with hand-entered ones in one module makes it harder to know where anything came from.
Yes, there is a Filters box on the step.