Guide: Setting up a content calendar approval flow with ContentBot drafts.

Another day, another "guide" for orchestrating a simple process through a dozen microservices and a SaaS chatbot. Content calendars existed before ContentBot. They were called spreadsheets and email.

So you want to gatekeep drafts with an "approval flow"? Fine. Here's the reliable, boring way. Set up a Git repo for your drafts. Use a branch per piece of content, open a PR for review. When the PR is merged, a webhook pings your CMS to publish. No vendor lock-in, no magic.

```yaml
# github-actions/workflow.yaml
name: Draft Approval
on:
pull_request:
branches: [ main ]
types: [closed]

jobs:
publish-if-merged:
if: github.event.pull_request.merged == true
runs-on: ubuntu-latest
steps:
- name: Trigger CMS Publish
run: |
curl -X POST ${{ secrets.CMS_WEBHOOK_URL }}
-H "Content-Type: application/json"
-d '{"commit_ref": "${{ github.sha }}"}'
```

Now you have a full audit trail, can roll back with git revert, and your entire team already knows how it works. Why pay for a bot to add another layer of abstraction to a solved problem?