Make

Overview

What This Integration Does

Make lets you build powerful automation scenarios across your apps. With NotiLens, you can send important scenario events as instant notifications.

Start from Make and connect securely using NotiLens authentication.

Why NotiLens

Why Use NotiLens with Make?

Get notified when your scenarios run, fail, or reach key steps. Stay informed without constantly checking Make scenario logs.

Setup

How to Connect Make to NotiLens

1. Start from Make

1. Create or open a Scenario in Make.
2. Add a new module.
3. Select NotiLens from the app list.
4. Choose the desired NotiLens action.

2. Authenticate with NotiLens

1. Click Add to create a new NotiLens connection.
2. You’ll be redirected to the NotiLens login page.
3. Log in with your NotiLens credentials.
4. Click Allow access on the "Make Integration wants access" screen.

3. Select or Create a Make Topic

1. Select an existing Make topic, or
2. Create a new topic for this scenario.
3. Continue to the next step.

Topics help organize notifications across different scenarios.

4. Configure the Notification Message

1. Define the notification title and message.
2. Map output fields from previous modules — order ID, status, user, amount, etc.
3. Fill in the fields below as needed:

5. (Optional) Add an error handler route

To catch scenario failures, add an error handler to any module:

1. Right-click the module you want to monitor and select Add error handler.
2. Choose Resume or Rollback depending on your scenario logic.
3. Add a NotiLens → Send Notification module (or HTTP → Make a request) in the error route.
4. Map the error details to the notification body:

{
  "title":      "Make scenario failed: {{scenario_name}}",
  "message":    "Module {{module_name}} error: {{error_message}}",
  "type":       "urgent",
  "event":      "scenario.failed",
  "force_send": true,
  "meta": {
    "scenario_id":   "{{scenario_id}}",
    "execution_id":  "{{execution_id}}",
    "error_type":    "{{error_type}}"
  }
}

Add this error route to each critical module to ensure failures are caught at the exact failing step.

6. Run and Test

1. Run the scenario once.
2. Confirm the notification appears in the NotiLens app.
3. Turn the scenario on.

You’re all set! Make will now send notifications to NotiLens whenever your scenario runs.

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 — e-commerce scenario with metrics

Map these fields from previous modules in the NotiLens body parameters:

{
  "title":   "Order processed",
  "message": "Order #{{order_id}} fulfilled for {{customer_name}}",
  "type":    "success",
  "event":   "order.fulfilled",
  "meta": {
    "amount":       "{{order_total}}",
    "record_count": "{{item_count}}",
    "duration_ms":  "{{scenario_duration}}"
  }
}

Example — data sync with error tracking

{
  "title":   "CRM sync completed",
  "message": "{{synced_count}} contacts updated, {{error_count}} failed",
  "type":    "success",
  "event":   "crm.sync",
  "meta": {
    "record_count":  "{{synced_count}}",
    "error_count":   "{{error_count}}",
    "items_skipped": "{{skipped_count}}",
    "api_latency_ms":"{{api_response_time}}"
  }
}