Short answer: Drop the "Dub → Create Dub Short Link" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Destination URL url | url | Required | A fully qualified URL (https://...) for the destination url. |
Custom Slug key | string | Optional | Leave empty for auto-generated |
Domain domain | string | Optional | Domain |
{"url": "e.g. https://example.com/path","key": "my-link","domain": "{{trigger.domain}}"}
{"id": "link123","key": "abc123","url": "https://example.com","clicks": 0,"domain": "dub.sh","shortLink": "https://dub.sh/abc123"}
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.
Triggered by anything in the catalog. Free tier available. No credit card.