Photo: free stock photography (Unsplash licence) — see imprint
Give them a verb
A custom flow action — 'push order to ERP', 'notify the account manager', 'reserve stock' — appears in the Flow Builder like any core action. Once it exists, anyone can attach it to any trigger without a developer in the loop.
Give them a condition
Custom rule conditions do the same for the Rule Builder: 'customer has an open credit limit', 'product is on contract'. Now pricing, shipping and flow rules can all reason about facts that only exist in your business.
Keep the action dumb
The action should validate its input and hand off to a queue, not perform a five-second ERP round trip inside the flow. A flow that blocks is a checkout that blocks.
Name things for the person clicking
'ErpOrderSyncActionV2' means nothing to your operations manager. Name it 'Send order to ERP', describe what it does in one sentence, and the automation will actually get used.
- A custom action turns a developer task into a click.
- Actions validate and queue; they never block.
- Name them for the person in the admin, not the repo.
We do this for a living — Shopware, Node.js, React, ERP integration and automation for B2B.
Talk to an engineer