HTTP module validation failed for 6 parameters when sending Telegram inline keyboard via blueprint import

Questions
,
1

:bullseye: What is your goal?

Send a Telegram message with inline keyboard buttons (PUBLISH/REJECT/DRAFT) via HTTP module in a Make scenario that processes news alerts.

:thinking: What is the problem & what have you tried?

I replaced a telegram:SendReplyMessage node with http:ActionSendData v3 via blueprint JSON import to send Telegram inline keyboard buttons.

Error: “Validation failed for 6 parameters” on every run.

I tried adding parameters: shareCookies, rejectUnauthorized, followRedirect, useQuerystring, gzip, useMtls, serializeUrl, followAllRedirects — none worked.

The exact same module (http:ActionSendData v3) works perfectly in node 7 of my blueprint sending another Telegram message. Node 24 is structured identically, only URL and body differ.

I need to know: what are ALL required parameters for http:ActionSendData v3 in a blueprint JSON? Can someone share a working exported blueprint with this module?

:clipboard: Error messages or input/output bundles

Validation failed for 6 parameters:

  • Missing value of required parameter ‘shareCookies’
  • Missing value of required parameter ‘rejectUnauthorized’
  • Missing value of required parameter ‘followRedirect’
  • Missing value of required parameter ‘useQuerystring’
  • Missing value of required parameter ‘gzip’
  • Missing value of required parameter ‘useMtls’

:camera_with_flash: Screenshots (scenario flow, module settings, errors)

scenario_2.webp
scenario_2.webp1456×819 51.7 KB

3

Hello @Jose_Eduardo_Machain,

I deleted your blueprint as it contains your API keys.
Please change them as soon as possible as they were public for a few hours.

Regarding your problem - please start by validating your JSON.

I highly recommend using dedicated modules like Create JSON rather than trying to create them directly in module- especially if they are that complex and use new lines and other escaped characters. Many APIs can throw completely random errors when JSON is not parsed correctly.

Your module #24 contains very messy JSON and it could be the source of your problems.

Keep in mind you are using legacy modules - it is much safer to use the latest ones, where one of the benefits is storing encrypted API keys in the module.

Have a great day,
Michal