# Scheduling NetoFuse

{% hint style="info" %}
**📘File locations**

These instructions assume files are in the following locations, but you can change this by adjusting the scripts and commands accordingly:

`/etc/netofuse/netofuse.yml` Configuration file

`/usr/local/bin/netofuse-run.sh` Script to be run by cron job

`/usr/local/bin/netofuse-entrypoint.sh` Script to be run inside container *(if applicable)*
{% endhint %}

## Scheduling NetoFuse with Cron <a href="#scheduling-netofuse-with-cron" id="scheduling-netofuse-with-cron"></a>

Schedule NetoFuse to run by creating a cron job on your Linux system. If running multiple modules, you can create a shell script that executes NetoFuse multiple times from a single cron job.

For example, to run integrations daily at 2:00am:

1. Make a script to contain the netofuse commands to execute if you are running more than a single module:

#### `/usr/local/bin/netofuse-cron-run.sh` <a href="#usrlocalbinnetofuse-cron-runsh" id="usrlocalbinnetofuse-cron-runsh"></a>

{% tabs %}
{% tab title="Shell" %}

```
#!/bin/sh
/usr/local/bin/netofuse run claroty
/usr/local/bin/netofuse run axonius
```

{% endtab %}
{% endtabs %}

Set correct permissions for this script to be executable: `chmod 700 /usr/local/bin/netofuse-cron-run.sh`

2. Add the run script to cron

run `crontab -e` and add the following line:

`0 2 * * * /usr/local/bin/netofuse-cron-run.sh`

A handy website for finding the right cron syntax:

<https://cron.help/>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fusion.vectra.ai/netofuse/get-started/run.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.