Integrating MacWhisper with other services

From version 13.6 onwards you can connect MacWhisper to a variety of automation and note-taking services. This lets you automatically forward finished transcripts to tools like Zapier, Make.com, n8n, your own custom webhook, or a local Obsidian vault.


Most integrations use webhooks: MacWhisper sends a small HTTP request to the URL you configure, containing the transcript title and text. From there, you can build your own automations (send to Notion, email, Slack, CRMs, etc.).


If you want to connect MacWhisper to your local Obsidian vault, you need to use the Local REST API plugin in Obsidian. MacWhisper will talk directly to that local API and create or update a markdown file for each transcript.

1. Requirements & where to find the settings

Integrations require an active MacWhisper Pro license

Integrations are a Pro feature. If MacWhisper does not detect a valid Pro license, the Integrations screen will show a message prompting you to upgrade and the settings will be disabled.


Once you have Pro:

  1. Open MacWhisper.
  2. Go to Settings → Integrations.
  3. You’ll see sections for Zapier, Make.com, n8n, Custom Webhook, and Obsidian.

All credentials (webhook URLs, API keys, Obsidian token) are stored securely in your macOS Keychain.

2. Automatic sending after a transcription finishes


At the top of the Integrations settings page you’ll see a toggle for:

“Automatically send after finished transcription”

  • When this toggle is enabled, MacWhisper will:
    • Detect when a transcription is finished.

    • Send the transcript to all integrations that are properly configured (have a valid URL/API key, etc.).


If you’d rather decide later what to do with a transcript, leave this toggle off and only enable it when you want things to run automatically.


What gets sent (for webhook-based integrations):

{
  "title": "The transcript title",
  "transcript": "Full transcript text here..."
}

Obsidian is slightly different (see below).

3. Zapier integration


Use Zapier to connect MacWhisper to thousands of apps (Notion, Google Sheets, Slack, email, etc.).


