Integrations
Works with your stack
74 connections to the systems your team lives in, 44 of them able to start workflows from their own events. Anything else can send a webhook or be reached as an HTTP API.
Engineering
Incidents & monitoring
Project management
Messaging
Support
CRM
Payments
Commerce
Forms & scheduling
Infrastructure
Content
Databases
Developer tools
No connection matches that yet.
An HTTP API connection reaches any API with a key, and any system can start a workflow with a webhook.
Built in
No connection needed
Workspaces
A folder of its own for a run, in a Docker sandbox: clone a repository, hand the job to opencode or codex, run your tests, push a branch. No connection to add — though a GitHub one is what it clones and pushes with.
Tools
Webhooks
Any system that can POST JSON — monitoring, forms, CI, internal services. No setup: every workflow can have its own private URL.
Your steps receive
The URL only starts runs while the workflow's trigger is enabled.
Webhook trigger docs →AI models
Built-in Claude, or your own provider
Use Murmurator AI's built-in Claude models with no setup, billed per token — or add a key for any supported provider at no markup.
Or bring your own key:
Webhooks
If it can send JSON, it can start a workflow
Point your monitoring, forms or internal tools at a workflow's URL. The request body arrives as trigger.body, ready for JavaScript to normalize and a model to triage.
From any toolcurl -X POST https://murmurator.app/hooks/w/<token> \ -H "Content-Type: application/json" \ -d '{ "title": "p95 latency > 2s", "service": "checkout" }' # → 202 {"run_id": 128}
Prefer to drive things from your own agents? The MCP server lets Claude, Cursor or any MCP client build and run workflows with the same tools our assistant uses.
Example: Incident triage from any alert
Turn noisy monitoring webhooks into triaged, tracked incidents.
Your next automation is one sentence away.
14-day free trial with $5 of built-in AI included. Cancel anytime.