50+ connections, most of them with triggers

Murmurator now connects to more than fifty services, up from ten. Browse them all on the integrations page.

What's new

Payments and commerce: Stripe, Paddle, Lemon Squeezy, Chargebee, Square, Shopify and WooCommerce. Support and CRM: Zendesk, Intercom, Front, Freshdesk, HubSpot, Pipedrive and Attio. Engineering: GitLab, Bitbucket, Jira, CircleCI, Buildkite and Vercel. Incidents and infrastructure: Sentry, PagerDuty, incident.io, Datadog, Statuspage, Heroku, Render and Cloudflare. Plus Asana, ClickUp, Trello, Todoist, Notion, Airtable, Webflow, Mux, Typeform, Tally, Calendly, Cal.com, Twilio, Discord, Telegram, Customer.io, PostHog, Clerk and Ashby.

Every one works the same way

• Paste the key the form asks for. Each form says where to find it.
• Named tools for the common jobs, such as stripe.create_refund, zendesk.update_ticket or pagerduty.update_incident, with responses trimmed to what a workflow needs.
• api_get for any other endpoint of the provider's API, with the same key. Tick Allow raw writes for api_request.

Triggers

37 of them can start workflows from their own webhooks: a failed Stripe payment, a new Shopify order, a Zendesk ticket, a GitLab merge request, a PagerDuty incident, a Typeform response. Every delivery's signature is checked against the provider's own scheme, and stale deliveries are refused wherever the provider timestamps them. Each provider brings its own filters, such as projects for GitLab or forms for Typeform.

trigger:
  kind: stripe
  connection: stripe
  events: [invoice.payment_failed]
  livemode: [true]

See it end to end in the failed payment follow-up example, and the details in catalog connections and catalog triggers.