In the Zapier section you’ll see:

  • A Webhook URL field (placeholder looks like https://hooks.zapier.com/hooks/catch/abcdefgh)
  • A Test button that appears once a valid URL is filled in.
  • A small status label (Success / error) after testing.

MacWhisper sends a POST request to your Zapier webhook with JSON:

{
  "title": "Title of the transcript",
  "transcript": "Full transcript text"
}

How to set it up in Zapier

  1. In Zapier, create a new Zap.
  2. Choose “Webhooks by Zapier” → “Catch Hook” as the trigger.
  3. Zapier will give you a Webhook URL.
  4. Copy that URL.
  5. In MacWhisper, open Preferences → Integrations → Zapier.

  6. Paste the URL into Webhook URL.

    Once the URL is valid, click Test in MacWhisper:

    • If the connection works, you’ll see “Success” next to the button.
    • If there’s a problem, MacWhisper will show the error message returned by Zapier (e.g. “Not found”).

After that, when Automatic sending is enabled and a transcription finishes, Zapier will receive the transcript and your Zap can continue the workflow. In Zapier the title and transcript values will appear and you can setup how you want them to be used.


4. Make.com integration


Make.com lets you build more advanced scenarios and flows using your transcripts.


In the Make.com section, you’ll see:


  • Webhook URL (placeholder: https://hook.eu1.make.com/abcdefgh)
  • API Key (placeholder: ABCDEFGHIJKLM)
  • A Test button, once both fields are filled in.

MacWhisper sends a POST request with:


  • JSON body:
{
  "title": "Transcript title",
  "transcript": "Full transcript text"
}
  • Header:
x-make-apikey: YOUR_API_KEY

How to set it up in Make

  1. In Make.com, create a new Scenario.
  2. Add a module that accepts a webhook / HTTP request (e.g. “Webhook” or “HTTP: Watch Incoming Request”).
  3. Copy the Webhook URL generated by Make.
  4. Generate or copy your Make API Key (from your Make account settings).
  5. In MacWhisper, open Preferences → Integrations → Make.com.

  6. Paste the Webhook URL and API Key into the fields.

    Click Test:

    • On success, MacWhisper shows “Success”.
    • On failure, you’ll see the error Make returned.

Once configured and automation is enabled, every finished transcript will be sent into your Make scenario.

5. n8n integration


Use n8n to run self-hosted or cloud workflows with your transcripts as input.


In the n8n section you’ll see:

  • Webhook URL (placeholder: https://username.app.n8n.cloud/webhook/abcdefg)
  • A Test button when a valid URL is present.
  • A small status label showing the test result.

MacWhisper sends a POST request to this URL with JSON:

{
  "title": "Transcript title",
  "transcript": "Full transcript text"
}

How to set it up in n8n

  1. In n8n, create a new Workflow.
  2. Add a Webhook trigger node.
  3. Copy the Webhook URL from that node.
  4. In MacWhisper, open Preferences → Integrations → n8n.

  5. Paste the URL into Webhook URL.

    Click Test in MacWhisper to send a sample payload:

    • n8n should receive the test request.

    • MacWhisper will show Success or the error coming back from n8n.


With automation enabled, every finished transcript will be posted to that webhook and can trigger your n8n workflow.

6. Custom Webhook integration


If you have your own API or any service that accepts an HTTP POST, use the Custom Webhook integration.


In the Custom Webhook section you’ll see:

  • Webhook URL (placeholder: https://www.customwebhook.com/abcdefgh)
  • A Test button when a valid URL is present.


MacWhisper sends:

  • Method: POST
  • Content-Type: application/json
  • Body:
{
  "title": "Transcript title",
  "transcript": "Full transcript text"
}

How to use it

  1. Set up your own service / endpoint that accepts JSON.
  2. In MacWhisper, open Preferences → Integrations → Custom Webhook.
  3. Paste your endpoint URL into Webhook URL.
  4. Use Test to verify your server is reachable and responds correctly.
  5. Enable Automatic sending if you want every finished transcript to be posted there.

This is ideal if you want full control (your own database, a custom app backend, etc.).

7. Obsidian integration (local vault via REST API)


If you use Obsidian for note-taking, MacWhisper can send transcripts directly into your local vault.

🔧 Requirement: You must install and enable a plugin that exposes a local REST API in Obsidian (for example the “Local REST API” community plugin). Configure an API token there first and install the required certificate if you want to. use an https connection.

In the Obsidian section you’ll see three fields:


  • IP Address

    Default: 127.0.0.1 (local machine)

    Note: The placeholder currently shows https://127.0.0.1, but the integration will combine this with the port, e.g. 127.0.0.1:27124.

  • Port

    Default: 27124 (typical default for Obsidian REST plugins)

  • API Token

    The token you configured in the Obsidian REST plugin.


When these are filled in, MacWhisper builds a URL like:

http://127.0.0.1:27124/vault/<Title>.md

and sends:


  • Method: PUT
  • Headers:
    • Authorization: Bearer YOUR_OBSIDIAN_TOKEN
    • Content-Type: text/markdown
  • Body:

    • transcript (raw markdown text of the transcript)


So each transcript becomes a .md file in your vault, using the transcription title as the file name.


How to set it up

  1. In Obsidian:
    • Install and enable the Local REST API (or similar) plugin.
    • Set its port (e.g. 27124).
    • Generate and copy the API token.

    • Make sure the plugin is allowed to create/update files in the desired vault.


      In MacWhisper, open Preferences → Integrations → Obsidian:


    • IP Address: usually https://127.0.0.1.
    • Port: the same port you configured in Obsidian (e.g. 27124).

    • API Token: paste the token from Obsidian.

      Once all fields are filled, MacWhisper will show a Test button:

    • Click Test to have MacWhisper send a small test markdown file.

    • If everything is configured correctly, you’ll see Success, and a new file should appear in your Obsidian vault.


With Automatic sending enabled, MacWhisper will create/update a markdown file in your vault for each finished transcript.

Testing integrations & reading errors

Every integration section (Zapier, Make.com, n8n, Custom Webhook, Obsidian) has a Test button once the required fields are filled in:


  • MacWhisper sends a small test request with dummy data.

    The result appears as a small label next to the button, e.g.:

    • ✅ Success

    • ⚠️ An error message returned by the service (“Not found”, validation error, etc.).


You can click on the status label to clear it and run another test.


If you see repeated failures:


  • Double-check the URL, API key, port and token.

    For Obsidian, make sure:

    • The plugin is running.
    • The vault is open.

    • Obsidian is listening on the same IP/port you configured in MacWhisper.


Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.