SOLVED
Automation unlocked
Notify your tools, trigger your pipelines, or orchestrate a fleet of agents. From the moment content is published.
Get started
No dashboard required.
Your AI handles publishing through a structured API. Your team stays in the tools they already use.
Full control, zero risk.
Role-based access means your AI can only do what you allow. Draft content never leaks.
Live in minutes.
Connect once. From that point, a conversation is all it takes to publish.
Until now, content state changes in Forge were silent. A post published, a story archived, and nothing outside Forge could react. That changes today.
Level 1 — Notify your tools
Webhooks fire on publish, update, or archive. Connect to Zapier, Make, or n8n. No code required. A post goes live, a Slack message fires, an Airtable row is created, an email campaign starts. Forge sends the event; your integration platform handles the rest.
Level 2 — Trigger your pipelines
Same webhook, your own endpoint. Your backend receives the event and does whatever your workflow requires: invalidate a cache, kick off a build, notify a client.
The outbound webhooks reference covers payload format, signature verification, and retry behaviour. forge-cli lets you manage endpoints and inspect delivery logs from the terminal.
Level 3 — Orchestrate your agents
MCP clients can subscribe to content resources. When a post changes, connected agents are notified via MCP protocol. No polling, no missed events. Forge becomes the shared state for an agent fleet.
One infrastructure. Three use cases. Forge doesn't know which level you need today, but it's ready for all three.
Ready to put your AI to work?
Forge is open source and self-hosted. Get started in minutes.