LostChurn Docs

LostChurn's Zapier integration lets you automate workflows between LostChurn and thousands of other apps. Trigger Zaps when recoveries succeed, payments fail, or campaigns complete — and take actions like sending Slack messages, updating spreadsheets, or creating tickets.

Prerequisites

A Zapier account (Free plan or above)
A LostChurn account with an API key (generate one at Settings > API Keys)

Getting Started

1. Find LostChurn on Zapier

Log in to your Zapier account.
Go to My Apps and click Add Connection.
Search for LostChurn and select it.
Enter your LostChurn API key when prompted. You can find or create an API key at Settings > API Keys in your LostChurn dashboard.
Click Yes, Continue to authorize.

2. Create Your First Zap

Click Create Zap in the Zapier dashboard.
Choose LostChurn as the trigger app.
Select a trigger event (e.g., Recovery Succeeded).
Connect your LostChurn account if not already connected.
Test the trigger to pull in sample data.
Add an action step (e.g., send a Slack message, add a Google Sheets row).
Turn on your Zap.

Available Triggers

Triggers fire automatically when events occur in LostChurn.

Trigger	Description	Fires When
Recovery Succeeded	A failed payment was successfully recovered	A retry attempt succeeds and the invoice is paid
Recovery Failed	A recovery attempt failed	A retry attempt returns a decline
Recovery Exhausted	All recovery attempts have been used	The recovery campaign reaches its final step without success
Payment Failed	A new failed payment was received	A webhook from your payment processor reports a failed charge
Campaign Completed	A recovery campaign finished	All steps in a campaign have been executed
Customer Created	A new customer was added	A new customer record is created from a webhook event

Trigger Data

Each trigger includes relevant data fields you can use in your Zap actions:

Recovery Succeeded example fields:

recovery_id — Unique recovery identifier
customer_email — Customer's email address
customer_name — Customer's name
amount — Recovered payment amount (in cents)
currency — Payment currency (e.g., usd)
decline_code — Original decline reason
retry_count — Number of retry attempts
recovered_at — Timestamp of successful recovery

Available Actions

Actions let other apps trigger operations in LostChurn.

Action	Description
Create Recovery Note	Add a note to an existing recovery
Pause Recovery	Pause an active recovery campaign for a customer
Resume Recovery	Resume a paused recovery campaign
Update Customer	Update customer metadata (tags, notes)

Available Searches

Searches let you look up existing data in LostChurn.

Search	Description
Find Customer	Look up a customer by email address
Find Recovery	Look up a recovery by ID or customer email
Get Recovery Stats	Get recovery statistics for a date range

Pre-Built Zap Templates

Get started quickly with these popular templates:

Recovery Notifications

Recovery Succeeded → Slack Message — Post a celebratory message to your team channel when a payment is recovered
Recovery Exhausted → Email — Notify your CS team when a recovery campaign fails so they can follow up manually

Data Tracking

Recovery Succeeded → Google Sheets Row — Log every successful recovery to a spreadsheet for reporting
Payment Failed → Airtable Record — Track all failed payments in Airtable with decline codes and amounts

CRM Updates

Recovery Succeeded → HubSpot Deal — Create a deal in HubSpot when a recovery succeeds (alternative to the native HubSpot integration)
Customer Created → Salesforce Contact — Add new LostChurn customers to Salesforce

Ticketing

Recovery Exhausted → Zendesk Ticket — Create a support ticket for manual follow-up when automated recovery fails
Payment Failed → Jira Issue — Track payment failures as Jira issues for engineering review

Authentication

LostChurn uses API key authentication with Zapier. Your API key is sent as a Bearer token in the Authorization header:

Authorization: Bearer lc_live_xxxxxxxxxxxxxxxxxxxx

API Key Permissions

Zapier requires an API key with the following scopes:

webhooks:read — subscribe to event triggers
webhooks:write — manage webhook subscriptions
recoveries:read — access recovery data for triggers and searches
customers:read — access customer data for triggers and searches
customers:write — update customer data for actions

You can create a scoped API key at Settings > API Keys with only the permissions Zapier needs.

How It Works

Behind the scenes, LostChurn's Zapier integration uses REST Hooks:

When you turn on a Zap, Zapier calls LostChurn's API to create a webhook endpoint subscribed to the selected event type.
When the event occurs, LostChurn delivers the payload to Zapier's webhook URL.
When you turn off the Zap, Zapier calls LostChurn to delete the webhook subscription.

This means triggers are instant (no polling delay) and efficient (no unnecessary API calls).

Rate Limits

Zapier actions and searches are subject to LostChurn's standard API rate limits:

Plan	Rate Limit
Engine	60 requests/minute
Recovery	120 requests/minute
Command	300 requests/minute

Troubleshooting

Trigger not firing

Verify your Zap is turned on
Check that the API key used by Zapier is still active at Settings > API Keys
Ensure the event type actually occurred (e.g., a recovery must succeed, not just start)
Check Settings > Webhooks for delivery failures

Authentication error

Generate a new API key at Settings > API Keys and reconnect in Zapier
Ensure the API key has the required scopes

Duplicate triggers

Zapier deduplicates events by recovery_id. If you see duplicates, check if you have multiple Zaps subscribing to the same event.

Next Steps

n8n Integration — open-source alternative to Zapier
Outbound Webhooks — build fully custom integrations
API Keys — manage API keys and scopes

Zapier Integration