Repository navigation
Send the API key from n8n's HTTP Request node too - #8
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Picking the Shotstack credential in n8n's HTTP Request node fails every call to api.shotstack.io with "Missing API key".
n8n hands that node's address to the credential as
uri, the legacy request field. The credential only readurl, so it never saw a Shotstack address. It now falls back touri. The host rule is unchanged: the key still goes only to api.shotstack.io.Verify:
npm test. Two new cases intest/credential-host-scope.mjs: an Ingest API call throughurigets the key, a third-partyuridoesn't.Risk: credential only. Rollback: revert.