Send customers to GossipGarden with Make
Make can watch an app for a finished job or a new booking. Add an HTTP “Make a request” module at the end of the scenario and every customer it carries is asked for a review.
Connect your tools › Make · Checked against the vendors' own documentation on October 16, 2026.
What you need
- A GossipGarden account with your business and review link set up, and your private address from Settings › Connect.
- A Make account. Make's free plan includes 1,000 credits a month and each module run costs a credit, so a scenario that checks for new customers every 15 minutes uses about 2,900 credits a month on the trigger alone. Prefer an instant trigger where the app offers one.
- A scenario whose first module brings in the customer: a finished job, a paid invoice, a booking.
Your private address. Every account has one. Find it in GossipGarden under Settings › Connect and copy it from there. It ends in 22 letters and numbers, and anyone who has it can add customers to your account, so keep it private. If it leaks, make a new one on the same page and the old one stops working at once.
Set it up
These five steps are the same whichever app starts the scenario.
- Add the module after your trigger
Click the + after the module that brings in the customer, search for HTTP and choose Make a request.
- Paste your private address as the URL
Copy it from Settings › Connect in GossipGarden. Set Method to POST.
- Send JSON
Set Body content type to application/json and Body input method to Data structure, so Make escapes the values for you. (If you choose JSON string instead, you must escape quotes and line breaks yourself.)
- Add one item per field
Add an item for each row of the table below, with the name as written and the matching value from the earlier module. Only an email address or a phone number is required.
- Run once, then look in GossipGarden
Click Run once. The HTTP module's output shows the status code and the answer: 202 with status created means the customer is in and will be asked. Then open Settings › Connect to see it under Recent customers received.
What to send
Add one row per field, with the name on the left exactly as written and the matching value from the earlier step on the right. Only an email address or a phone number is required.
| Name | Choose | Why |
|---|---|---|
| name | The customer's name: one value, or first_name and last_name as two rows. | Optional. Without one, the email address stands in, and the greeting reads “Hi there”. |
| The customer's email address. | Required unless you send a phone number. If the value holds several addresses (a calendar's guest list), we use the first one that isn't yours. | |
| phone | The customer's mobile number. | Optional. A number on its own is saved but not asked: texting needs the customer's consent. |
| external_id | The job, invoice, order or booking number. | Recommended. A customer is asked once for each number, so a retry, a replay or a duplicate task does nothing. Without one, a customer who already has a request in progress is still not asked twice. |
| source | Type the tool's name, like shopify. | Optional. Names the tool in Recent customers received and keeps one tool's numbers apart from another's. |
| send_after | A date and time (ISO 8601). | Optional. Ask no sooner than this, up to 30 days ahead. The customer is then asked within your sending hours. |
To stop a request for a booking you already sent, make the same HTTP request to your address followed by /cancel, with the booking's external_id and source. A request that has already been sent can't be called back.
Test it
Try it with one line
This is the whole interface. Run it in a terminal (replace the address with yours) and the customer appears in Settings › Connect within seconds:
curl -X POST "https://YOUR-PROJECT.supabase.co/functions/v1/hooks/YOUR-TOKEN" \
-H "Content-Type: application/json" \
-d '{"name": "Sam Rivera", "email": "[email protected]", "external_id": "test-1"}'What the answers mean
| Status | Meaning | |
|---|---|---|
| 202 created | The customer is in and will be asked. | |
| 202 waiting | They already have a request in progress, so nothing new was queued. | |
| 202 duplicate | You sent this external_id before. Nothing happened, which is the point: a retry or a replay never asks anyone twice. | |
| 202 suppressed | They unsubscribed, or you sent only a phone number: saved, not asked (texting needs the customer's consent). | |
| 422 | There was no email address or phone number, the email address wasn't valid, or it was your own. The answer says which. | |
| 404 | The address is wrong or has been replaced. Copy the current one from Settings › Connect. | |
| 409 | Your account has reached its customer limit. Contact support to raise it. | |
| 429 | More than 120 deliveries in a minute. Wait a minute and try again. | |
| 413 | The body was larger than 64 KB. |
If it doesn't work
- The module answers 404.
- The address is wrong or has been replaced. Copy the current one from Settings › Connect.
- The module answers 422.
- The answer names the reason: no email address or phone number, an email address that isn't valid, or your own address. Check the value you mapped.
- Can the scenario wait until the job is over?
- Make's Sleep tool waits at most five minutes, so don't wait in Make. Send a send_after time instead and GossipGarden holds the request until then.
- Can my scenario send only some customers?
- Your scenario decides which jobs it sends; that part is yours. GossipGarden asks every customer it receives, and there is no field for how the visit went. Don't filter on a rating: asking only the satisfied customers is review gating.
Every customer this sends is asked exactly like one you type in: the same ask, to everyone, never twice for the same job. Nothing in this guide, in the address or in GossipGarden looks at how the visit went, and you shouldn't filter on it either: asking only the happy customers is review gating, which Google and the FTC prohibit. What review gating is and why it matters.