docs: update code examples to use KNOCK_SECRET_API_KEY #1281
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updates Node.js code examples in the workflow triggering documentation to use
KNOCK_SECRET_API_KEYinstead ofKNOCK_API_KEYfor clarity about appropriate key usage.Files updated:
content/send-notifications/triggering-workflows/schedules.mdx- inline code exampledata/code/workflows/trigger.ts- MultiLangCodeBlock snippetdata/code/workflows/trigger-with-actor.ts- MultiLangCodeBlock snippetdata/code/workflows/trigger-with-object-as-recipient.ts- MultiLangCodeBlock snippetdata/code/workflows/cancel.ts- MultiLangCodeBlock snippetNote for reviewer: Only the Node.js examples that use
process.env.KNOCK_API_KEYwere updated. Other language examples (Python, Ruby, Go, Java, etc.) use hardcoded placeholder values likesk_12345which were left unchanged.Tasks
Requested via Slack by Scoti Dodson
Link to Devin run