Short answer: You can posthog capture event in PostHog by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the PostHog PostHog Capture Event action to a workflow, map its 3 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 Name event | string | Required | Event Name. Example: user_signed_up |
Distinct ID distinct_id | string | Required | Unique identifier for the user |
Properties properties | json | Optional | Properties. (JSON object). e.g. "{ "plan": "pro", "source": "organic" }" |
{"event": "e.g. user_signed_up","distinct_id": "{{trigger.distinct_id}}","properties": "{ \"plan\": \"pro\", \"source\": \"organic\" }"}
{"status": 1}
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.