Discover
Three flows in detail
An online order, all the way to the ERP
Step 1/4
Webhook
An online shop sends a Webhook : A message one application sends to another on its own as soon as something happens, here a new order. NoxFlow receives it and runs the planned job right away. to NoxFlow for every new order.
- Webhook : An online shop sends a webhook to NoxFlow for every new order.
- Trigger : NoxFlow triggers the associated job. The execution engine fetches it, with its parameters and connections.
- Customer sync : The job finds the customer in the CRM and syncs it to the ERP, along with the order.
- Supervision : Your team follows every processed order on NoxFlow, in near real time.
An order file dropped, all the way to the ERP
- Drop : An order file is dropped into the watched folder, by a partner or an export. The job associated with it is triggered.
- Preparation : The execution engine fetches the job to run, with its parameters and connections.
- Run : The Python job reads the orders from the file and records them in the ERP. Data moves from one application to another without leaving your network.
- Supervision : Only the status, logs and metrics go up to NoxFlow. Your team follows the run in near real time.
- Alert : The day the write fails, an alert is sent to your team.
The data warehouse, loaded every night
- Schedule : Every night at 2 a.m., NoxFlow starts the chain. The execution engine fetches the parameters and connections it needs.
- Customers : The first job reads the customers from the CRM. The connection token expires mid-run: the execution engine refreshes it itself.
- Orders : The second reads the ERP orders from where it stopped the night before: it keeps its cursor from one run to the next.
- Load : Once both reads are done, the data warehouse is loaded. Your BI dashboards benefit from fresh data that never left your network.
- Supervision : In the morning, the team finds the night's summary on NoxFlow. The observatory shows which connections were used and the load of the next 24 hours.
Your applications, your rules.
Your information system has its own applications and business rules. With NoxFlow, even those that were never meant to talk to each other exchange data, on your terms.
Design, orchestrate and supervise
From Python to a supervised flow
It all starts on your machine.
Your jobs are written in Python. The code is entirely yours: you keep your version control and the AI assistant of your choice.
A job designed with your AI assistant.
You, or your usual AI assistant, write the Python code. The nox command creates the job, and the logic goes into main.py. A library dedicated to your ERP : Enterprise resource planning software: orders, stock, purchasing and accounting are managed in one tool. is created, reusable by your next jobs.
Tested locally, published as a frozen version.
You run the job on your machine to test it. Once validated, you publish it to NoxFlow.
One job, as many configurations as needed.
Each configuration reuses the job with its own parameters and connections. Teams who do not code can run it by filling in the fields, step by step.
On demand, on top of the schedule.
The job's page shows its latest runs. You can start it whenever you want, on top of its schedule.
Your team can see what is happening.
Runs, failures and their causes: everyone follows them in one place and can act before business teams notice an anomaly or missing data.