Connect Linkly to HTTP / Webhook

Create a new short link via POST /api/v1/link. See the documentation.

Permanently delete a short link via DELETE /api/v1/workspace/{workspace_id}/links/{id}. The short URL will return 404 for new visitors. See the documentation.

Fetch a single short link via GET /api/v1/link/{id}, with full metadata including click counts, custom domain, and redirect rules. See the documentation.

List all custom domains in your workspace via GET /api/v1/workspace/{workspace_id}/domains. See the documentation.

Retrieves available options for the Link ID field.

List all short links in your workspace via GET /api/v1/workspace/{workspace_id}/list_links, with click counts and metadata. See the documentation.

List all workspaces the API key has access to via GET /api/v1/workspaces. Useful for finding the workspace ID required for API requests. See the documentation.

Update an existing short link via POST /api/v1/link (with id) — change its destination URL, slug, name, or custom domain without breaking the existing short URL. See the documentation.

Send an HTTP request using any method and URL. Optionally configure query string parameters, headers, and basic auth.

Send an HTTP GET request to any URL. Optionally configure query string parameters, headers and basic auth.

Send an HTTP POST request to any URL. Optionally configure query string parameters, headers and basic auth.

Send an HTTP PUT request to any URL. Optionally configure query string parameters, headers and basic auth.

Use with an HTTP trigger that uses "Return a custom response from your workflow" as its HTTP Response

Require authorization for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".

Validate HMAC signature for incoming HTTP webhook requests. Make sure to configure the HTTP trigger to "Return a custom response from your workflow".