If your reception has certain working hours, and you want to prevent reservations from being created after a specific time of the day, you can automate same-day restrictions by using our integration partner Zapier.

 

Requirements to implement same-day restrictions:

1. Have a Mews Enterprise subscription.
2. Be connected to the “Webhooks by Zapier" integration in your Mews Marketplace. 
   • As this is a custom integration, send a request to our Support Team to arrange for it to be added to your Marketplace. Once your integration is connected, the Mews Support team provides both the Client Token and Access Token for your Webhooks Integration connection.
3. Have a Zapier account (Starter subscription or above).
   • After successfully connecting your integration, you can create a Zapier account. Subscription fees are applicable for your Zapier account (website).

 

Setting up your Custom Webhook & Zap

 

1. Ensure your Zapier account time zone matches the property’s time zone (e.g. Australia/Sydney).

The following steps walk you through creating a brand new custom Webhook from scratch. In your Zapier account, you will need to create:

 

• A Trigger
• A Formatter
• A Custom Webhook request

 

Create the Trigger

1. Create a new Zap. Note: Zapier automatically generates a basic zap containing a trigger and an action (skip the Zapier AI automation).
2. Click on the first step in your Zap: Trigger.
3. For the App, select Schedule by Zapier.
4. On the Trigger event dropdown, select the frequency for how often you need the zap to run. Generally this is Every Day.
5. Click Continue.
6. Select the Time of day you need the zap to run. This is the time the restriction is created in Mews. Note: the time of day depends on the time zone applicable for your Zapier account. For example, if your Zapier account is set to the Houston/Texas time zone, the zap will be scheduled to run at the time specified in Houston's local time.
7. Under Trigger on weekends? select yes/no whether you need the zap to run on weekends. 
8. Click Continue.
9. Test your trigger. This step does not generate any restrictions, but checks that your trigger configurations are correct, and creates a shell record containing set data that can be used for manual testing. Zapier uses this data when testing your custom webhook after it has been set up.
10. Your trigger is now configured. Click on the Continue with Selected Record option to proceed to setting up your formatter step.

 

Create the Formatter step

1. Beneath the trigger step, click the plus sign to create a new step between the two existing steps.  
2. For the App, select Formatter by Zapier.
3. In Action event select Date / Time
4. Click Continue.
5. In the transform field, select Format.
6. You will see a Values>Input field. Click on the + (plus) icon within the Input field, and select the pre-defined Year, Month, and Day placeholders. Ensure that they are separated by a “-“ (hyphen). Type T00:00:00 after the day placeholder. Your input field should look like this:
   
   
   
   
7. In the To Format field, select the date format: YYYY-MM-DDTHH:mm:ssZ (2006-01-22T23:04:05 + 0000)
8. In to To Timezone, select UTC.
9. In the From Format, select the date format: YYYY-MM-DDTHH:mm:ssZ (2006-01-22T23:04:05 + 0000)
10. In the From Timezone, select the time zone of the Zapier account (i.e. the Property’s time zone).
11. Click Continue.
12. Test the step. The output should follow the: YYYY-MM-DDTHH:mm:ssZ (2006-01-22T:04:05 + 0000) format. Click Edit, and remove the trailing time zone indicator (+0000) and replace with a “Z” immediately after the second values.
    E.g.
    Your output should go from this: 2025-06-29T14:00:00 +0000
    To this: 2025-06-29T14:00:00Z
13. Click Continue to proceed to the webhook step.

 

Create the Custom Webhook

1. Move to the last step in your zap.
2. For the App, select Webhooks by Zapier. Note: You will need a Zapier subscription of Starter or above to use this feature.
3. For the Action event, select Custom Request.
4. Click Continue.
5. In the Method field, select POST. 
6. In the URL field, enter the correct URL for the environment you wish to work in:
• For Mews Demo, enter: https://api.mews-demo.com/api/connector/v1/restrictions/set
• For Mews Production account, enter: https://api.mews.com/api/connector/v1/restrictions/set
  Please note: the restrictions/add endpoint has now been deprecated.

7. In the Data Pass-Through, select FALSE.
8. In the Data field, copy and paste the code below:
   

   {
   
       "CLIENTTOKEN": "(provided by support)",
   
       "ACCESSTOKEN": "(provided by support)",
   
     "Client": "Sample Client 1.0.0",
   
     "ServiceId": "(of the bookable service the restriction should apply to)",
   
     "Data": [
   
       {
   
         "Type": "Start",
   
                   "STARTUTC": "Output",
   
                   "ENDUTC": "Output",
   
         "Days": {
   
           "Monday": true,
   
           "Tuesday": true,
   
           "Wednesday": true,
   
           "Thursday": true,
   
           "Friday": true,
   
           "Saturday": true,
   
           "Sunday": true
   
         }
   
       }
   
     ]
   
   }

9. In the data field, replace the text {{_GEN_1751268785267__output}} for the StartUTC with the Output from step 2. Place the cursor between the quotation marks, press the plus icon, select the 2. Date /Time Formatter step and select the Output option. This will insert the placeholder for the converted date/time.
10. Repeat this process for the EndUTC.
11. Once the placeholders, client and access token and service IDs have all been added to the webhooks code, click continue.
12. Test the step and check the Mews Restrictions to ensure the close out has been created as expected. Delete any test restrictions.

 

Find an integration's access token

How to find Product ID/Service ID/Accounting Category ID in Mews?