Zapier

Push Perly churn signals, expansion opportunities, and health score changes to 6,000+ apps through Zapier triggers and searches.

~3 minPushOAuth 2.0

Overview

The Zapier integration lets you route Perly signals to any of Zapier's 6,000+ connected apps. When a customer is at risk, an upsell opportunity emerges, or a health score changes, Zapier can trigger workflows in your ticketing system, email platform, project management tool, or anywhere else your team works.

This is an outbound-only integration. Perly pushes events to Zapier -- it does not pull data from it.

Zapier

PUSH

Perly

triggers

customer search

Available triggers

The Perly Zapier app provides 5 triggers and 1 search action:

↓ PULL

↑ PUSH

New Expansion Signal
Customer At Risk
Health Score Changed
Upsell Opportunity Detected
Billing Retry Failed

Trigger details

New Expansion Signal -- fires when Perly detects a customer approaching usage limits (seat count, API calls, storage) or exhibiting growth patterns. The payload includes the signal type, current usage, limit, and customer details.

Customer At Risk -- fires when a customer's risk level crosses a threshold you define (e.g., moving from medium to high). Includes the previous and new risk levels, top contributing signals, and suggested actions.

Health Score Changed -- fires whenever a customer's health score changes by more than a configurable delta (default: 10 points). Includes the old score, new score, direction, and contributing factors.

Upsell Opportunity Detected -- fires when Perly identifies a customer likely to benefit from a higher tier or add-on, based on usage patterns and engagement signals. Includes the opportunity type, confidence score, and recommended plan.

Billing Retry Failed -- fires when a customer's payment fails after all retry attempts are exhausted. Includes the failure reason, amount, and number of retry attempts.

Search action

Find Customer -- look up a Perly customer by their Perly ID, external ID, or email address. Returns the customer profile, current health score, risk level, and linked integrations. Useful as a mid-Zap step to enrich data from other triggers.

Connecting Zapier

1
Install the Perly app
Search for "Perly" in the Zapier app directory and add it to your Zapier account.
2
Click Connect
When creating a Zap with a Perly trigger, Zapier will prompt you to connect your Perly account.
3
Log in with your Perly credentials
Enter your Perly email and password in the OAuth popup.
4
Select your workspace
If you belong to multiple Perly workspaces, choose the one you want to connect.
Done -- connection is active
Your Perly account is now linked. You can use any Perly trigger or search action in your Zaps.

Example Zap recipes

Trigger	Action
Customer At Risk	Create Jira ticket for CS team
Health Score Changed	Update row in Google Sheets tracker
New Expansion Signal	Send Slack DM to account manager
Upsell Opportunity	Create deal in HubSpot
Billing Retry Failed	Send recovery email via Mailchimp

Payload format

All triggers send a JSON payload with a consistent 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"
}

Additional fields vary by trigger type. See the Perly API reference for full payload schemas.