Short answer: Drop the "Bitly → Shorten URL" 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 |
|---|---|---|---|
Long URL long_url | url | Required | Long URL. e.g. "https://example.com/very/long/url" |
Title title | string | Optional | Title. e.g. "My Link" |
Custom Domain domain | string | Optional | Custom Domain. e.g. "bit.ly" |
{"long_url": "https://example.com/very/long/url","title": "My Link","domain": "bit.ly"}
{"id": "bit.ly/abc123","link": "https://bit.ly/abc123","long_url": "https://example.com/very/long/url","created_at": "2026-04-11T10:00:00Z"}
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.