What it does
Remute sends a signed HTTPS request to a URL you register whenever something happens: a call completes, an appointment is booked, changed or cancelled, or a contact is created.
Paste a Webhooks by Zapier, Make or n8n URL and build the rest there: add a row to a sheet, create a task, tell a CRM. Failed deliveries are retried automatically.
- call.completed200 OK · 142 ms
- appointment.booked200 OK · 96 ms
- contact.createdRetrying
Retries on failure
Use cases
Log every call
Add a row to Google Sheets or Airtable for each call, with the summary and the outcome.
Create a CRM record
When a contact is created, push it to your CRM or helpdesk without typing it twice.
Trigger follow-ups
On a booked appointment, send a reminder from your own system or start an internal checklist.
How to connect
You register an endpoint on the Developers page. It needs an HTTPS URL on the public internet.
- In your automation tool, create a trigger that receives webhooks and copy its URL.
- In Remute, open Developers in the sidebar, then add a webhook with that URL and pick the events.
- Copy the signing secret Remute shows once. Your receiver can use it to verify each request.
- Trigger a test event. Check that your automation runs.
- Optionally verify the signature in your receiver, using the webhook-id, webhook-timestamp and webhook-signature headers.
- TriggerWebhooks by Zapier
- ActionAdd a row to a sheet
- StatusOn
Built in your own tool
Events you can subscribe to
Each request carries an id, a type, a timestamp and the data of the event.
| Event | When it fires | Data |
|---|---|---|
| call.completed | A call ends | Call details and summary |
| appointment.booked | An appointment is booked | Start and end, contact, call |
| appointment.changed | An appointment is moved | New times and status |
| appointment.cancelled | An appointment is cancelled | The appointment and its status |
| contact.created | A new contact appears | The contact |
Good to know
- Webhooks need the Pro or Business plan, and the URL must be HTTPS on a public address; private addresses and localhost are rejected.
- A public domain that resolves to a private IP cannot be detected before delivery.
- Requests are signed in the same style as Svix. Verify them in your receiver and reject old timestamps.
Frequently asked questions
Does it work with Zapier, Make and n8n?
Yes. Any tool that gives you an HTTPS URL to receive webhooks can be the receiver, including Webhooks by Zapier, Make and n8n.
How do I know a request is really from Remute?
Each request is signed. Verify the signature with your secret and the webhook-id, webhook-timestamp and webhook-signature headers.
What happens if my receiver is down?
Remute retries failed deliveries automatically. Registered endpoints and recent attempts are visible on the Developers page.