AWS SES Template - ERROR: Bad request - please check your parameters

Describe the problem/error/question


Getting an error when trying to send an email using the Send Template operation. It appears to be an issue when using the template operation. I can confirm it works when using the send operation.

What is the error message (if any)?

ERROR: Bad request - please check your parameters


NodeApiError: Bad request - please check your parameters
    at Object.awsApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/SES/GenericFunctions.js:27:15)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Object.awsApiRequestSOAP (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/SES/GenericFunctions.js:42:22)
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/SES/AwsSes.node.js:971:40)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:730:19)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:660:53
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:1062:20

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

    "id": "rec23b67jY0j0G6rY",
    "createdTime": "2024-03-05T15:36:13.000Z",
    "Firstname": "John",
    "Lastname": "Doe",
    "Email": "[email protected]",
    "Name": "John Doe",
    "Created At": "2024-03-05T15:36:13.000Z"

Information on your n8n setup

  • n8n version: n8nio/n8n:1.31.0
  • Database (default: SQLite): postgreSQL
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: AWS Linux (Kubernetes)

Hey @Ebenezer_Isaac,

Welcome to the community :raised_hands:

As you have noticed this is something we are aware of and we have a GitHub issue opened for this and an internal ticket that we are tracking as NODE-1216 to fix this.

Hopefully this will be fixed during our next internal node team bug fix session.

1 Like

Hey @Jon, just following up with this one. Do you know when the fix for this would be released? Thanks

Hey @Ebenezer_Isaac,

I don’t have an exact date at the moment but it should be soon as we have recently hired more people for our support team so I will be able to spend more time fixing bugs like this that might fall through the gaps.