# DOC- Chatbot configuration reminder

**URL:** <https://devforum.zoom.us/t/doc-chatbot-configuration-reminder/41413>\
**Category:** Feature Requests\
**Created:** [January 24, 2021, 6:58pm UTC](https://devforum.zoom.us/t/doc-chatbot-configuration-reminder/41413 "2021-01-24T18:58:04Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![breynoldszoom](https://avatars.discourse-cdn.com/v4/letter/b/a88e57/32.png) [@breynoldszoom](https://devforum.zoom.us/u/breynoldszoom)\
**Post date:** [January 24, 2021, 6:58pm UTC](https://devforum.zoom.us/t/doc-chatbot-configuration-reminder/41413/1 "2021-01-24T18:58:04Z")

</div>

**Is your feature request related to a problem? Please describe.**  
In the end it was pilot error, but this took up hours of my time and likely  
and hour of Zoom support time including a live Zoom call. A gentle  
reminder would have likely avoided this for everyone.

**Describe the solution you’d like**  
Suggested text to add to the Chat bot definition flow.

“NOTE- If you are using any server side IP whitelisting in front of your endpoint  
then be sure BOTH the Zoom client IP and all Zoom servers are granted access.”

(I think the latter are really hard to enumerate so the net may be a wide open port  
and the use of the Zoom verification token. Certainly more elegant firewall rules can  
be used… I was seeing the oAuth request on my AWS endpoint because I had my laptop whitelisted.  
I was not seeing any slash command requests from Zoom servers though.  
That’s obvious in hindsight, but a one sentence reminder similar to above would be useful).

**Describe alternatives you’ve considered**  
NA

**Additional context**  
NA