> For the complete documentation index, see [llms.txt](https://help.clickatell.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clickatell.com/chat-flow/user-facing-nodes/input-nodes/oauth-request.md). # OAuth Request The *OAuth Request* node allows you to authenticate your customers securely against your chosen identity provider (IDP) from within your workflow so that they can access secure services specific to them from your internal platforms. {% embed url="" %} ## Request users to authenticate via Chat Flow To trigger an authentication request as part of your workflow in Chat Flow: 1. Drag and drop the *OAuth Request* node into your workflow. 2. Configure the node and save.

Setup of an OAuth Request node

3. When a customer reaches this step in the flow, a link is presented to them. Clicking this link opens the login page/authentication page of your selected IDP. 4. Once the customer enters their details and is authenticated successfully, they are directed back to the channel they were engaging on. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.clickatell.com/chat-flow/user-facing-nodes/input-nodes/oauth-request.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.