> For the complete documentation index, see [llms.txt](https://blog.rhinoautomator.com/brians-integration-and-automation-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.rhinoautomator.com/brians-integration-and-automation-notes/automations/automated-github-gitbook-update-notifications/1.-set-up-a-basic-workflow.md).

# 1. Set up a Basic Workflow

{% hint style="danger" %}
I've migrated the entire blog over to my new website. Please go to [https://rhinoautomator.com](https://rhinoautomator.com/) for more as this will be deleted at some point.
{% endhint %}

Before getting to work on the GitHub side, one of the bits you'll need from your automation platform is a webhook to enter into the notification settings.

{% stepper %}
{% step %}

#### In Rewst, create a new workflow

{% hint style="info" %}
Remember to follow best practices when naming your workflow. Just as Rewst has undergone a lot of standardization of naming, your organization should be doing the same.
{% endhint %}
{% endstep %}

{% step %}

#### For now, just create a single noop action

Did you pronounce this noop or noop? Debate about it in the ROC Open Mic chat.

{% hint style="warning" %}
Don't forget to hit publish to save otherwise you'll see a failure in your workflow history once the webhook notifications are set up in GitHub
{% endhint %}
{% endstep %}

{% step %}

#### Add a webhook trigger

This trigger only needs to live at the parent organization level, so there is no need to toggle on the managed organizations or select any from the dropdown.
{% endstep %}

{% step %}

#### Copy the webhook or leave tab open for reference

{% endstep %}
{% endstepper %}