Perly

Make (formerly Integromat)

Send Perly churn signals, expansion opportunities, and health score changes to Make scenarios via webhooks.

~2 minPushwebhook

Overview

The Make integration lets you route Perly events into Make scenarios using webhooks. When a customer's health score drops, a billing retry fails, or an expansion signal fires, Make receives the event and can trigger any downstream workflow -- CRM updates, email sequences, ticket creation, and more.

This is an outbound-only integration. Perly pushes events to Make via webhooks.

Make
PUSH
Perly
webhook events

Available events

Perly can send the following event types to your Make webhook:

↓ PULL
    ↑ PUSH
    • New Expansion Signal
    • Customer At Risk
    • Health Score Changed
    • Upsell Opportunity Detected
    • Billing Retry Failed

    You can choose which event types to forward when configuring the webhook in Perly. By default, all events are sent.

    Connecting Make

    No OAuth is required. The connection is established by pasting a Make webhook URL into Perly.

    1. 1
      Create a new scenario in Make
      Log in to Make and create a new scenario. Add a "Webhooks" module as the trigger and select "Custom webhook".
    2. 2
      Copy the webhook URL
      Make generates a unique webhook URL when you create the Custom webhook module. Copy this URL.
    3. 3
      Add the webhook in Perly
      In Perly, go to Settings > Integrations > Make. Paste the webhook URL and select which event types to forward.
    4. Done -- events flow automatically
      Perly sends a test event to verify the connection. Once confirmed, all selected events will be delivered to your Make scenario in real time.

    Setting up a scenario

    Once the webhook is connected, build your Make scenario like any other webhook-triggered workflow:

    1. The Webhooks module receives the Perly event payload.
    2. Add a Router module to branch logic based on event_type.
    3. Connect downstream modules (HTTP, email, CRM, Slack, etc.) to each branch.

    Example scenario: At-risk customer alert

    ModuleAction
    Webhook triggerReceives customer_at_risk event
    FilterOnly proceed if risk_level is high or critical
    SlackPost alert to #customer-success channel
    HubSpotCreate task for account owner
    Google SheetsLog the event in a tracking spreadsheet

    Payload format

    All events sent to Make follow this JSON structure:

    {
  "event_type": "customer_at_risk",
  "customer_id": "cust_abc123",
  "customer_name": "Acme Corp",
  "customer_email": "admin@acme.com",
  "health_score": 32,
  "risk_level": "high",
  "signals": ["login_frequency_drop", "payment_failed"],
  "timestamp": "2026-03-24T14:30:00Z"
}

    Make's Webhooks module automatically parses the JSON. You can map any field directly to downstream module inputs.

    Event filtering

    In Perly, you can filter which events reach your Make webhook:

    • By event type -- select specific triggers (e.g., only customer_at_risk and billing_retry_failed).
    • By risk level -- only send events when risk exceeds a threshold.
    • By health score delta -- only send health score changes above a minimum point swing.

    Configure filters in Settings > Integrations > Make > Event Filters.