AvantGuard - PXL icon

AvantGuard - PXL

AvantGuard - PXL

Overview

This node allows you to update an existing short link managed by the AvantGuard PXL service. It is useful for modifying attributes of a short URL such as its route, destination URL, metadata (title, description, image, favicon), consent settings, click count, and timestamps. Typical use cases include correcting or changing the target URL of a short link, updating preview information for social sharing, or managing tracking data like clicks and consent preferences.

For example, if you have a short link pxl.to/mylink and want to change where it redirects or update its preview title, this node lets you do that programmatically within an n8n workflow.

Properties

Name Meaning
Id Unique identifier of the short link to update. This is a composite text of domain and route (e.g., pxl.to/mylink). Prepending https:// forms the full short link URL. Required to specify which short link to update.
Additional Body Fields Optional fields to update on the short link. These include:
- Route: The path segment of the short link.
- Destination: The URL where the short link redirects.
- Title: Text shown in link previews.
- Description: Text shown in link previews.
- Image: URL of image shown in previews.
- Favicon: URL of favicon shown in browser redirects.
- Consent: Boolean to request visitor consent before storing cookies.
- Clicks: Integer count of clicks.
- Created At: Date/time string when the link was created (UTC).
- Updated At: Date/time string of last update (UTC), including clicks updates.

Output

The node outputs JSON data representing the updated short link object returned from the API after the update operation. This typically includes all current properties of the short link such as id, route, destination, metadata, click counts, and timestamps.

There is no binary output.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard PXL API.
  • The node uses the base URL https://api.pxl.to/api for requests.
  • The user must configure the appropriate API authentication credentials in n8n prior to using this node.

Troubleshooting

  • Invalid Id: If the provided Id does not correspond to an existing short link, the API will likely return an error indicating the resource was not found. Verify the Id format and existence.
  • Invalid Field Values: Providing invalid URLs or improperly formatted dates in additional fields may cause validation errors. Ensure URLs are valid and date strings follow expected formats.
  • Authentication Errors: Missing or incorrect API credentials will result in authorization failures. Confirm the API key is correctly set up in n8n credentials.
  • Network Issues: Connectivity problems to api.pxl.to can cause request failures. Check network access and proxy settings if applicable.

Links and References

Discussion