148 trigger windmill

[nicopace]

Closes #148

Written with assistance of Google Gemini, reviewed by me.

[rudokemper]

Suggested change

	## Real-Time Syncing with KoboToolbox Webhooks
	## Webhooks
	### Real-Time Syncing with KoboToolbox Webhooks

[rudokemper]

Link to KoboToolbox REST Services documentation

[rudokemper]

Suggested change

	When using KoboToolbox to collect data in the field, you don't need to manually run a script every time you want to pull down the newest form submissions. Instead, you can use **Webhooks** (*REST Services* in KoboToolbox) to automate the process.
	When using KoboToolbox to collect data in the field, you don't need to manually run a script, or rely on a schedule, every time you want to pull down the newest form submissions. Instead, you can use **Webhooks** (*REST Services* in KoboToolbox) to automate the process.

[rudokemper]

Suggested change

	As soon as a surveyor submits a new record, KoboToolbox sends an automatic, instant message to your script. This immediately triggers your flow to run and process the new data. This ensures your datasets in Guardian Connector are updated in real-time, without any manual intervention.
	As soon as a surveyor submits a new record, KoboToolbox automatically triggers your Windmill script to run and process the new data. This ensures your datasets in Guardian Connector are updated in real-time, without any manual intervention.

[rudokemper]

Suggested change

	*To set this up, you simply generate a unique Webhook URL for your script in the Hub, and paste it into the "REST Services" settings of your KoboToolbox project.*
	*To set this up, you simply generate a unique Webhook URL for your script in the Windmill, and paste it into the "REST Services" settings of your KoboToolbox project.*

This is missing documentation. It is not just the URL. Also the token and Body must be pasted into the REST Services.

Please have Gemini read the documentation I wrote, or manually improve it yourself to guarantee accuracy.

[rudokemper]

Add a section ## Scheduling, as this is the most common way that we trigger scripts.

[rudokemper]

And it should absolutely go before ## Webhooks

[rudokemper]

Suggested change

	## Other Ways to Automate Scripts
	Beyond KoboToolbox, you can automate your workflows in a variety of ways depending on your organization's needs. Here are the primary methods available for running or triggering scripts:
	* **[Schedule](https://www.windmill.dev/docs/core_concepts/scheduling):** Run a script automatically at a specific time or recurring interval.
	* Example: Pulling data from a government agency every night at midnight.
	* **[Webhooks](https://www.windmill.dev/docs/core_concepts/webhooks):** Trigger a script instantly when an external service sends an update.
	* Example: updating dashboards when new submissions have been done on KoboToolbox.
	## Other Ways to Trigger Scripts

And add * **Manual Runs**:

[rudokemper]

In addition to my review comments, please also update your PR title to be more descriptive.

When squashing and merging in this (and any of our GC) repos, the PR message will become the commit message. So the PR title matters for understanding logs and diffing.