Hi Novacura Gurus!
We are using a scheduled machine workflow in Novacura to send a SQL dataset encoded as JSON via an HTTP POST using the Web Page Submit connector.
At the moment, the connector has predefined Authentication URL and HTTP headers, and it sends the payload as URL‑encoded data, which is an old standard.
Example
What we want to send (standard JSON):
JSON
{
“Name”: “John Smith”,
“Age”: 23
}
What is currently being sent at the moment (URL‑encoded):
Name=John+Smith&Age=23
We have now received new requirements from our partner:
-
The payload must be sent as standard JSON (not URL‑encoded).
-
Authentication must be updated to use machine tokens instead of basic authentication (username/password).
My questions
-
Is it possible to build this solution using the Web Page Submit connector, or does it only support URL‑encoded payloads?
-
Since we currently cannot use the REST connector, is there any way to:
-
Retrieve an authentication token,
-
Store it in a variable,
-
Fetch employee data,
-
Convert it into a JSON payload,
-
And then send it to the endpoint using the token for authentication
all within the Web Page Submit connector?
-
Or would we need a workaround, for example sending the data to Azure, and handling the token retrieval and authentication logic there instead?
All creative ideas are most welcome!
BR,
Viktor