Company
Connecting Mutterbox to what you already use
Three standard exits — webhook, API and CSV export — connect Mutterbox to every tool you already use. More ready-made integrations are in preparation.
Three ways data leaves
A webhook fires the moment something happens — analysis finished, report ready, monitoring alert. A read-only API lets you pull data when you need it. CSV export gives you the full corpus for a spreadsheet or a warehouse. Each of these works with any tool that can receive HTTP or open a file.
Signed webhooks
Every delivery carries a signature letting you verify it came from us and was not altered on the way. Without it the receiver would have to trust anyone who knows the address.
Zapier, Make, n8n
All three accept a webhook and call an API with a token. You do not need a plugin from us — you need an address and a token, and both are in the panel.
A widget for your site
One line of code shows the rating and review count from connected platforms. No cookies and no tracking, so no changes to your privacy policy.
Step by step
Three ways to get data where you need it
-
1
Webhook — immediate reaction
The event fires the moment an analysis is ready. Wire it into Zapier, Make, n8n or your own address and react automatically.
-
2
API — pull on demand
A read-only token gives access to locations, analyses, problem cards and quotes as JSON. Enough to build your own dashboard or to feed a warehouse.
-
3
CSV — data for a spreadsheet
The full corpus from every analysis: reviews with date, platform, rating, categories and sentiment. Ready to paste or import.
-
4
Widget — numbers on your site
One line of code shows the rating and review count from connected platforms, with no cookies and no tracking.
In practice
The most common integration among our customers
A webhook wired into Make that, once an analysis is ready, pulls the highest-weight problem card and opens a ticket in the issue tracker — with the deadline from the horizon field and the quotes in the description. Three steps in a builder, no code, an hour to set up the first time.
1 hour
is the typical time to connect it to your own system. More ready-made integrations are in preparation and appear here as they launch.
Why it works this way
Integration that keeps working
Webhooks, an API and CSV export are standards every tool understands — from Zapier and Make to your own script and your data warehouse. You can wire them into a booking system, a CRM or a spreadsheet in an hour of developer time, and they keep working when the other side ships a new version. More ready-made integrations are in preparation and appear here as they launch.
Common questions
Is there an integration with my booking system?
Not a direct one. There is a webhook and a read-only API, which you connect through Zapier, Make or your own script — in practice about an hour of a developer's time.
Can analyses be started from outside?
Starting an analysis stays in the panel, where its credit price is visible. That means you can safely drop the API token into a low-code tool or someone else's script — it will pull data and generate no cost.
What format does the API return?
JSON, with the same fields you see in the panel: locations, analyses, problem cards with quotes and metrics. Documentation sits in the panel, next to token generation.
Be first in when we launch
Join the waitlist. We'll write once, on launch day, with a link to create your account.