Short answer: You can get dub link analytics in Dub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Dub Get Dub Link Analytics action to a workflow, map its 2 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 |
|---|---|---|---|
Link ID linkId | string | Required | Link ID |
Interval interval | options | Optional | Interval. Options: 24 hours, 7 days, 30 days, 90 days |
{"linkId": "{{trigger.linkId}}","interval": "{{trigger.interval}}"}
{"leads": 50,"sales": 10,"clicks": 1500}
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.