Feature Request: Native Automation Integrations - Windmill.dev, n8n, Make, Zapier & Python SDK

[githb-ac]

TryPost already has a REST API and an MCP server, so the real opportunity is no longer “add API access” but to turn that existing foundation into a polished, production-ready automation platform. This feature request proposes expanding TryPost’s developer surface with native automation integrations, stronger webhook and event tooling, MCP-first workflow support, and an official Python SDK — making it far easier for agencies, technical teams, and AI-agent workflows to integrate TryPost into real production systems. The current docs already position API and MCP access as part of the platform, so this request is about deepening and operationalising that capability rather than starting from zero.

Summary

A complete automation layer built on top of TryPost’s existing API and MCP server, including native integrations for Windmill, n8n, Make, and Zapier; a production-ready Python SDK; robust webhooks and event subscriptions; and MCP-aware templates for agent-driven publishing workflows. TryPost already documents both API and MCP access, including AI client guidance and shared authentication, which makes this an expansion of the current developer platform rather than a greenfield feature.

Why This Matters

Teams that automate content operations do not just need raw endpoints they need reliable connectors, event delivery, security controls, and tooling that make automation maintainable in production. A mature automation layer would make TryPost significantly more attractive to agencies, developers, and technical growth teams that want to plug publishing, approvals, analytics, and AI-driven drafting into broader operational workflows. Since TryPost already supports API and MCP access, strengthening that layer is a logical product step and a strong differentiator for AI-assisted social publishing

Proposed MVP

Native integrations for Windmill,dev, Zapier, Make, n8n, and with common triggers and actions such as create draft, schedule post, post published, fetch analytics, and new inbox event

Official Python SDK with typed methods, retries, pagination helpers, and examples for reporting pipelines, scheduled publishing jobs, and MCP-aware workflows; Python SDKs are a common pattern for developer platforms that want strong automation adoption

Webhook and event subscription system with signed payloads, retry logic, delivery logs, dead-letter handling, and filtered event topics

MCP-first automation templates for agent workflows such as “generate drafts in chat, save to TryPost as drafts, route to approval, then schedule automatically”

Scoped API keys and short-lived tokens for automation environments so teams can limit access by role and workflow

Event explorer and audit log UI so teams can inspect what automation ran, what failed, and which system or agent triggered each action

Prebuilt recipe library for common use cases such as blog-to-social automation, analytics-to-Slack alerts, and AI-draft-to-approval pipelines

Developer portal improvements including interactive examples, webhook testing tools, Postman collections, and clearer MCP quickstarts