Zapier

Connect Nimriz to Zapier with OAuth or API-key auth, instant triggers, link actions, and search steps.

Nimriz has a native Zapier app that connects your workspace to thousands of downstream tools using instant triggers, link actions, and search steps.

Nimriz for Zapier is live in the Zapier App Directory. Connections support Sign in with Nimriz (OAuth) and workspace API keys. Existing API-key connections keep working.

Prerequisites

  • A Nimriz workspace on Professional plan or higher.
  • A Zapier account.

Connect Nimriz to Zapier

You can use the embedded Zapier templates and builder in the dashboard at IntegrationsAutomationZapier, or connect from Zapier directly.

  1. Find the Nimriz app in the Zapier App Directory.
  2. Click Connect.
  3. Choose Sign in with Nimriz, sign in, choose the workspace, and approve the requested scopes.
  4. To connect with a key instead, paste a workspace API key from IntegrationsDeveloperBackend API access.
  5. Zapier verifies the connection and labels it with your workspace name.

To move an existing Zap from API-key auth to OAuth, create a new Nimriz connection in Zapier, then update the Zap to use that connection. Nimriz does not change existing Zaps automatically.

Disconnect or reconnect

  • OAuth connection: revoke the Nimriz grant from your workspace principal list, then create a new Zapier connection when you want to reconnect.
  • API-key connection: revoke or rotate the workspace API key from IntegrationsDeveloperBackend API access, then update the Zapier connection with the new key.

OAuth connections request links:read, links:write, domains:read, analytics:read, webhooks:read, and webhooks:write.

Available triggers

All triggers are instant (REST Hook). Nimriz delivers events to Zapier in real time, not by polling.

TriggerEvent typeDescription
New Link Createdlink.createdA new short link is created in your workspace
Link Updatedlink.updatedA link's destination, slug, expiration, or redirect status changes
Link Clickedlink.clickedA short link is clicked (bot traffic excluded)
QR Code Scannedlink.qr_scannedA QR code is scanned (bot traffic excluded)

Available actions

ActionDescription
Create Short LinkCreates a new short link with optional custom slug, expiration, and redirect status
Update Link SlugChanges the slug on an existing link
Update Link DestinationChanges the destination URL on an existing link
Update Link ExpirationSets, changes, or removes link expiration
Remove Link PasswordRemoves password protection from a link

Available searches

SearchDescription
Find LinkLooks up a link by short URL or domain ID + short code
List Recent LinksReturns recently created links for the workspace
Check Slug AvailabilityChecks whether a slug is available on a domain
Get Link AnalyticsFetches click or QR scan analytics for a link

Example Zap: QR scan to Google Sheets

  1. Trigger: Nimriz > QR Code Scanned.
  2. Action: Google Sheets > Create Spreadsheet Row.
  3. Map data.domain_name, data.short_code, data.country, and data.device_category to sheet columns.

Every QR scan now logs a row with the scan location and device type.

Example Zap: New link to Slack

  1. Trigger: Nimriz > Link Created.
  2. Action: Slack > Send Channel Message.
  3. Use data.short_url and data.destination_host in the message body.

Payload format

Trigger payloads follow the standard Nimriz webhook envelope:

{
  "id": "evt_uuid",
  "type": "link.clicked",
  "api_version": "2026-03-30",
  "workspace_id": "ws_uuid",
  "data": {
    "url_id": "url_uuid",
    "domain_name": "go.brand.com",
    "short_code": "launch",
    "touch_type": "short_link_click",
    "country": "US",
    "device_category": "mobile",
    "utm_source": "twitter"
  }
}

Use fields inside data in your Zap action steps.

Related guides

Related next steps

Ready to test this setup?

Create an account to try the workflow, or compare plans when the setup needs higher limits, integrations, or team controls.