From 14a142fa65d9d55d5a10f19475d31c9c7749cfd7 Mon Sep 17 00:00:00 2001 From: Riskey <36894937+RiskeyL@users.noreply.github.com> Date: Tue, 9 Sep 2025 10:10:33 +0800 Subject: [PATCH] Documentation edits made through Mintlify web editor --- en/plugins/quick-start/develop-plugins/tool-oauth.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/en/plugins/quick-start/develop-plugins/tool-oauth.mdx b/en/plugins/quick-start/develop-plugins/tool-oauth.mdx index d0868369..6b1f54bf 100644 --- a/en/plugins/quick-start/develop-plugins/tool-oauth.mdx +++ b/en/plugins/quick-start/develop-plugins/tool-oauth.mdx @@ -20,7 +20,7 @@ OAuth in Dify involves **two separate flows** that developers should understand Admins of Self-Hosted Dify instances must go through this setup flow. -Dify instance's admins or developers first need to register an OAuth app at the third-party service as a trusted application. From this, they'll be able to obtain the necessary credentials to configure the Dify tool provider as an OAuth client. +Dify instance's admins or developers first need to register an OAuth app at the third-party service as a trusted application. From this, they'll be able to obtain the necessary credentials to configure the Dify tool provider as an OAuth client. As an example, here are the steps to setting up an OAuth client for Dify's Gmail tool provider: @@ -100,7 +100,7 @@ The `oauth_schema` section of the provider manifest definitions tells Dify what #### client_schema -This defines the input for OAuth client setup: +Defines the input for OAuth client setup: ```yaml gmail.yaml oauth_schema: @@ -137,7 +137,7 @@ Specifies what the user authorization flow produces (Dify manages these automati Include both `oauth_schema` and `credentials_for_provider` to offer OAuth \+ API key auth options. -### 2. Complete required OAuth methods in Tool Provider +### 2. Complete Required OAuth Methods in Tool Provider Add these imports to where your `ToolProvider` is implemented: