Private beta

Connect Looply to Zapier

Set up Looply’s private Zapier integration, authenticate a workspace token, and use the New Contact Created or Lead Replied REST Hook triggers.

Availability: this is a private, invite-only beta. The Looply app is not currently listed in the public Zapier App Marketplace. Features and trigger fields may change while the integration is validated.

Accept the private Zapier invite

Before you connect

An active Looply workspace and permission to change its integrations.
A Zapier account that can accept a private developer invite.
At least one recent contact if you want Zapier to load a sample record.

Setup

Open Looply and go to Settings, then Integrations, then Zapier.
Prepare the connection and copy the workspace-specific integration token.
Accept the private Zapier invite using the button above.
Create a Zap and choose Looply as the trigger app.
Paste the Looply integration token when Zapier asks you to authenticate.
Choose a trigger, test the sample, map fields, and publish your Zap.

Treat the integration token like a password. Rotating it in Looply invalidates the previous token, so reconnect affected Zaps with the new value. Disconnecting the integration stops active subscriptions.

Available triggers

New Contact Created

Runs once when a new Looply contact is created.

on_lead_created

Lead Replied

Runs when a tracked campaign lead receives a fresh reply.

on_lead_reply

Fields sent to Zapier

Values can be null when Looply does not have the corresponding contact or reply data. Reply-only fields are populated only for the Lead Replied trigger.

Group	Fields
Event	looply_event, looply_trigger_type, looply_sync_reason, occurred_at
Contact	looply_blog_id, looply_contact_id, email, first_name, last_name, full_name, phone
Company	company, job_title, location, industry
Web presence	website, company_url, linkedin_url
Qualification	source, intent, intent_keyword, total_score
Reply only	campaign_lead_id, campaign_id, replied_at

Delivery, duplicates, and limitations

Triggers use Zapier REST Hooks and deliver fresh events to active subscriptions.
Looply deduplicates its queue by Zap subscription and event key.
Network and destination behavior can still produce retries or duplicate downstream actions. Make important Zap actions idempotent using the contact ID, trigger type, and occurrence time.
Failed delivery information is retained for troubleshooting in the integration state.
The beta exposes two triggers only and is not a historical bulk-export tool.

Privacy and token safety

Looply sends the fields listed above to the HTTPS hook URL registered by Zapier. Review the destination app, mapped fields, and your own lawful basis before publishing a Zap. Never place the Looply integration token in a public document, spreadsheet, message, or Zap output field.

Troubleshooting

Zapier says the token is invalid

Copy the current workspace token again. If it was rotated, reconnect the Zapier account with the replacement token.

No sample is returned

Create or update an eligible contact, then test the trigger again. The sample endpoint uses the latest available workspace record.

Events stopped arriving

Confirm the Looply integration is active, the private invite was accepted, trigger delivery is enabled, and the Zap is published. If the problem continues, email support@joinlooply.com.

Last reviewed August 27, 2026.