Actions6
Overview
This node integrates with a URL shortening service API, allowing users to create and manage shortened URLs programmatically. It is particularly useful for marketing campaigns, social media sharing, or any scenario where long URLs need to be condensed for easier distribution and tracking.
The "Encurtar URL" (Shorten URL) operation enables users to generate a short link from a long URL with various customization options such as custom aliases, password protection, expiration dates, and meta information for enhanced presentation. This can help improve click-through rates, track user engagement, and control access to the destination content.
Practical examples:
- Creating branded short links with custom domains and aliases for promotional emails.
- Protecting sensitive URLs with passwords before sharing.
- Setting expiration dates on temporary campaign links.
- Adding meta titles and descriptions to improve link previews on social platforms.
- Using geo-targeting or device-targeting to redirect users based on location or device type.
Properties
| Name | Meaning |
|---|---|
| URL Longa | The original long URL that you want to shorten. |
| Alias Personalizado | A custom alias for the shortened URL, allowing for branded or memorable links. |
| Tipo De Redirecionamento | The type of redirection for the shortened URL. Options: Direto (direct), Frame, Splash. |
| Senha | Password to protect the shortened URL, restricting access. |
| Domínio Personalizado | Custom domain to use for the shortened URL. Options include several predefined domains like https://demanda.sistema.chat, https://link.clientes.online, etc. |
| Data Para Expirar | Expiration date/time for the shortened URL in format like YYYY-MM-DD HH:mm:ss. After this date, the link may become inactive. |
| Título Meta | Meta title for the shortened URL, used in link previews. |
| Descrição Meta | Meta description for the shortened URL, enhancing preview snippets. |
| Imagem Meta | URL to an image (jpg or png) used in the meta preview of the shortened URL. |
| Geo Targeting | Geo-targeting data to customize redirection based on user location. |
| Device Targeting | Device-targeting data to customize redirection based on the user's device type. |
| Language Targeting | Language-targeting data to customize redirection based on the user's language settings. |
| Pixels | Array of pixel IDs for tracking purposes, enabling integration with analytics or advertising pixels. |
| Channel ID | Channel identifier associated with the shortened URL, possibly for campaign or source tracking. |
| Deep Link | JSON object containing app store links for deep linking, allowing mobile apps to open directly from the shortened URL. |
Output
The node outputs JSON data representing the result of the URL shortening operation. This typically includes details about the newly created short URL, such as:
- The shortened URL itself.
- Any custom alias applied.
- Metadata fields (title, description, image).
- Expiration date if set.
- Tracking and targeting configurations.
- Status or error messages if applicable.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the URL shortening service API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing long URL input will cause the operation to fail.
- Using a custom alias that already exists may result in an error.
- Incorrectly formatted expiration dates might be rejected by the API.
- Missing or invalid API credentials will prevent successful communication with the service.
Error messages:
- Errors related to authorization usually indicate misconfigured or missing API keys.
- Validation errors often point to incorrect property values (e.g., invalid URL format, unsupported characters in alias).
- Network or timeout errors suggest connectivity problems with the URL shortening service.
Resolutions:
- Verify all required properties are correctly filled.
- Ensure the API credential is properly set up in n8n.
- Check the format of dates and URLs.
- Avoid duplicate custom aliases or choose a different one.