Connect Frontro Live to Zapier

Frontro Live for Zapier lets channel owners and administrators start automated workflows when recordings, users, marketing consent, purchases, subscriptions, gifts, tips, or registrations change in Frontro.

Connect

In Zapier, create a Zap and choose Frontro Live.
Choose a trigger and select Sign in.
On Frontro, choose a channel where you are an owner or administrator and approve the requested access.
Return to Zapier, test the trigger, map its fields into the next step, and publish the Zap.

Frontro uses OAuth. You do not need to paste a webhook URL, access token, client secret, or private key. The connection label includes the Frontro Live channel that granted access.

If Frontro Live is not available to your channel yet, contact Frontro Support.

Supported triggers

Trigger	Runs when
Recording Completed	A Frontro Live recording is ready for an automation.
User Signed Up	A user completes signup on the connected channel.
User Deleted	A user is deleted or tombstoned on the connected channel.
User Subscribed to Email Marketing	A user's committed email-marketing preference changes to subscribed.
User Unsubscribed from Email Marketing	A user's committed email-marketing preference changes to unsubscribed.
User Subscribed to SMS Marketing	A user's committed SMS-marketing preference changes to subscribed.
User Unsubscribed from SMS Marketing	A user's committed SMS-marketing preference changes to unsubscribed.
One-Time Purchase Completed	An authoritative one-time purchase completes.
Subscription Started	A subscription purchase starts.
Subscription Cancelled	A subscription is cancelled.
Gift or Tip Completed	A gift or tip purchase completes.
Registration Completed	A user completes a Frontro Live registration.

The Complete Recording Transcription action completes the Frontro delivery associated with an imported Otter recording.

Map fields safely

Every trigger includes these common fields:

Field	Meaning
`eventId`	Stable event identifier and idempotency key.
`eventType`	The Frontro event name.
`occurredAt`	When the business event occurred.
`channelId`	The Frontro channel that owns the event.
`schemaVersion`	The event contract version.

Use eventId to upsert or deduplicate data in a destination that could otherwise create the same record more than once. Do not deduplicate on names, email addresses, timestamps, or Zap run IDs.

Money fields ending in Minor are integer minor units. For USD, 2500 means $25.00.

Older events that were already queued when a new optional field shipped can omit that field. Treat optional contact, name, and recording metadata as nullable.

See the Zapier API and event reference for scopes, endpoints, payload fields, and errors.

Otter transcription

Use Recording Completed as the trigger, then map its recording URL and import name into Otter. When the Otter recording is ready, use Complete Recording Transcription with values from the same workflow:

Map Transcription Completion URL from the Frontro recording event.
Map Otter Recording ID from the preceding Otter step.
Set the status to COMPLETED or FAILED.
Map the Otter transcript URL when the status is COMPLETED.

The completion URL is unique to one Frontro delivery. Do not type it, store it as a reusable constant, or construct it from an event ID.

Troubleshooting

I cannot connect my account

Confirm that you are an owner or administrator of an eligible Frontro channel. If access changed after the connection was created, disconnect and reconnect it.

A trigger has no sample

Perform the matching action with a disposable test user or test transaction, then test the trigger again. Do not use a real customer's deletion, consent, or purchase as test data.

A destination received the same event twice

Compare eventId. Configure the destination to upsert or deduplicate on that value before replaying a Frontro delivery. A Zap retry can repeat an HTTP request even though it represents the same business event.

An Otter completion failed

Remap the delivery-specific completion URL from the same Recording Completed run. Never reconstruct the callback URL manually.

I need Frontro Support

Email support@frontro.com or use the Blaze support control in Frontro Creator. Include the Zap run timestamp, trigger name, and eventId. Do not include passwords, OAuth tokens, unrelated customer data, or payment credentials.

Disconnect

Disconnect in both products:

Open App connections in Zapier, select Frontro Live, and disconnect the account. Zapier disables dependent Zaps and removes its stored connection.
In Frontro Creator, open Settings → Integrations → Zapier and disconnect the grant for the same channel. Frontro then revokes the grant and removes its REST Hook subscriptions.

Do not consider the authorization revoked until Frontro Creator no longer shows the connected grant. Removing only the Zapier App Connection does not revoke Frontro's server-side grant.

Disconnecting does not erase prior Zap History or data already copied into another app. Remove that data separately when required.

Privacy and deletion

User lifecycle events can contain names, email addresses, phone numbers, roles, and marketing-consent state so downstream systems can identify the correct person and honor consent or deletion changes.

Limit access to Zap History and connected destinations.
Avoid copying contact data into logs or notification messages.
Do not use a marketing subscription event as proof of consent for a different channel.
When user.deleted arrives, remove the matching person from systems that no longer have a lawful reason to retain the data.
Frontro placeholder email addresses are not emitted.

For Frontro's general support and privacy resources, see Support and your channel's account settings.