Automate Review Requests with Make
Add an HTTP module to any Make scenario and post customer details to your EmbedMyReviews endpoint. EmbedMyReviews maps the fields, times the request around the appointment or order date, and sends it by SMS or email through your own providers.
Works on every Make plan, including free. There is no EmbedMyReviews module to install and no API key to manage.
Salesforce • Pipedrive • Acuity • Typeform
HTTP: Make a request
POST youragency.com/api/webhooks/inbound/…
EmbedMyReviews
Fields mapped, request scheduled
How It Works
Four steps in the setup wizard. Make sends the data, EmbedMyReviews handles the mapping, the timing and the send.
Name the connection
In EmbedMyReviews, give the connection a name and choose the review campaign it feeds. You get an endpoint URL on your own domain.
Add the HTTP module
After your trigger, add HTTP, Make a request. Method POST, body type Raw, content type JSON. Paste the endpoint URL and click Run once to send a test.
Map the fields
EmbedMyReviews captures the test payload. Point first name, last name or full name, email and phone at the right keys, plus an optional appointment or order date.
Choose when to send
Straight away, a set delay of up to 7 days timed from the appointment or order date, or the next morning at a chosen time. Then activate.
What triggers a request, and what never does
The trigger is whatever your scenario sends. EmbedMyReviews has no event names of its own, so a filter or router in Make decides who reaches the endpoint.
Why Agencies Choose Make
Make (formerly Integromat) is built for multi-step automations with branching, filters and transformations, laid out visually.
Visual Scenario Builder
Drag-and-drop interface shows your entire workflow visually. See exactly how data flows between apps and where logic branches.
Routers & Filters
Split workflows based on conditions. Each EmbedMyReviews connection is tied to one campaign, so a router can send different customer types to different endpoints.
Data Transformations
Built-in functions to format, parse, and transform data. Clean phone numbers, format names and merge fields before the request goes out, all without code.
Scheduling Options
Run scenarios on a schedule or instantly on a trigger. The review-request delay itself is set in EmbedMyReviews, so the scenario can finish as soon as the request is posted.
Error Handling
Built-in error handlers catch a failed HTTP request and retry it or alert you, so a temporary network issue does not lose a review request.
Execution History
Full logs of every scenario run on the Make side, and a log of every request received, skipped, or sent on the EmbedMyReviews side.
Popular Make Scenarios
Common scenarios agencies build with the HTTP module. Each one ends the same way: a POST to the endpoint with the customer's details.
CRM → Review Request
When a deal is marked Won in Pipedrive, Salesforce, or any CRM, post the contact to the endpoint and let EmbedMyReviews apply the delay.
Invoice Paid → Review Request
Trigger review requests when invoices are paid in QuickBooks, Xero, or FreshBooks. Map the paid date so the delay runs from the transaction.
E-commerce Order Delivered
When shipping status changes to Delivered in BigCommerce, Magento, or any store Make connects to, post the order and request a product review.
Appointment Completed
After appointments end in Acuity, Cal.com, or SimplyBook.me, post the booking with its end time mapped as the appointment date.
Form Submission → Campaign
Route form submissions from Typeform, JotForm, or Google Forms to the right endpoint based on form fields.
Support Ticket Resolved
When support tickets are marked resolved in Zendesk, Freshdesk, or Intercom, request feedback on the support experience.
Shopify, WooCommerce, HubSpot and Calendly have native EmbedMyReviews integrations that need no scenario at all. See Shopify, WooCommerce, HubSpot and Calendly.
Make vs Zapier: When to Choose Make
Both reach EmbedMyReviews the same way, with an HTTP request to your endpoint. The difference is what it costs and how the workflow is built.
Choose Make When
- •You want to send data to EmbedMyReviews on a free plan. The HTTP module is included on every Make tier
- •You need complex branching logic with multiple paths
- •Visual workflow design is important for your team
- •You need heavy data transformations between steps
- •You want detailed execution logs and debugging tools
Consider Zapier When
- •You need the widest app selection (6,000+ apps)
- •Simple, linear workflows are all you need
- •You are already on a paid Zapier plan. Webhooks by Zapier, the step that posts to the endpoint, is not available on the free tier
- •Your team already lives in Zapier's ecosystem
The endpoint is the same for both, so moving from one platform to the other later means moving the HTTP step, not rebuilding the connection. See the Zapier integration.
What you need before connecting
The connection is a URL that Make posts to. Nothing is installed on either side, and the wizard checks each step before anything goes live.
- A Make account on any plan, including free. The HTTP module is a core module with no add-on required.
- A configured domain on your EmbedMyReviews account. The endpoint URL is built from it, so it lives on your own white-label domain.
- A review campaign with SMS or email configured through your own provider.
Optional signing secret
Turn on a signing secret and every request has to carry an HMAC-SHA256 signature that EmbedMyReviews verifies before the payload is accepted. Useful when the scenario handles data you would rather not trust to the URL alone.
Rotate the token any time
Regenerating the token gives you a new URL and the old one stops working immediately. Update the HTTP module and the scenario carries on.
Your providers. Wholesale rates.
Make posts the contact to EmbedMyReviews, and EmbedMyReviews sends the review request through your own Twilio (SMS) or SMTP (email) accounts. You pay wholesale rates directly to your providers, with no EmbedMyReviews markup on messaging.
Common questions
Is there an EmbedMyReviews module in Make?
No. You use Make's built-in HTTP module (Make a request) to POST customer details to the endpoint URL that EmbedMyReviews gives you. There is nothing to install in Make and no API key to paste. The URL carries its own token.
Which Make plan do I need?
Any plan, including the free one. The HTTP module is a core Make module, so a scenario that ends with a POST to your endpoint runs on every tier. Your only limit is Make's operation allowance for the plan you are on.
What fields do I need to send?
An email address or a phone number is required, and both can be sent. Add a first name and last name, or a single full name that EmbedMyReviews splits for you. The keys in your JSON can be named anything; you map them in EmbedMyReviews from the captured test payload, including nested values with dot notation. You can also send an appointment or order date to anchor the timing.
Can I time the request around the appointment or order date?
Yes. Map a date field from the payload as the appointment or order date and the delay is measured from that moment rather than from when the request arrived. Choose straight away, a set delay from 15 minutes up to 7 days, or the next morning at a chosen time. If a submission arrives without the date, EmbedMyReviews uses the arrival time instead.
Can I secure the endpoint?
The URL contains a random token, and you can regenerate it at any time, which stops the old URL immediately. For an extra check, turn on a signing secret and EmbedMyReviews verifies an HMAC-SHA256 signature on every request before accepting the payload.
Does the client see EmbedMyReviews branding?
No. The endpoint URL is built from the domain configured on your account, so it reads as youragency.com rather than EmbedMyReviews, and the review requests themselves go out through the client's own SMS and email providers.
Related integrations
Connect Make and let your scenarios ask for the review.
Included in the flat $99/month plan for unlimited clients and connections. No per-connection fees.
No credit card required. Explore the platform for 14 days.