Workflow overview
Why this workflow matters
Helpful for business development and pipeline building. Relevant for managed services and support workflows.
How it works Send a POST request with a JSON array of records and your validation rules. The workflow checks every field in every row and returns a structured report showing valid/invalid rows with specific error messages. Supported rules: required, type (string, number, email, date, url, boolean), min/max, minLength/maxLength, regex, enum, and dateFormat (YYYY-MM-DD, DD.MM.YYYY, MM/DD/YYYY). The response includes a summary (total, valid, and invalid row counts) plus a detailed error list with row number, field name, failed rule, and error message. Set up steps Import the workflow and activate it Send a POST request to the webhook URL with "data" (array of objects) and "rules" (validation config) Optionally edit the Set Default Rules node to define fallback rules — these are used when no rules are sent in the request No external services or API keys required. Works on self-hosted and cloud AlekSystem instances. Who is this for Operations teams, data engineers, and anyone importing data into ERP systems, CRMs, or databases who needs to catch errors before bad data enters the system. How to customize Edit the Set Default Rules node for your standard field definitions. Rules sent in the request body override the defaults, so one endpoint works for multiple data structures. Extend the Code node for custom checks like cross-field validation.
Best fit
Categories
Services
Use cases
Need another direction?