Skip to content

Commit c007d55

Browse files
committed
more links
1 parent a0e9f61 commit c007d55

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

.github/workflows/docs-pr.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ jobs:
3131
- name: Get pnpm store directory
3232
id: pnpm-cache
3333
run: |
34-
echo "::set-output name=pnpm_cache_dir::$(pnpm store path)"
34+
echo "pnpm_cache_dir=$(pnpm store path)" >> $GITHUB_OUTPUT
3535
3636
- uses: actions/cache@v4
3737
name: Setup pnpm cache

docs-v2/pages/rest-api/webhooks.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# REST API Example: Webhooks
22

3-
Pipedream supports webhooks as a way to deliver events to a endpoint you own. Webhooks are managed at an account-level, and you send data to these webhooks using [subscriptions](/rest-api/#subscriptions).
3+
Pipedream supports webhooks as a way to deliver events to an endpoint you own. Webhooks are managed at an account-level, and you send data to these webhooks using [subscriptions](/rest-api/#subscriptions).
44

55
For example, you can run a Twitter [event source](/sources/) that listens for new tweets. If you [subscribe](/rest-api/#subscriptions) the webhook to this source, Pipedream will deliver those tweets directly to your webhook's URL without running a workflow.
66

docs-v2/pages/workflows/steps.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Steps are the building blocks you use to create workflows.
1313

1414
### Triggers
1515

16-
Every workflow begins with a [trigger](/workflows/triggers/) step. Trigger steps initiate the execution of a workflow; i.e., workflows execute on each trigger event. For example, you can create an [HTTP trigger](/workflows/triggers/#http) to accept HTTP requests. We give you a unique URL where you can send HTTP requests, and your workflow is executed on each requesingle st.
16+
Every workflow begins with a [trigger](/workflows/triggers/) step. Trigger steps initiate the execution of a workflow; i.e., workflows execute on each trigger event. For example, you can create an [HTTP trigger](/workflows/triggers/#http) to accept HTTP requests. We give you a unique URL where you can send HTTP requests, and your workflow is executed on each request.
1717

1818
You can add [multiple triggers](/workflows/triggers/#can-i-add-multiple-triggers-to-a-workflow) to a workflow, allowing you to run it on distinct events.
1919

0 commit comments

Comments
 (0)