Skip to content

Commit b529c0a

Browse files
small patch
1 parent 7c104c4 commit b529c0a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs-v2/pages/connect/workflows.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ import { Steps, Tabs } from 'nextra/components'
22

33
# Running workflows for your end users
44

5-
Just like you can build and run internal [workflows](/docs/workflows/) for your team, **you can run workflows for [your end users](/connect/api#external-users), too**.
5+
Just like you can build and run internal [workflows](/workflows/) for your team, **you can run workflows for [your end users](/connect/api#external-users), too**.
66

77
Whether you're building well-defined integrations or more-autonomous AI agents, workflows provide a powerful set of tools for running [code](/code) or [pre-defined actions](/workflows/actions) on behalf of your users. Pipedream's UI makes it easy to build, test, and [debug](/workflows/inspect) workflows.
88

@@ -85,7 +85,7 @@ npm i @pipedream/sdk
8585

8686
To invoke workflows, you'll need:
8787

88-
1. The OAuth client ID and secret from **Step 1**
88+
1. The OAuth client ID and secret from **[Step 1](/connect/workflows#create-an-oauth-client)**
8989
2. Your [Project ID](/projects#finding-your-projects-id)
9090
3. Your workflow's HTTP endpoint URL
9191
4. The [external user ID](/connect/api#external-users) of the user you'd like to run the workflow for

0 commit comments

Comments
 (0)