fix: Resolve expressions in credentials following paired item (#8250)

## Summary
Fixes the issue that pairedItem information was not available in
expressions that got used in credentials


## Related tickets and issues

[PAY-1207](https://linear.app/n8n/issue/PAY-1207/paireditem-expressions-not-working-correctly-in-credentials)


## Review / Merge checklist
- [x] PR title and summary are descriptive. **Remember, the title
automatically goes into the changelog. Use `(no-changelog)` otherwise.**
([conventions](https://github.com/n8n-io/n8n/blob/master/.github/pull_request_title_conventions.md))
- [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up
ticket created.
- [ ] Tests included.
> A bug is not considered fixed, unless a test is added to prevent it
from happening again.
   > A feature is not complete without tests.

---------

Co-authored-by: Omar Ajoue <krynble@gmail.com>
This commit is contained in:
Jan Oberhauser
2024-01-08 10:48:20 +01:00
committed by GitHub
parent 008fd5a917
commit ccb2b076f8
7 changed files with 56 additions and 39 deletions

View File

@@ -1882,6 +1882,7 @@ export async function getCredentials(
type: string,
additionalData: IWorkflowExecuteAdditionalData,
mode: WorkflowExecuteMode,
executeData?: IExecuteData,
runExecutionData?: IRunExecutionData | null,
runIndex?: number,
connectionInputData?: INodeExecutionData[],
@@ -2001,6 +2002,7 @@ export async function getCredentials(
nodeCredentials,
type,
mode,
executeData,
false,
expressionResolveValues,
);
@@ -3149,6 +3151,7 @@ export function getExecuteFunctions(
type,
additionalData,
mode,
executeData,
runExecutionData,
runIndex,
connectionInputData,
@@ -3281,6 +3284,7 @@ export function getExecuteFunctions(
key,
additionalData,
mode,
executeData,
runExecutionData,
runIndex,
connectionInputData,
@@ -3608,6 +3612,7 @@ export function getExecuteSingleFunctions(
type,
additionalData,
mode,
executeData,
runExecutionData,
runIndex,
connectionInputData,