The Zapier integration lets your workspace send data into Limitlytics from forms, automations, CRMs, call-booking tools, and other systems without losing auditability.

What Zapier can do

Limitlytics Zapier v1 supports:

• Find Lead -- look up an existing lead by email and/or phone
• Create Lead -- create a new lead in Limitlytics
• Update Lead Status -- move an existing lead to a new status
• Submit Report Data -- submit report values for any supported data field
• Lead Status Updated trigger -- send lead status changes from Limitlytics back to Zapier

Connecting Zapier

To connect Zapier:

1. Open Settings > Integrations > Zapier
2. Start the Zapier connection flow from Zapier
3. Sign in to Limitlytics
4. Choose the workspace Zapier should access
5. Approve the connection

Important: Each Zapier connection is tied to exactly one workspace. If you manage multiple workspaces, connect each one separately.

Only admins can authorize Zapier.

Safe write rules

Limitlytics applies a few safety rules to protect data quality:

• Every inbound Zapier write is stored with an external event ID
• Lead status updates must target a specific Lead UUID
• Report submissions must be tied to a specific team member and report date
• Duplicate create-lead requests are not created again when a matching lead already exists
• Unsupported status metadata is rejected instead of being stored loosely

These rules are designed to keep Limitlytics as the system of record.

Action setup tips

When you configure a Zapier action for Limitlytics:

• Member and offer inputs are shown as dropdowns based on the connected workspace and pass UUID values behind the scenes
• Lead, transition, report submission, workspace, user, offer, connection, subscription, and Zapier event IDs exposed by the integration are UUIDs
• Data field inputs stay key-based and continue to use the stable data field key
• Create Lead soft-stops when the email and/or phone already match an existing lead, so the Zap does not keep creating duplicates
• Update Lead Status only shows the extra fields that apply to the selected status
• Update Lead Status treats a repeated move to the lead's current status as a successful no-op
• Submit Report Data accepts a date or timestamp, then resolves the final report date before saving
• Actionable setup or validation problems still fail and should be fixed in the Zap

Customer transitions and invoicing

When Update Lead Status moves a lead to Customer, Zapier can drive the same billing flow as the app:

• Deal value and Transaction are required
• Offer stays optional, but should be mapped when you know which offer was sold
• First invoice date is supported when you want the first invoice draft to use a specific billing date
• Installments are supported for payment plans

If Transaction is set to a payment plan, make sure Installments is also mapped.

External event IDs

For the strongest duplicate protection, map a stable immutable event ID from the upstream system into External event ID.

If you leave External event ID blank, Limitlytics generates a best-effort fallback from the Zap action payload. This is convenient for simple setups, but identical payloads can collapse into the same event.

Report dates and timezones

For Submit Report Data, use Report date or timestamp like this:

• Use a plain date such as 2026-04-24 when you already know the reporting day
• Map a timestamp from a previous Zap step when the reporting day should be derived automatically

By default, Limitlytics uses the selected member timezone to turn a timestamp into the final report date. Use Report timezone override only when you need a different IANA timezone for that conversion.

Report field values

Report field values must be whole numbers. Positive and negative integers are supported.

Submit Report Data lets you choose how values are saved for the same member, report date, and data field:

• Add to existing value -- increment the current stored value
• Overwrite existing value -- replace the current stored value

The action defaults to Add to existing value.

Event history

The Settings > Integrations > Zapier page keeps a full history of Zapier activity for the workspace.

The page includes:

• An always-visible Active connections table
• An Event history table for inbound and outbound Zapier events

Workspace admins can open Details on an event to review the high-level effects of that Zapier activity without digging through technical payload data.

For each event, admins can review:

• Direction -- inbound or outbound
• Type -- lead creation, status transition, report submission, or outbound hook delivery
• Status -- applied, failed, undone, or undo blocked
• Which connection handled the event
• When the event was logged and processed

Some applied events can show that no changes were made. This means Limitlytics accepted the request safely but found the requested end state was already true.

This makes it easy to see what happened and when it happened.

Retry failed events

If an inbound Zapier write fails, admins can retry it from Settings > Integrations > Zapier.

Retrying reprocesses the saved payload through the same safety checks and business logic as the original request.

Undoing Zapier events

Admins can undo eligible inbound Zapier events from Settings > Integrations > Zapier.

Undo is conservative on purpose:

• A lead create can only be undone if that lead has not been changed since Zapier created it
• A lead status update can only be undone if it is still the latest relevant transition and no newer dependent data would be damaged
• A report submission can only be undone if the affected report values still match the values Zapier wrote

If Limitlytics detects newer dependent changes, the event is marked as undo blocked and the reason is shown in the event log.

Revoking a connection

Revoking a Zapier connection immediately:

• Marks the connection as revoked
• Revokes its OAuth tokens
• Revokes its outbound hook subscriptions

Use this if a Zap should stop sending or receiving data for the workspace.