Zapier

Overview

What This Integration Does

Zapier connects thousands of apps together. With NotiLens, you can send important Zap events as instant notifications.

Start from Zapier and connect securely using NotiLens OAuth.

Why NotiLens

Why Use NotiLens with Zapier?

Turn any Zap into a real-time alert. Get notified only when your workflows matter, without checking Zapier task history.

Setup

How to Connect Zapier to NotiLens

1. Start from Zapier

1. Create or edit a Zap in Zapier.
2. Add an Action step.
3. Select NotiLens as the app.
4. Choose the desired NotiLens action.

2. Authenticate with NotiLens

1. You’ll be redirected to the NotiLens login page.
2. Log in with your NotiLens credentials.
3. Click Allow access on the "Zapier Integration wants access" screen.

3. Select or Create a Zapier Topic

1. Choose an existing Zapier topic, or create a new one for this Zap.
2. Click Continue.

Each topic helps you organise notifications from different Zaps or workflows.

4. Configure the Notification Message

1. Set the message content you want to send to NotiLens.
2. Map fields from your Zap trigger — order ID, status, user, amount, etc.
3. Fill in the fields below as needed:

5. (Optional) Add a catch-all error handler Zap

To get notified when any Zap fails, create a dedicated error-handler Zap:

1. Create a new Zap with Zapier Manager as the trigger app.
2. Select the Zap Error trigger event.
3. Add a Webhooks by Zapier → POST action.
4. Set the URL to your NotiLens webhook and map the error details:

{
  "title":      "Zap failed: {{zap_name}}",
  "message":    "Error on step {{error_step}}: {{error_message}}",
  "type":       "urgent",
  "event":      "zap.failed",
  "force_send": true,
  "meta": {
    "zap_id":    "{{zap_id}}",
    "error_type":"{{error_type}}"
  }
}

This single error-handler Zap catches failures from all your other Zaps automatically.

6. Test and Finish

1. Run the Zap test step.
2. Confirm the notification appears in the NotiLens app.
3. Turn on the Zap.

That’s it! Your Zapier workflow is now sending notifications to NotiLens.

Metrics & Anomaly Detection

Tracking Metrics for Anomaly Detection

Pass numeric values in the meta field alongside your event. NotiLens learns your baseline over time and alerts when values deviate — spikes, drops, or unusual patterns — without you needing to set manual thresholds.

Common metrics to track

Example — order Zap with metrics

Map these fields from your Zap trigger data in the Body of the Webhooks step:

{
  "title":   "Order received",
  "message": "Order #{{order_id}} placed by {{customer_name}}",
  "type":    "success",
  "event":   "order.placed",
  "meta": {
    "amount":        "{{order_total}}",
    "record_count":  "{{item_count}}",
    "duration_ms":   "{{zap_duration_ms}}"
  }
}

Example — payment failure tracking

{
  "title":   "Payment failed",
  "message": "{{customer_email}} — {{failure_reason}}",
  "type":    "urgent",
  "event":   "payment.failed",
  "force_send": true,
  "meta": {
    "amount":      "{{charge_amount}}",
    "error_count": "{{consecutive_failures}}",
    "retry_count": "{{attempt_number}}"
  }
}