Initial commit of workflow invocation docs

Author: dylburger

docs-v2/pages/connect/api.mdx

@@ -43,6 +43,25 @@ or a specific version:
 
 ## Authentication
 
+### OAuth
+
+TO DO
+
+### Project keys
+
+You authenticate to the Connect API using **Basic Auth**. Send your project public key as the username and the project secret key as the password. When you make API requests, pass an
+`Authorization` header of the following format:
+
+```shell
+Authorization: Basic base_64(public_key:secret_key)
+```
+
+Clients like `cURL` will often make this easy. For example, here's how you list all accounts on a project:
+
+```shell
+curl 'https://api.pipedream.com/v1/connect/accounts' -u public_key:secret_key
+```
+
 ### TypeScript SDK (Server)
 
 Most of your interactions with the Connect API will happen on the server, to protect API requests and user credentials. You'll use the SDK in [your frontend](#typescript-sdk-browser) to let users connect accounts. Once connected, you'll use the SDK on the server to retrieve credentials, invoke workflows on their behalf, and more.
@@ -102,21 +121,6 @@ export default function Home() {
 }
 ```
 
-### REST API
-
-You authenticate to the Connect API using **Basic Auth**. Send your project public key as the username and the project secret key as the password. When you make API requests, pass an
-`Authorization` header of the following format:
-
-```shell
-Authorization: Basic base_64(public_key:secret_key)
-```
-
-Clients like `cURL` will often make this easy. For example, here's how you list all accounts on a project:
-
-```shell
-curl 'https://api.pipedream.com/v1/connect/accounts' -u public_key:secret_key
-```
-
 ## External users
 
 When you use the Connect API, you'll pass an `external_id` parameter when initiating account connections and retrieving credentials. This is your user's ID, in your system — whatever you use to uniquely identify them. 
@@ -136,6 +140,32 @@ If you need higher rate limits, please [reach out](https://pipedream.com/support
 
 ## API Reference
 
+### Invoke workflows
+
+You can use the SDK to invoke workflows on behalf of your users. Here's an example of invoking a workflow with the SDK:
+
+```typescript
+import { createClient } from "@pipedream/sdk";
+
+const pd = createClient({
+  oauthClientId: "your-oauth-client-id",
+  oauthClientSecret: "your-oauth-client-secret",
+});
+
+const response = await pd.invokeWorkflow(
+  "https://your-workflow-url.m.pipedream.net",
+  {
+    body: {
+      foo: 123,
+      bar: "abc",
+    },
+    // pass any other fetch options here
+  },
+);
+```
+
+`invokeWorkflow` uses Node's `fetch` API, so you can pass any standard options in that object.
+
 ### Tokens
 
 Your app will initiate the account connection flow for your end users in your frontend. But you can't expose your project keys in the client, since they'd be accessible to anyone. Instead, on your server, **you exchange your project keys for a short-lived token that allows a specific user to connect a specific app**, and return that token to your frontend.

packages/sdk/src/server/index.ts

@@ -643,7 +643,7 @@ class ServerClient {
    * @example
    * ```typescript
    * const response: JSON = await client.invokeWorkflow(
-   *   "https://eoy64t2rbte1u2p.m.pipedream.net",
+   *   "https://en-your-endpoint.m.pipedream.net",
    *   {
    *     body: {
    *       foo: 123,