Question

Chatbot embed restrict domain

  • 1 December 2023
  • 5 replies
  • 115 views

Userlevel 1

Hi 

Using instructions https://help.zapier.com/hc/en-us/articles/18151892318861-Embed-a-chatbot-on-a-webpage and switch on restrict domain and enter allowed domain eg mydomain.com or www.mydomain.com. but this now restricts mydomain.com from using the interface and get chat-app-0e4efa.zapier.app refused to connect. 

If I switch off restrict domains it works. 

Does this work ok for other users ?

 


5 replies

Userlevel 6
Badge +8

Is mydomain.com where you’re embedding the chatbot?

Userlevel 1

no that was an example .. its embedded on webiflex.com and I have set restrict domains = ON with an allowed domain = webiflex.com. Let me know if you want me to switch restrict domains = OFF 

Userlevel 1

@shalgrim further to prev comment i also notice below :

Refused to frame 'https://chat-app-0e4efa.zapier.app/' because an ancestor violates the following Content Security Policy directive: "frame-ancestors zapier.com zapier-staging.com https://www.google.com/recaptcha/ https://www.gstatic.com/recaptcha/ https://interfaces-synthetics-public.zapier.app/ https://webiflex.com https://www.webiflex.com".

Userlevel 7
Badge +6

Hi there @webiflex,

Zapier Interfaces is currently in its Beta phase, addressing the error you're encountering can be a bit challenging due to the limited tools we have at this stage. For the best assistance, I suggest getting in touch with our Interfaces team directly. They're the right folks to look into this issue for you.

You can reach out to them here: https://eap.zapier.app/interfaces

Thanks so much for your patience and understanding!

Userlevel 1

@ken.a  Hi , ok have submitted form but have done before and get no response. In case interface team are looking at this I have found further details . 

As I am using Google sites we get the following 

embedding page's origin (https:/**number removed**-atari-embeds.googleusercontent.com/) is not included in the allowed domains in the frame-ancestors directive, it would violate the CSP policy, and you might encounter a "Refused to frame" error. The Referrer header indicates the page from which the request originates.

In Summary any google site even with domain added will post above. I am hoping interface team can find some workaround. 

Reply