Short answer: You can get link click metrics in Bitly by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Bitly Get Link Click Metrics 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 |
|---|---|---|---|
Bitlink bitlink | string | Required | The short link without https:// |
Time Unit unit | options | Optional | Time Unit. Options: Day, Week, Month |
Number of Units units | number | Optional | e.g. 7 days, 4 weeks |
{"bitlink": "bit.ly/abc123","unit": "{{trigger.unit}}","units": "{{trigger.units}}"}
{"link_clicks": [{"date": "2026-04-11T00:00:00Z","clicks": 42},{"date": "2026-04-10T00:00:00Z","clicks": 38}]}
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.