No-code EDI automations: send every new order where it needs to go
A purchase order arrives at 2 a.m. By the time your team starts, it is already in the warehouse inbox as a spreadsheet and in your order system through a webhook. No code, a few minutes of setup.
Receiving an EDI document is only half the job. Somebody has to see it: the warehouse needs the order, accounting needs the invoice, your own software needs the data. Automations do that routing for you, document by document, without anyone forwarding emails.
An automation is a rule: when a document matching these conditions comes in or goes out, do this. Here is how one is built in Weredi.
Choose the direction
Documents that come in from your partners, or documents that go out to them. An incoming purchase order and an outgoing invoice usually need different people.
Narrow it down
Limit the rule to certain documents, such as only 850 purchase orders, and to certain partners. Leave either one empty and it applies to all of them.
850860810820Pick the action
Send an email to one or more people, with the document attached or in the message body, as the original EDI, a readable page, JSON, XML or an Excel spreadsheet. Or trigger a webhook: Weredi posts the document to your URL as JSON, XML or form fields.
Preview it, then switch it on
Check the output on a sample document before the rule goes live. Pause and resume it any time.
What teams usually automate
| When… | Then… |
|---|---|
| A purchase order comes in | Email it to the warehouse as a spreadsheet |
| A purchase order change (860) comes in | Email customer service so the order is updated |
| A remittance (820) comes in | Email accounting with the payment details |
| Any document comes in | Post it to your own system by webhook |
Forwarding by hand vs. an automation
By hand
- Someone checks the inbox and forwards each order
- Orders wait for business hours
- Each person reformats the data their own way
With an automation
- Each document is routed the moment it arrives
- Always the same format, for the same people
- Every run is recorded with the document
Shape the output with a mapping
Attach a mapping to an email or webhook action and the document is reshaped first: only the fields your team needs, with codes translated by lookup tables. Developers can go further with the REST API.
Questions
What is a no-code EDI automation?
A rule that acts on EDI documents without programming: when a document of a given type comes in or goes out for a given partner, it is emailed to someone or posted to a URL.
Can I receive EDI orders in Excel?
Yes. An automation can email each incoming purchase order with an Excel (.xlsx) attachment, or as JSON, XML, a readable page or the original EDI.
Do automations need a developer?
No. Emails and webhooks are set up in a form. A developer is only needed to build the system that receives a webhook, if you use one.
Which plan includes automations?
Automations are part of Weredi Plus and Enterprise, and run during the 14-day free trial.
Related articles
All articles →Set up your first automation
Automations are part of Weredi Plus and are on during the 14-day free trial.