Loops.so
Keep lifecycle data in motion

Build Loops.so audience workflows that keep contact properties and lifecycle events aligned with your product. Send the approved events that drive your existing Loops email workflows. Maintain contact properties and mailing-list choices from verified customer data.

Yes. Start with a mission such as 'Build the onboarding event relay'. SPIRITT builds the application, source mappings, validation, and operations queue around the connected account. Track event submission and contact reconciliation in a durable workflow ledger.

For customer-tier alignment, SPIRITT finds each Loops.so contact by verified email or user ID and checks the available property definitions. It updates only confirmed matches with the approved HubSpot tier, then looks up the contact again to compare the saved value. Missing contacts and conflicting identities go to review instead of being silently created by the update operation.

Connect the companion apps your mission needs: Supabase to supply product milestones; HubSpot to sync customer context; PostHog to map lifecycle signals. SPIRITT coordinates the separate systems and verifies each handoff.

SPIRITT creates and updates contacts and properties, reads mailing lists and published transactional templates, and sends named events into existing Loops workflows. Template discovery is not direct transactional sending, and an accepted event is not proof of email delivery.

Open a SPIRITT workspace, connect Loops.so, and hand over a mission such as 'Build the onboarding event relay'. Name the target account or records, the outcome, and the companion apps involved. Set the approved scope for changes and customer-facing actions before the workflow runs.