Zapier

Zapier talks to the same REST API as your own scripts. You need a Growth or Ultimate workspace and an API token from Integrations → Zapier (or API — it is the same token).

Connect the app

1. In Zapier, add the Letlink connection and paste the API token when asked.
2. Zapier calls GET /api/v1/auth/me to verify it.
3. If the test fails with 403, the workspace plan does not include the API yet — upgrade to Growth.

Trigger: a link is visited

This is a REST Hook on event link_visited. When you turn the Zap on, Zapier POSTs to /api/v1/hooks/subscribe with its Catch URL. Each recorded click is then POSTed in the webhook payload shape (see Webhooks). While you are mapping fields, Zapier may also call GET /api/v1/visits to pull sample rows — that endpoint returns the last 50 clicks in the same shape.

Useful fields in the Zap: link_shortcode, link_destination_url, visitor_device_type, visitor_browser, visitor_referrer, visitor_variation, utm_source, utm_campaign, instagram_username.

Action: create a link

Maps to POST /api/v1/links. You can pass type, destination, short_code, title, domain, and the smart-type fields (ios_url, android_url, and so on). Free-plan smart types and over-cap workspaces return an error into the Zap's run log.

Operational notes

• Regenerating the token in Letlink breaks the Zapier connection until you paste the new value.
• Turning a Zap off should unsubscribe the hook. If a Catch URL is left behind, delete it under Integrations → Webhooks.
• High-traffic links will produce one Zap run per recorded click. Filter in Zapier (for example only visitor_variation = qr) rather than recording a second short code.