Automate Review Requests with Pabbly Connect
Add an API by Pabbly action to any Pabbly Connect workflow and EmbedMyReviews adds the contact to a review campaign, then sends the request by SMS or email at the time you choose. Payments, forms, bookings and CRM updates all work the same way.
No app to install on either side. The workflow posts to an endpoint on your own domain, and you map the fields visually from a test submission.
Trigger
Razorpay · Payment captured
Action
API by Pabbly · POST
reviews.youragency.com/api/webhooks/inbound/•••••
Sends the next morning at 9:00 AM. "Hi Arjun, thanks for your purchase. Would you share a quick review?"
How It Works
Four steps in the setup wizard. The endpoint URL is generated for you, and the field mapping is built from a real test submission.
Name the connection and choose a campaign
Give the connection a name your team will recognise and pick the review campaign that incoming contacts join.
Add API by Pabbly and send a test
In Pabbly, add an API by Pabbly action after your trigger, set the method to POST, paste the endpoint URL, then Save and Send Test Request. The payload is captured.
Map fields
Point first name, last name or full name, email and phone at the matching fields in the captured payload. Email or phone is required.
Choose when to send
Straight away, a set time after the appointment or order date, or the next morning at a chosen time. Then activate.
What triggers a request, and how it is timed
The trigger is whatever starts your Pabbly workflow. EmbedMyReviews only sees the POST that arrives, so any Pabbly trigger app can start a review request.
Workflows Agencies Build with Pabbly Connect
One API by Pabbly action turns the tools a client already runs into a source of review requests, without changing how the client works.
Payment gateways
Razorpay, PayU, Instamojo and similar triggers in Pabbly send the buyer's details after a captured payment. The request follows the purchase.
Form builders
Elementor, Gravity Forms, Jotform and Google Forms submissions map straight to name, email and phone.
Booking and scheduling tools
Map the appointment end time as the anchor so the request goes out after the visit, not when it was booked.
CRMs and pipelines
Trigger on a deal moving to won or a contact gaining a tag, and let the contact join the campaign the same minute.
Courses and memberships
Enrolment or completion events from an LMS can ask for a review a few days later, once the learner has finished the material.
Agencies managing client workflows
Each client gets its own connection and endpoint under its own account. Nothing is shared between clients.
Integration Features
The same inbound engine that powers the Zapier, Make and n8n presets, with guidance written for Pabbly.
Works in any Pabbly workflow
Add an API by Pabbly action after any trigger, choose POST, and paste the endpoint URL. Nothing else is needed on the Pabbly side.
Test-payload capture and visual mapping
Send one test from Pabbly and pick fields from what arrived. Nested values use dot-notation paths, and a single full-name field is split into first and last automatically.
Date-anchored timing
Straight away, 15 minutes to 7 days after the appointment or order date, or the next morning at a chosen time. Without a mapped date, the delay runs from arrival.
Endpoint on your own domain
The URL your client pastes into Pabbly is built from your white-label domain. There is no third-party brand anywhere in their workflow.
Signing secret and rotatable token
Add an optional HMAC-SHA256 signing secret, and regenerate the endpoint token whenever you need to. The old URL stops working immediately.
Lost-job recovery
A request anchored to a date weeks away sits in the queue for a long time. Every six hours, any send that went missing is re-dispatched from the stored record.
What you need before connecting
There is no EmbedMyReviews app in the Pabbly Connect directory, and none is needed. The API by Pabbly action posts to an endpoint that the setup wizard generates for you.
- A Pabbly Connect account on any plan that includes the API by Pabbly action.
- A configured domain on the EmbedMyReviews account. The endpoint URL is built from it.
- A review campaign with SMS or email configured through your own provider.
- A trigger step in Pabbly whose output includes an email or phone number for the customer.
White-label safe
The endpoint lives on your own domain, so the client never sees a third-party brand in their Pabbly workflow. The URL they paste reads as your platform, and the setup guidance they follow is hosted on your dashboard.
Skip the test if you prefer
The test submission makes mapping faster, but you can skip it and enter field paths by hand, then re-capture later once the workflow is live.
Your providers. Wholesale rates.
Review requests triggered from Pabbly Connect are sent through your own Twilio (SMS) or SMTP (email) accounts. You pay wholesale rates directly, with no EmbedMyReviews markup on messaging. Your Pabbly plan is billed separately by Pabbly.
Common questions
Is there an EmbedMyReviews app in Pabbly Connect?
No, and none is needed. Add an API by Pabbly action after your trigger, set the method to POST, and paste the endpoint URL that the setup wizard gives you. The endpoint sits on your own white-label domain. Pabbly sends the data, EmbedMyReviews maps it to a contact, and the campaign takes it from there.
What data do I send?
A JSON body with the customer's name, email and phone, plus an optional appointment or order date. Email or phone is required, the rest is optional. You do not need to rename anything in Pabbly: send a test, then pick which incoming field is the first name, last name or full name, email, phone and date. Nested values are addressed with dot-notation paths, and a single full-name field is split automatically.
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. The delay you choose, from 15 minutes up to 7 days, or the next morning at a set time, is then measured from that moment rather than from when the workflow ran. Fields such as end_time, appointment_date, completed_at and order_date are suggested automatically when the test payload contains one. If a submission arrives without the date, the arrival time is used.
What happens if the payload has no email or phone?
The submission is logged as skipped with the reason, and no request is sent. Everything that arrives is listed in the connection log with its outcome, so you can see which Pabbly runs produced a request and which did not.
Can I secure the endpoint?
The endpoint token is unguessable on its own, and you can regenerate it at any time, which stops the old URL immediately. For a stronger guarantee, add a signing secret and have the sender sign the raw body with HMAC-SHA256. Requests that fail the signature check are rejected.
Pabbly Connect, Zapier or Make: which should I use?
All three use the same inbound engine and the same four-step wizard, so choose whichever platform the client already pays for. On Zapier the Webhooks by Zapier action requires a paid plan. On Make the HTTP module works on every plan, including free. On Pabbly Connect the API by Pabbly action is used on any plan that includes it. The wizard, field mapping and timing options are identical across all three.
Related integrations
Zapier
The same inbound flow through Webhooks by Zapier on paid Zapier plans.
Make
Post from the HTTP module on every Make plan, including free.
n8n
The HTTP Request node, on n8n Cloud or self-hosted.
Inbound Webhooks
Point any app that can send a POST at the same endpoint, no automation platform required.
Connect Pabbly Connect and let your workflows 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.