Nimriz

Automation integrations

Automate branded link workflows across your stack.

Turn link creation, clicks, and QR scans into connected workflows. Use dedicated Nimriz triggers, actions, modules, and nodes in Zapier, Make, or n8n to create links, update them, find them, and pass events onward.

Compare automation appsStart for free
  • Event-driven triggers
  • Link actions
  • Search and lookup steps

How it works

From a Nimriz signal to the next step.

Start from Nimriz or add a Nimriz operation inside a workflow that begins somewhere else.

  1. 01

    Start from a real event

    Use link creation, link updates, clicks, and QR scans to begin a workflow. Available event coverage depends on the automation app you choose.

  2. 02

    Work with one event model

    Nimriz uses one event model across connection paths, so event names and core fields stay familiar while each app or destination formats the payload for its own contract.

  3. 03

    Create, update, or find

    Add branded link actions and lookup steps inside the same workflow that already connects your campaign, CRM, and reporting tools.

Compare workflow builders

Choose the automation model that fits your team.

All three connect Nimriz events with link operations. The main differences are where the workflow runs, which modules are included, and how your team connects the workspace.

Read integration overview
Comparison of Nimriz integrations for Zapier, Make, and n8n
Compare
Zapier
Make
n8n
Good fit forNo-code automation, CRM updates, Team notificationsMarketing operations, Reporting workflows, CRM enrichmentSelf-hosted automation, Data sync, Operational alerts
Starts fromLink created, Link clicked, QR scannedLink created, Link clicked, QR scannedLink created, Link clicked, QR scanned
Building blocks4 instant triggers, 5 actions, 4 searches3 instant triggers, 3 actions, 1 searches6 trigger node events, 7 operations node
First setup stepSearch for Nimriz in the Zapier App Directory and add it to a Zap.Ask for an invitation to the Nimriz custom app through the setup docs.Add the n8n-nodes-nimriz community node to your n8n instance.
Access and runtimeAvailable in the Zapier App Directory; connect with Nimriz sign-in or a workspace API keyCustom app access is granted by invitation; request it through the setup docsCommunity node on npm (n8n-nodes-nimriz); connect with Nimriz OAuth2 or a workspace API key

Automation apps

Explore each workflow path in detail.

Review the modules, setup path, and operating model before opening the full integration page.

Automation and webhooks

Nimriz for Zapier

The Nimriz Zapier app uses instant webhook triggers, not polling, so Zaps fire the moment a link is created, clicked, or scanned. Click and scan triggers exclude bot traffic before your Zap ever runs, which keeps task usage and downstream noise under control.

Instant triggersLink actionsSearch steps

Included building blocks

Instant triggers

  • Link created
  • Link updated
  • Link clicked (bot traffic excluded)
  • QR code scanned (bot traffic excluded)

Actions

  • Create short link
  • Update link slug
  • Update link destination
  • Update link expiration
  • Remove link password

Searches

  • Find link
  • List recent links
  • Check slug availability
  • Get link analytics

Why it fits

Instant triggers, bots excluded

Triggers are delivered over webhooks the moment events happen, and click and QR scan triggers filter bot traffic by default. Zaps react to real visitors instead of burning tasks on crawler noise.

Actions and searches, not just triggers

Create short links, update slugs, destinations, and expirations, and look up links or analytics mid-Zap. Nimriz behaves like a full participant in your workflow, not a read-only event source.

One event model everywhere

The Zapier app uses the same event catalog and payload format as Nimriz webhooks and destinations, so a workflow you prototype in Zapier can graduate to a direct integration without remapping fields.

At a glance

Trigger model
Instant webhook-based triggers; no polling delays
Triggers
Link created, link updated, clicks, QR scans
Actions
Create link, update slug, update destination, update expiration, remove password
Searches
Find link, list recent links, check slug availability, get link analytics

Setup path

Four steps from connection to an active workflow.

View Zapier integrationSetup guide
  1. 01

    Find the app

    Search for Nimriz in the Zapier App Directory and add it to a Zap.

  2. 02

    Connect your workspace

    Sign in with Nimriz, or authenticate with a workspace API key.

  3. 03

    Pick a trigger or action

    Start a Zap from an instant Nimriz trigger or use link actions inside an existing Zap.

  4. 04

    Test and turn on

    Run the built-in Zap test with live sample data, then publish.

Automation and webhooks

Nimriz for Make

The Nimriz app for Make pairs instant webhook triggers with link management modules, so marketing operations scenarios can react to real campaign activity and create or update branded links in the same canvas. Click and scan triggers exclude bot traffic before a scenario starts.

Webhook triggersLink modulesScenario automation

Included building blocks

Instant triggers

  • Watch new links
  • Watch link clicks (bot traffic excluded)
  • Watch QR scans (bot traffic excluded)

Actions

  • Create short link
  • Update link slug
  • Update link destination

Searches

  • Find a link

Why it fits

Instant scenario starts

Watch modules receive events over webhooks the moment they happen. Click and QR scan watches filter bot traffic by default, so scenarios run on real visitor activity.

Manage links inside scenarios

Create short links and update slugs or destinations as scenario steps, so campaign link operations live next to the rest of your automation.

