I have an email workflow that sends mails via brevo and realised that the parameter for recipients is misspelled!
{
“parameters”: {
“sendHTML”: true,
“subject”: “={{ $json.body.subject }}”,
“htmlContent”: “={{ $json.body.body }}”,
“sender”: “office@example.com”,
“receipients”: “={{ $json.body["recipients[0]"] }}”,
“additionalFields”: {…},
No errors, but it might cause problems when someone spells it correctly…
@Bernhard yeah youre right, its misspelled in the node itself — the displayName is “Receipients” and the internal name is “receipients”, theres no correctly-spelled version anywhere in the Brevo node. so its baked in, and the typo is load-bearing: if you correct it to “recipients” in your json the node no longer sees the field, so leave it misspelled in your workflows. worth filing as a bug, though theyd probably only fix the display label since renaming the internal name would break every existing workflow using it.
yeah I guess they will not be happy about it, but maybe they can rename the node and additionally support the old misspelled version, so that it’s fine from now on and existing nodes keep working.
where would i file the bug report?
@Bernhard Issues · n8n-io/n8n · GitHub, use the bug report template. and yeah, aliasing the old spelling is exactly how theyd keep existing workflows working.