Webhooks are a powerful way to send real-time data from one application to another. By connecting a webhook to Quick Audio Note, you can instantly send your new notes, summaries, and transcripts to your own custom applications and services. This guide will show you exactly how to create a webhook endpoint and connect it to your account.

What is a Webhook?

Think of a webhook as an automated notification. Instead of your application constantly asking our server "Is there a new note yet?", our server will automatically send a message to your application the moment a new note is created. This message is sent to a specific URL you provide—your "webhook endpoint."

Step 1: Create a Webhook Endpoint on Your Server

Your endpoint is a URL on your server that is programmed to listen for incoming data. When Quick Audio Note sends a notification, it will be in the form of an HTTP POST request containing a JSON body. Your server needs to be ready to accept and process this.

Below is a basic example of how to create an endpoint using Node.js and the popular Express framework. The same principles apply to any language like Python (with Flask/Django), PHP (with Laravel), Ruby (with Rails), etc.

// server.js - A simple Express server for our webhook

const express = require('express');
const app = express();
const port = 3000;

// This is crucial! It tells Express to parse incoming JSON bodies.
app.use(express.json());

// Define our webhook endpoint URL: /webhook/new-note
app.post('/webhook/new-note', (req, res) => {
  // The note data from Quick Audio Note is in the request body.
  const noteData = req.body;

  console.log('Received new note:', JSON.stringify(noteData, null, 2));

  // Here, you would add your custom logic:
  // - Save the data to your own database
  // - Send a message to a Slack channel
  // - Create a task in Asana or Jira

  // It's important to send a success response back to Quick Audio Note.
  res.status(200).json({ message: 'Webhook received successfully!' });
});

app.listen(port, () => {
  console.log(`Server listening at http://localhost:${port}`);
});

Step 2: Understand the JSON Payload

Every time you create a note, we will send a JSON payload to your endpoint. It will be structured like this, giving you everything you need to work with the note's content.

{
  "noteId": "a1b2c3d4-e5f6-7890-g1h2-i3j4k5l6m7n8",
  "title": "Project Kickoff Meeting",
  "summary": "Key decisions were made about project timelines and team roles. The budget was approved and the next steps are to create the project plan.",
  "transcript": "John: Okay, let's start the meeting. The main goal today is to finalize the timeline...\nSarah: I've reviewed the proposal, and I think we can deliver phase one by the end of Q3...",
  "createdAt": "2025-09-25T14:30:00Z"
}

Step 3: Get a Publicly Accessible URL

For our servers to send you data, your webhook endpoint URL must be public. A localhost URL will not work.

• For Production: Deploy your server application to a cloud provider like Vercel, Heroku, AWS, or DigitalOcean. They will provide you with a permanent public URL.
• For Testing & Development: It's often easiest to use a tunneling service like ngrok. Ngrok creates a secure, public URL that forwards all traffic directly to your local server. It's free and simple to use:
  1. Download and install ngrok.
  2. Run your local server (e.g., node server.js).
  3. In a new terminal, run the command: ngrok http 3000 (replace 3000 with your server's port number).
  4. Ngrok will give you a public "Forwarding" URL that looks like https://random-string.ngrok.io. This is the URL you will use!

Step 4: Connect the URL in Quick Audio Note

You're on the final step! Now you just need to tell Quick Audio Note where to send the data.

1. Navigate to the "Integrations" or "Settings" section of your Quick Audio Note account.
2. Find the Webhook section.
3. Paste the full, public URL of your webhook endpoint (e.g., https://your-domain.com/webhook/new-note or your ngrok URL) into the input box.
4. Click "Save" or "Connect".
5. That's it! Your webhook is now active. You can test it by creating a new audio note. Check your server logs or ngrok's web interface to see the incoming data in real-time.