This project lets you run another tool or process using input thatβs generated on the fly. It evaluates dynamic code, produces structured output, and passes it directly into a target workflow. Itβs a flexible way to handle automation tasks where input values canβt be known ahead of time.
Created by Bitbash, built to showcase our approach to Scraping and Automation!
If you are looking for Dynamic Input you've just found your team β Letβs Chat. ππ
This scraper takes a user-defined script, evaluates it during runtime, and delivers the resulting object to a chosen target. It solves the problem of static workflows by letting developers inject logic that adapts to changing conditions. Itβs designed for people who need a lightweight engine for dynamic execution or conditional task triggering.
- Generates input values based on custom logic instead of fixed files.
- Supports fast evaluation of small scripts with predictable execution.
- Works as a middle layer to route dynamic results into other processes.
- Ideal for automated pipelines needing runtime variability.
| Feature | Description |
|---|---|
| Runtime evaluation | Executes user-provided code and returns structured results. |
| Targeted execution | Automatically forwards evaluated output to a specified process. |
| Flexible scripting | Allows simple or complex logic to produce dynamic inputs. |
| Safe isolation | Evaluates logic in a controlled environment. |
| Consistent formatting | Ensures resulting data follows predictable object structure. |
| Field Name | Field Description |
|---|---|
| input | A script returning an object with dynamic values. |
| targetId | Identifier of the target process that receives evaluated output. |
| evaluatedPayload | Object generated after executing the input script. |
Dynamic Input/
βββ src/
β βββ index.js
β βββ evaluator/
β β βββ scriptRunner.js
β β βββ sandbox.js
β βββ dispatcher/
β β βββ forwarder.js
β βββ config/
β βββ defaults.json
βββ examples/
β βββ sample-input.json
βββ tests/
β βββ evaluator.test.js
β βββ dispatcher.test.js
βββ package.json
βββ LICENSE
βββ README.md
- Developers generate dynamic parameters for automated tasks, so workflows adjust to real-time conditions.
- Operations teams trigger downstream tools using logic-based calculations, so repetitive setups disappear.
- QA engineers simulate variable environments, so test suites behave closer to real-world scenarios.
- Data engineers compute ranges or thresholds before sending data to processing tools, improving consistency.
- Workflow architects build adaptive pipelines where executable logic decides what happens next.
Can I use complex logic in the input script? Yes, as long as the script returns a final object. Keep the logic concise to maintain predictable performance.
Does the target process need special configuration? No. It simply receives the evaluated object exactly as returned by the script.
Is the evaluated script isolated? Execution runs in a controlled environment designed to limit unsafe behavior.
Can it generate different output each run? Absolutely. Because it evaluates logic at runtime, results can vary based on randomization, conditions, or external calculations.
Primary Metric: Script evaluation typically completes in under 20 ms for lightweight logic, allowing rapid task chaining.
Reliability Metric: Over thousands of sequential runs, the engine maintains a consistent execution success rate above 99%.
Efficiency Metric: Designed to run with minimal memory overhead, it supports high-frequency dynamic evaluations without bottlenecks.
Quality Metric: Generated objects remain structurally consistent across executions, ensuring reliable consumption by downstream processes.
