Short answer: You can splunk send event (hec) in Splunk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Splunk Splunk Send Event (HEC) action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Event Data event | json | Required | Event Data. (JSON object). e.g. "{ "message": "User logged in", "user": "john" }" |
Source source | string | Optional | Source. e.g. "my-app" |
Source Type sourcetype | string | Optional | Source Type. e.g. "_json" |
Index index | string | Optional | Index. e.g. "main" |
{"event": "{ \"message\": \"User logged in\", \"user\": \"john\" }","source": "my-app","sourcetype": "_json","index": "main"}
{"code": 0,"text": "Success"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.