Same payloads as the rest of Nimriz

The Make app shares the event catalog and payload format used by Nimriz webhooks and destinations, so field references stay consistent across your tooling.

At a glance

Trigger model
Instant webhook-based watch modules; no polling
Triggers
Watch new links, watch link clicks, watch QR scans
Actions
Create short link, update link slug, update link destination
Searches
Find a link by short URL or domain and short code

Setup path

Four steps from connection to an active workflow.

View Make integrationSetup guide
  1. 01

    Request access

    Ask for an invitation to the Nimriz custom app through the setup docs.

  2. 02

    Connect your workspace

    Authenticate the app with your workspace API key.

  3. 03

    Build the scenario

    Start from a watch module or add link modules to an existing scenario.

  4. 04

    Run once and schedule

    Use Run once with live data to verify the flow, then enable scheduling.

Automation and webhooks

Nimriz for n8n

Teams that self-host their automation should not have to give that up to automate link operations. The Nimriz community node works on n8n Cloud and self-hosted instances alike, with a trigger node for link activity and an operations node for creating, finding, and updating links.

Webhook triggersEvent payloadsWorkflow automation

Included building blocks

Trigger node events

  • Link created
  • Link updated
  • Link availability updated
  • Domain verification updated
  • Link clicked (bot traffic excluded)
  • QR code scanned (bot traffic excluded)

Operations node

  • Create link
  • Find link
  • Get link
  • List recent links
  • Update slug
  • Update destination
  • Check slug availability

Why it fits

Self-hosted friendly

The community node runs wherever your n8n runs. Keep automation on your own infrastructure while still reacting to link, QR, and domain events in real time.

Trigger node plus operations node

React to link created, updated, availability, domain verification, click, and scan events, and manage links with create, find, get, list, and update operations in the same workflow.

Bot-filtered click events

Click and QR scan triggers exclude bot traffic by default, so workflows act on genuine visitor activity instead of crawler noise.

At a glance

Runs on
n8n Cloud and self-hosted n8n instances
Trigger node
Link created, updated, availability, domain verification, clicks, QR scans
Operations node
Create, find, get, list, update slug, update destination, check slug availability
Payloads
Same signed event envelope used by Nimriz webhooks

Setup path

Four steps from connection to an active workflow.

View n8n integrationSetup guide
  1. 01

    Install the node

    Add the n8n-nodes-nimriz community node to your n8n instance.

  2. 02

    Connect credentials

    Sign in with Nimriz OAuth2, or authenticate with a workspace API key.

  3. 03

    Choose events

    Select the link, click, QR scan, or operations events that should start the workflow.

  4. 04

    Build and activate

    Start from the trigger node or add operations to an existing workflow, test, then activate.

Workflow ideas

Build around the work your team already runs.

Start from a Nimriz event or place a Nimriz operation in the middle of a larger workflow.

01

Create campaign links from incoming work

Turn form responses, spreadsheet rows, or another workflow step into branded links, then pass the resulting short URL to the next app.

02

React to clicks and QR scans

Start follow-up, routing, or notification steps from click and QR activity after bot traffic has been excluded.

03

Connect CRM and reporting workflows

Use link events and lookup steps in CRM updates, reporting scenarios, data syncs, and analytics checks.

04

Keep automation on your infrastructure

Run the Nimriz community node on n8n Cloud or a self-hosted n8n instance when your team needs control over the workflow runtime.

Operational confidence

Details that matter after a workflow is active.

Event-driven starts

Zapier and Make receive supported triggers over webhooks instead of polling. n8n uses a dedicated trigger node for supported link, domain, click, and scan events.

Bot-filtered activity

Every listed click and QR scan trigger excludes bot traffic by default, so downstream steps can focus on real visitor activity.

Familiar event fields

Automation apps use the Nimriz event catalog and familiar core fields. Each app, destination, and webhook still formats deliveries for its own contract.

Developer alternative

Handle lifecycle events in your own backend.

Manage webhook endpoints, signed deliveries, retries, replay paths, and event schemas using the docs. Use lifecycle webhooks for signed link and domain events. For click and QR scan streams, use the Generic HTTP destination instead.

Explore developer WebhooksRead Webhook setup guideExplore Generic HTTP

Choose automation apps

Use dedicated Nimriz triggers, actions, modules, and nodes when a visual builder should coordinate the workflow.

Choose signed webhooks

Webhooks are infrastructure, so Nimriz treats them that way. Every delivery is signed with a timestamped HMAC SHA-256 signature, carries a stable event ID for deduplication, retries on failure with exponential backoff, and stays inspectable in a delivery history with manual replay.

Events
Link created, link updated, link availability updated, domain verification updated
Security
Timestamped HMAC SHA-256 signatures with self-serve secret rotation
Reliability
At-least-once delivery, six retries with exponential backoff, dead-letter on exhaustion
Operations
Delivery history, manual replay, test deliveries, endpoint pause and resume
Click streams
For click and scan event delivery, pair webhooks with the Generic HTTP destination

Build your workflow

Put branded link operations inside the tools your team already uses.

Start with Zapier, Make, or n8n, or review every Nimriz connection path from the integrations hub.

Start for freeExplore all integrations