Change a shared link's destination with TaskVegas redirects

Keep a stable link

Create a TaskVegas redirect and share its returned public URL. Later, update the destination while retaining that link. This is useful for an event page, rotating resource, or document whose publishing location may change after people have received the original link.

Understand what the link manages

TaskVegas manages redirects under its own public domain. It does not edit an external website's server rules or move its content. Anyone with an enabled public redirect URL can follow it, so the link should lead to information appropriate for that audience.

Approve inspection and changes separately

Sign in to the intended workspace. Grant redirects:read for listing records and redirects:write for creating, updating, or deleting them. No provider API key is required. Review the exact destination before asking the assistant to make a change.

Prepare a reviewed change

Use a short descriptive slug and a destination you control or are authorized to share.

Illustrative prompt: Create a redirect titled Product guide with slug product-guide, pointing to https://example.com/guide. Show me the saved public URL and destination. Later, update that same redirect only after I provide and approve its replacement destination.

Create, inspect, and update

Start with list_redirects to avoid duplicates. Use create_redirect with slug, title, and destination. Save the returned publicUrl. Before updating, inspect the current record, then call update_redirect for the exact slug. Open the public link and confirm its final destination.

Retain an understandable record

A change report should show what remained stable and what changed.

Illustrative result: product-guide remains the shared TaskVegas link. Previous destination: /guide. New destination: /guide-v2. Enabled: true. The actual public URL must come from the saved record, not from an invented workspace identifier.

Follow the saved link

Check the complete hostname and path, test the enabled link, and confirm that it leads to the intended content. A successful save proves the record changed; it does not prove that the destination page is available or appropriate.

Recover from common errors

If the slug already exists, inspect it before choosing another. If a concurrent change causes a conflict, refresh before retrying. Restore a mistaken destination with an update, or set enabled to false. Delete only when you intend to remove the record.

Use supported destinations

Slugs contain 3–64 lowercase letters, numbers, and hyphens; titles contain 1–120 characters. Destinations require public HTTPS without credentials and cannot point back to TaskVegas. The current beta supports up to 100 redirect records per workspace.

Test before sharing widely

Create one low-impact redirect, confirm its destination, and practice disabling or restoring it. Keep the record's public URL handy so future changes target the same link.

Related capabilities and workflows

• Connection and consent guide
• Open your workspace

Sources and editorial record

Reviewed against TaskVegas implementation base 93577921b1f10c7a0c20418999184795137810ff. Editorial evidence date: 2026-10-10.

Prepared by the TaskVegas editorial team with AI assistance; checked against the reviewed adapter contracts. Examples are illustrative unless a dated live evidence reference is explicitly supplied. No professional credentials are implied.

• TaskVegas workspace