n8n

n8n can sit in front of Letlink in three different ways. Webhooks and the REST API work on Growth and Ultimate. The MCP Client node needs Ultimate. The in-app page is Integrations → n8n; it shows your token and the MCP URL even if you already know the API docs.

1. Webhook trigger (Growth and Ultimate)

1. In n8n, add a Webhook node. Switch it to POST, production mode, and copy the production URL.
2. Paste that URL under Letlink Integrations → Webhooks.
3. Each recorded click arrives as the link_visited JSON object. Map link_shortcode, visitor_variation, utm_campaign, and so on into later nodes.

This is the right default for “when someone clicks, do X” — add a row to Airtable, notify a different Slack workspace, enrich the IP, open a ticket.

2. HTTP Request (Growth and Ultimate)

Use n8n's HTTP Request node against https://letl.ink/api/v1. Set header X-API-KEY to the token from Integrations → n8n. Typical calls:

• GET /auth/me — connection test.
• GET /links?domain=letl.ink — inventory plus click totals.
• POST /links with JSON — create a short link from a form, a CRM, or a spreadsheet row.
• GET /visits — pull the latest 50 clicks on a schedule if you do not want a push webhook.

GET https://letl.ink/api/v1/links?domain=letl.ink
Header: X-API-KEY = YOUR_TOKEN

3. MCP Client (Ultimate)

Point n8n's MCP Client node at Streamable HTTP https://letl.ink/mcp with Authorization: Bearer YOUR_TOKEN. The tools are the same ones Claude and ChatGPT see: workspace_summary, list_links, get_link, get_recent_visits, create_link. Use this when a workflow should *ask* the workspace questions rather than parse REST JSON itself.

Which to pick