Slack-to-Site Publishing Pipeline in Under 30 Seconds

Context

Publishing a short technical note involved several small but repetitive steps: format the content, create the Markdown file, add metadata, commit it, wait for deployment, and confirm that the page was live.

I built a workflow that turned those steps into one controlled publishing path initiated from Slack.

My role

I designed, implemented, and operated the complete flow: command format, n8n orchestration, content validation, GitHub integration, deployment trigger, and completion notification.

How it worked

1. A structured Slack command supplied the title, body, and content metadata.
2. n8n validated and transformed the input into the site’s Markdown format.
3. The workflow created the file and committed it through the GitHub API.
4. Netlify built and deployed the updated site.
5. The workflow returned the live URL and deployment status.

For a normal short entry, the path from Slack submission to a live page completed in under 30 seconds, including the site build.

Why it mattered

The useful result was not simply faster publishing. It was a repeatable interface between an idea and a production system. The workflow made file structure, metadata, version control, deployment, and notification explicit and inspectable.

This became an early building block for later autonomous content operations, where agents could prepare work but publishing still passed through defined tools and observable state transitions.

Stack

• Slack commands
• n8n
• GitHub API
• Markdown and Astro content collections
• Netlify deployment

Status: Operated as a production workflow and later absorbed into the broader publishing infrastructure behind The Unnamed Roads.