fix(docs): Update automation.mdx (#69)

Author: Ryan-Amirthan

fern/products/api-definition/api-definition.yml

@@ -60,7 +60,7 @@ navigation:
       - page: Overlay Customizations
         icon: fa-regular fa-shuffle
         path: ./pages/openapi/overrides.mdx
-      - page: Automatic Updates
+      - page: Sync your OpenAPI Specification
         icon: fa-regular fa-arrows-rotate
         path: ./pages/openapi/automation.mdx            
       - section: Integrate your Server Framework
@@ -150,4 +150,4 @@ navigation:
       - page: Export to OpenAPI
         icon: fa-regular fa-file-export
         slug: export-openapi
-        path: ./pages/fern-definition/export-openapi.mdx
+        path: ./pages/fern-definition/export-openapi.mdx

fern/products/api-definition/pages/openapi/automation.mdx

@@ -1,12 +1,54 @@
 ---
-title: Automatically Update
+title: Sync your OpenAPI Specification
 subtitle: Pull your latest OpenAPI Specification into your Fern Folder automatically.
 ---
 
-If you host your OpenAPI Specification at a publically available URL, you can have Fern programmatically fetch the latest spec on a preconfigured cadence. By default, this will be done every day and open a new PR on the GitHub repo that contains your Fern Folder. This feature requires installation of the [Fern GitHub App](https://github.com/apps/fern-api).
-
-```yml title="generators.yml"
-api:
-  path: openapi/openapi.json
-  origin: https://example.com/openapi.json
+If you host your OpenAPI Specification at a publicly available URL, you can have Fern programmatically fetch the latest spec on a preconfigured cadence through the [sync-openapi GitHub Action](https://github.com/fern-api/sync-openapi). This ensures your committed OpenAPI spec stays up to date with your live API.
+## Setup
+<Steps>
+  <Step title="Configure the origin URL">
+   Add the origin field to your generators.yml to specify where your OpenAPI spec is hosted:
+   ```yml title="generators.yml"
+    api:
+      path: openapi/openapi.json
+      origin: https://api.example.com/openapi.json
+    ```
+  </Step>
+  <Step title="Add the GitHub Action">
+    Create `.github/workflows/sync-openapi.yml` in your repository:
+    ```yml
+    name: Sync OpenAPI Specs # can be customized
+    on:                               # additional custom triggers can be configured
+      workflow_dispatch:              # manual dispatch
+      push:                                          
+        branches:
+          - main                      # on push to main
+      schedule:
+        - cron: '0 3 * * *'           # everyday at 3:00 AM UTC
+  jobs:
+    update-from-source:
+      runs-on: ubuntu-latest
+      steps:
+        - uses: actions/checkout@v4
+          with:
+            token: ${{ secrets.OPENAPI_SYNC_TOKEN }}
+        - name: Update API with Fern
+          uses: fern-api/sync-openapi@v2
+          with:
+            update_from_source: true
+            token: ${{ secrets.OPENAPI_SYNC_TOKEN }}
+            branch: 'update-api'
+            auto_merge: false
+            add_timestamp: true
 ```
+  </Step>
+  <Step title="Add a GitHub token">
+    Generate a [fine-grained personal access token](https://github.com/settings/personal-access-tokens) with read/write access to your repository.
+  </Step>
+  <Step title="Add to Repository Secrets">
+    Navigate to your repository's `Settings > Secrets and variables > Actions`. Select **New repository secret**, name it `OPENAPI_SYNC_TOKEN`, add your token, and click **Add secret**.
+  </Step>
+</Steps>
+By default, this will create daily PRs with API spec updates to the repo containing your Fern folder. If you would like to adjust the frequency, learn more about GitHub's [schedule event](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule).
+
+<Info> For detailed configuration options and other use cases, see the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi). </Info>