topic Re: Obtain synthetic variable via workflow in Synthetic Monitoring

Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 10:41:02 GMT

Hi team,

I am trying to create a synthetic monitor that obtains a token via JavaScript and then makes an API call using that token as the Authorization token. After the API call, I want to send the result in an email.

What is the best way to do this? Where can we store the token to use it later on a workflow?

We need a way to store the tokento use it because the result of a batch execution doesn't show the token.

Thanks in advance!

Elena

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 11:16:37 GMT

Hello, @elenaperez!

Could you share why you need to fetch the token from the Synthetic monitor with JavaScript?

Is the token only created after a browser login, or is it just stored in localStorage by the application?

Also, why not use Credential Vault instead? The usual pattern is to store the authentication secrets there, get the token directly in the Workflow, use it in the next API call, and then send the email. This is safer than trying to pass the token from Synthetic execution results.

I hope it helps you 😁

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 11:26:20 GMT

The token is stored on the localstorage after doing some steps on the page. That is the only way to get it.

These are the steps before obtaining the token:

If I store the token in the credential vault, which option should I select?

And how do I get it from the workflow later?

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 11:35:39 GMT

Thanks for sharing the steps.

Since the token is only created after the browser login and stored in localStorage, it makes sense that you are retrieving it with JavaScript inside the Synthetic monitor.

However, I would avoid storing that generated token in Credential Vault as I said. Credential Vault is intended for static credentials, such as username/password, client ID, client secret, or API keys, not for short-lived session tokens generated during a browser session.

If the API call depends on that localStorage token, the cleanest option is to perform the API call in the same Synthetic JavaScript step, immediately after reading the token.

If the final goal is to send the API result by email through a Workflow, then the better long-term design would be to move the authentication/API logic into the Workflow, using Credential Vault only for the login credentials or client credentials. The Workflow would then generate the token, call the API, format the result, and send the email.

For the Credential Vault scope:

Synthetic: use this if the credential is only used by the Synthetic monitor.
AppEngine: use this if the credential needs to be used by Workflows/AppEngine actions.

I would not store the runtime token itself in Credential Vault unless there is no other option and you are aware of the expiration and security implications.

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 11:40:15 GMT

I am not sure I understand. If I do the API call from the workflow, how do I obtain the token generated from the synthetic?

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 11:45:20 GMT

You would not obtain the token generated by the Synthetic monitor from the Workflow. That is the key point.

The token created during the Synthetic execution belongs to that browser session runtime, and it is not meant to be passed later to a Workflow. Synthetic results also may hide sensitive values, so it is not a reliable place to extract a token from.

If the API call is done from the Workflow, then the Workflow should also obtain its own token. In that design, Credential Vault stores the static credentials, such as username/password, client ID, or client secret. Then the Workflow uses those credentials to authenticate, receives a new token, uses it in the API call, and sends the email.

So the desing would be something like this:

Workflow
  1. Read credentials from Credential Vault
  2. Authenticate and get a new token
  3. Call the API using that token
  4. Format the response
  5. Send the email

If the token can only be created by going through the browser flow in Synthetic and there is no backend authentication endpoint available, then the API call should stay inside the Synthetic JavaScript step, right after reading the token from Localstorage. In that case, the Workflow will not be able to reuse that Synthetic-generated token directly.

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 13:05:17 GMT

The only way to obtain the token is via the browser flow. What about sending the API result on a log?
Something is not working with my code:

(async function() { // 1) Leer token RINA var rinaToken = localStorage.getItem("rina_token") || ""; if (!rinaToken) { api.error("[RINA] Token not found"); return; } // 2) Llamada a la API de RINA var RINA_API_URL = "https://{environmentid}.live.dynatrace.com/api/v2/logs/ingest"; var DT_LOG_INGEST_TOKEN = "****"; try { var logPayload = [{ content: rinaResponseBody, attributes: { source: "synthetic-rina", api: "PendingMessages", synthetic: "browser-clickpath", environment: "prod" }, timestamp: Date.now() }]; var dtResp = await fetch(DT_LOG_INGEST_URL, { method: "POST", headers: { "Authorization": "Api-Token " + DT_LOG_INGEST_TOKEN, "Content-Type": "application/json; charset=utf-8" }, body: JSON.stringify(logPayload) }); api.info("[DT_LOG_INGEST] status=" + dtResp.status); } catch (e) { api.error("[DT_LOG_INGEST] error=" + (e && e.message ? e.message : String(e))); } })();

I don't see any logs ingested with that format

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 13:15:34 GMT

Yeah, could work as a workaround.

The main problem is that the script defines this variable:

var RINA_API_URL = "https://{environmentid}.live.dynatrace.com/api/v2/logs/ingest";

but later it uses:

fetch(DT_LOG_INGEST_URL, ...)

DT_LOG_INGEST_URL is not defined, so the request will fail before anything is ingested.

There is also another issue: rinaResponseBody is used in the log payload, but it is not defined in the snippet. You first need to make the RINA API call with the token, read the response body, and only then send that result to Dynatrace Logs.

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 13:36:39 GMT

After fixing, I get this error:

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 13:38:58 GMT

Can I see the StackTrace complete, please?

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 13:41:57 GMT

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 13:50:25 GMT

How is your JS code now, after you fixed?

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 14:01:44 GMT

(async function() { // 1) Leer token RINA var rinaToken = localStorage.getItem("rina_token") || ""; if (!rinaToken) { api.error("[RINA] Token not found"); return; } // 2) Llamada a la API de RINA var RINA_API_URL = "https://rinaes01.portal.ss/eessiRest/PendingMessages?date=2026-05-05"; var rinaResponseBody = ""; try { var rinaResp = await fetch(RINA_API_URL, { method: "GET", headers: { "Authorization": "Bearer " + rinaToken, "Content-Type": "application/json" } }); rinaResponseBody = await rinaResp.text(); api.info("[RINA] API status=" + rinaResp.status); } catch (e) { api.error("[RINA] API error=" + (e && e.message ? e.message : String(e))); return; }

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 14:02:11 GMT

// 3) Ingestar el RESULTADO de la API en Dynatrace Logs var DT_LOG_INGEST_URL = "https://{environmentid}.live.dynatrace.com/api/v2/logs/ingest"; var DT_LOG_INGEST_TOKEN = "***"; try { var logPayload = [{ content: rinaResponseBody, attributes: { source: "synthetic-rina", api: "PendingMessages", synthetic: "browser-clickpath", environment: "prod" }, timestamp: Date.now() }]; var dtResp = await fetch(DT_LOG_INGEST_URL, { method: "POST", headers: { "Authorization": "Api-Token " + DT_LOG_INGEST_TOKEN, "Content-Type": "application/json; charset=utf-8" }, body: JSON.stringify(logPayload) }); api.info("[DT_LOG_INGEST] status=" + dtResp.status); } catch (e) { api.error("[DT_LOG_INGEST] error=" + (e && e.message ? e.message : String(e))); } })();

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 14:07:13 GMT

The code looks close, but I would check the exact error returned by the Synthetic execution first. Is it Failed to fetch, 401, 403, 400, or only the stack frame with Object.fail?

Since this runs inside a Synthetic browser clickpath, the call to the Dynatrce Log Ingest API is executed from the browser context. This means it can be blocked by CORS or browser security restrictions, even if the token and payload are correct.

Can you also log the response body from the Log Ingest call?

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 14:21:05 GMT

Where can I see the response logged with api.info("[DT_LOG_INGEST] response body=" + dtRespBody); ?

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 14:23:27 GMT

In the Synthetic monitor execution details. Open the Synthetic monitor, then go to the latest execution result or failed execution. In the execution details, open the specific step where the custom JavaScript runs. The messages written with api.info() should appear in the step logs/details for that execution.

If nothing appears, it may mean the script failed before reaching that line, or that the fetch() call failed before a response was returned. In that case, add an api.info() right before the fetch() and keep the catch block with api.error() to confirm where it stops.

Re: Obtain synthetic variable via workflow

elenaperez — Tue, 05 May 2026 14:33:45 GMT

I added the api.info() before the fetch and don't see anything

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 14:54:39 GMT

Try using api.startAsyncSyntheticEvent() at the beginning of the JavaScript step and api.finish() at the end of every success/error path. Here is the doc

Re: Obtain synthetic variable via workflow

MaximilianoML — Tue, 05 May 2026 14:55:08 GMT

Like this code:

api.startAsyncSyntheticEvent(); (async function () { try { var rinaToken = localStorage.getItem("rina_token") || ""; if (!rinaToken) { api.error("[RINA] Token not found"); api.finish(); return; } var RINA_API_URL = "https://{environmentid}.live.dynatrace.com/api/v2/logs/ingest"; var DT_LOG_INGEST_TOKEN = "***"; var logPayload = [{ content: rinaResponseBody, loglevel: "INFO", "log.source": "synthetic-rina", "rina.api": "PendingMessages", "synthetic.type": "browser-clickpath", environment: "prod", "rina.status_code": String(rinaResp.status), timestamp: Date.now() }]; var dtResp = await fetch(DT_LOG_INGEST_URL, { method: "POST", headers: { "Authorization": "Api-Token " + DT_LOG_INGEST_TOKEN, "Content-Type": "application/json; charset=utf-8" }, body: JSON.stringify(logPayload) }); var dtRespBody = await dtResp.text(); api.info("[DT_LOG_INGEST] status=" + dtResp.status + " body=" + dtRespBody); api.finish(); } catch (e) { api.error("[SCRIPT] error=" + (e && e.message ? e.message : String(e))); api.finish(); } })();