How to Connect Miru to 5,000+ Apps with Zapier

Miru doesn’t have a native Zapier integration. It has something better: an API that works with Zapier’s webhook triggers and actions. This means you’re not limited to whatever pre-built “Zap templates” a product team decided to ship. You can connect Miru to any of Zapier’s 5,000+ apps and build exactly the workflow you need.

Here are three workflows we actually use. Not hypothetical. Not “you could do this.” We do this. Every week.

---

1. Google Calendar to Miru: Auto-Log Meeting Time

Every meeting is billable time that’s easy to forget. This Zap watches your Google Calendar for completed events with a specific label (we use “billable”) and creates a time entry in Miru automatically.

Trigger: Google Calendar — Event Ended Filter: Event title or description contains “billable” Action: Webhooks by Zapier — POST to https://app.miru.so/api/v1/time_entries

The POST body:

{
  "project_id": 42,
  "duration": "{{event_duration_minutes}}",
  "note": "Meeting: {{event_title}}",
  "work_date": "{{event_date}}"
}

Set the Authorization header to Bearer YOUR_TOKEN. That’s the whole configuration. Every billable meeting now logs itself. You stop losing 3-5 hours a week of meeting time that never made it onto an invoice.

---

2. Miru Invoice to Slack: Notify the Team When Invoices Send

When you send an invoice to a client, your team should know. Not because they need to approve it — because transparency about cash flow makes everyone smarter about the business.

This one uses Zapier’s Schedule trigger to poll Miru’s invoice endpoint every hour and checks for newly sent invoices.

Trigger: Schedule by Zapier — Every Hour Action 1: Webhooks by Zapier — GET https://app.miru.so/api/v1/invoices?status=sent Action 2: Slack — Send Channel Message

The Slack message:

Invoice #{invoice_number} sent to {client_name} for ${amount}.

Simple. No dashboard to check. No “did that invoice go out?” emails. The information finds the people who need it.

---

3. Stripe Payment to Miru + QuickBooks: Close the Loop

When a client pays an invoice through Stripe, two things need to happen: Miru marks the invoice as paid (this happens automatically), and your accounting tool needs to record the payment.

Trigger: Stripe — Payment Successful Action 1: Webhooks by Zapier — GET the corresponding Miru invoice Action 2: QuickBooks — Create Payment Receipt

Now your accountant sees the payment in QuickBooks the moment it clears. No manual data entry. No month-end reconciliation scramble. The payment flows from Stripe to Miru to QuickBooks without anyone touching it.

---

Setting Up Zapier Webhooks with Miru

Every Zap that talks to Miru follows the same pattern:

1. Generate an API token in Miru (Settings > Profile > API Token)
2. Use “Webhooks by Zapier” as the action or trigger
3. Set the URL to https://app.miru.so/api/v1/{resource}
4. Add the Authorization: Bearer YOUR_TOKEN header
5. Set Content-Type: application/json for POST/PUT requests

The Miru API supports all the standard operations — list, create, update, delete — on time entries, invoices, clients, projects, and expenses. Anything you can do in the web app, you can do through a Zap.

---

Why This Beats a Native Integration

Native integrations are limited to what the developer imagined. A Zapier webhook integration is limited to what you can imagine. Want to create a time entry from a Todoist task? Do it. Want to send an invoice summary to Notion? Do it. Want to trigger an invoice when a GitHub milestone closes? Go for it.

The API is the integration. Zapier is just the glue.

Get your API token at app.miru.so and connect Miru to everything.