Webhooks let ManyRequests tell another app the moment something happens in your portal, like a new client or a new request. You give ManyRequests a URL, pick an event, and ManyRequests sends the event's data to that URL every time it happens.
Use case: post a message in your team's Slack channel whenever a client submits a request. Create a webhook in an automation tool such as Make, paste its URL into ManyRequests with the REQUEST CREATED event, and connect it to Slack.
Only portal admins and admins can manage webhooks.
How to add a webhook
Go to Settings > Integrations and open the Webhooks tab.
Click Add webhook.
Enter a Name so you can recognise it later, and paste the Webhook URL from the app that will receive the data.
Under Webhook event, choose the event that should trigger it. Each webhook listens to one event; add one webhook per event you need.
Click Save changes.
Your webhooks are listed with their Name, URL, Event type and Created at date.
How to edit or delete a webhook
On the Webhooks tab, click the three dots at the end of the webhook's row.
Choose Edit to change its name, URL or event, then click Save changes. Or choose Delete and confirm.
Events you can use
Webhook event | Sent when |
CLIENT CREATED | A new client is added. |
CLIENT UPDATED | A client's details change. |
ORGANIZATION UPDATED | An organization's details change. |
REQUEST CREATED | A request is submitted. Queued requests are sent when they leave the queue. |
REQUEST UPDATED | A request is updated. |
PAYMENT CREATED | An invoice is created. The data includes its status and paid date. |
COMMENT CREATED | A comment is posted on a request (internal comments are flagged as internal). |
CANVAS COMMENT CREATED | A comment is added on a file (annotation). |
SUBSCRIPTION CREATED | A new subscription starts. |
SUBSCRIPTION CANCELED | A subscription is canceled. |
SUBSCRIPTION SET TO CANCEL AT PERIOD END | A subscription is set to cancel at the end of its period. |
SUBSCRIPTION PAUSED | A subscription is paused. |
SUBSCRIPTION RESUMED FROM PAUSE | A paused subscription is resumed. |
SUBSCRIPTION UPDATED | A subscription's details change. |
REVIEW CREATED | A client leaves a review on a request. |
BRAND CREATED | A new brand is created. |
REQUEST ASSIGNEES CHANGED | Team members are assigned to or removed from a request. |
REQUEST TAG ADDED | A tag is added to a request. |
REQUEST TAG REMOVED | A tag is removed from a request. |
What ManyRequests sends
Each event is sent as an HTTP
POSTrequest with a JSON body.Requests are not signed: there's no signature header to verify. Use a long, hard-to-guess URL and treat it like a password.
If your URL doesn't respond within 3 seconds or returns an error, ManyRequests tries again, up to 3 attempts.
For example, a CLIENT CREATED webhook sends:
{"id": 42, "name": "John Doe", "email": "[email protected]", "created_at": "2026-10-02T09:15:00.000000Z", "organization": "ACME Corp."}
Request events include more data, such as the request's number, link, status, service, client, organization, assignees, files, form answers and tags.
Example: send new requests to Slack with Make
In Make, create a scenario and add the Webhooks module with the Custom webhook trigger.
Add a webhook, give it a name and copy the URL Make gives you.
In ManyRequests, add a webhook with that URL and the REQUEST CREATED event.
Back in Make, add a Slack module (for example, Create a Message), connect your Slack account and map fields such as the request title and URL into the message.
Run the scenario once, submit a test request in your portal to check the message arrives, then turn the scenario on.
The same approach works with Zapier, n8n, Pipedream or your own server. If you use Zapier, its ManyRequests app may be simpler: see Complete list of Zapier triggers and actions.