How to send review requests from a completed-job form with Make

What happens automatically?

1. 01 →

   Staff submit a completed job

2. 02 →

   Make checks it and sends the contact

3. 03

   EMR runs the review campaign

Who does what?

Set up EMR Automations while signed in as the agency owner and working in the intended client location. The business owner handles access to their own software. They do not need your agency login or a daily EMR task.

Have these ready

• An enabled Jotform account and Make account, with the form owned by the business or managed under an agreed agency arrangement.
• An EMR campaign, a configured domain for its webhook URL and a test email you control.
• A named person who will investigate failed Make runs or depleted credits.

1. 1

   Together

   Create a short internal completion form

   In Jotform, create an internal form with four fields: Job reference (Short Text), Customer first name (Short Text), Customer email (Email), and Job completed? (Single Choice with Yes and No). Require the job reference, email and completion answer. Start with email only for this walkthrough.

   Use this form after the service. Do not use a general enquiry form or a satisfaction rating as the trigger. Start with one business and one EMR location.

   Keep submissions for staff: in the form builder, open Settings → Form Settings → Show More Options → Password Protection and enable a password. Share the form link and password with staff, and confirm the published form asks for it before launch.

   Before moving on: A staff member can fill it in using only details already recorded for the completed job.

2. 2

   Agency

   Create the receiving address in EMR

   Open the client dashboard and location from your agency. Go to Connect → Integrations → Automations and click Connect Make. If the card shows Manage Make, open it and choose New Connection.

   Name the connection, select the campaign and copy the Endpoint URL. Leave the wizard waiting for a test submission. This URL contains a secret token; treat the whole address like a password.

   Before moving on: The wizard displays a URL on the configured domain and is waiting to capture data.

3. 3

   Business owner

   Create the Jotform credential

   In Jotform, open your profile → Settings → API and create a new key. Give this connection Full Access because Make must create the submission webhook.

   Add it securely to the Make connection with the agency. Use a dedicated key so this connection can be revoked independently.

   Before moving on: Make has a dedicated Jotform credential with permission to create its webhook.

4. 4

   Agency

   Start the Make scenario with the form

   Create a scenario and add Jotform → Watch for Submissions. Create its webhook and connection, enter the Jotform API key and select the completion form.

   Click Run once, then submit the form using your own email and Job completed? = Yes. Open the captured output so the form’s actual fields are available to map.

   Before moving on: Make shows the test submission, including the customer email and completion answer.

5. 5

   Agency

   Filter completed jobs and add the HTTP action

   Add HTTP → Make a request after the Jotform module. On the connection between them, add a filter: Job completed? equals Yes AND Customer email exists. These are conditions on the captured form answers: only a finished job with an email can continue.

   In HTTP, choose No authentication, paste the EMR Endpoint URL and set Method to POST. Select Body content type application/JSON and Body input method Data structure. Create three Text fields named first_name, email and job_id. Click each value and select the matching Jotform answer from the mapping panel. Do not type a customer email into the module: that would send every job to the same person.

   Leave the optional signing setting at its default for this basic setup. The private Endpoint URL identifies the EMR connection; you do not add an EMR API key or an Authorization header.

   Before moving on: The HTTP action sends the customer’s values, not the Jotform owner’s email or literal placeholder text.

   The fields to map

   first_name

   Map Customer first name from the Jotform output → EMR First Name

   email

   Map Customer email from the Jotform output → EMR Email

   job_id

   Map Job reference so you can identify the submission later. EMR does not use it to permanently block duplicate jobs.

   See an example of the data EMR receives

   Illustrative data only. Select the real source fields in your automation tool; use your own email for testing.

   {
     "first_name": "Alex",
     "email": "[email protected]",
     "job_id": "JOB-1042"
   }

6. 6

   Agency

   Match the form fields inside EMR

   Keep EMR waiting for its test, run the Make scenario once and submit a fresh completed test job. EMR should show Submission received.

   In EMR, match First Name to first_name and Email to email. Leave Appointment or order date empty for this form: the delay will start when the data arrives. Keep job_id in the submitted data to help identify a job in Recent requests; it is not a rule that blocks repeat jobs.

   Choose A set time after the moment, for example one hour, and click Activate Webhook. The first captured sample was for setup; submit a fresh test after activation to prove campaign delivery.

   Before moving on: The active webhook has the correct email mapping and timing.

7. 7

   Together

   Turn on the scenario and test both paths

   Save the scenario and turn on its scheduling so new submissions run automatically. Complete the tests below with your own details.

   Agree who checks Make’s scenario history and EMR activity. Repeatedly replaying a failed run can create new requests outside the five-minute duplicate window, so inspect the destination before retrying.

   Before moving on: A fresh completed job sends once; an unfinished job is filtered out.

How to know it is working

Follow the event all the way to a message you receive. A green connection or a successful test response is only part of that journey.

If something does not work

At handover, record the connection name, source account, client location, campaign, timing, test result and person responsible for failures. Test again after changing the workflow. Keep passwords, API keys and private webhook URLs out of the handover notes.

Cost, reliability and the simpler alternatives

Common questions