Skip to main content
Apply to Beta
AppsLoops
[v1.0]

Loops

Sync clients to audiences and send transactional email from records

Connect Loops

What you can do

Connect your Loops API key to sync Clients into mailing lists and send transactional emails from the client record page. Each workspace uses its own Loops account — Kato never shares keys across workspaces.

Contact context before sending

Review the record and surrounding client work before triggering a supported message, reducing the chance that an email is separated from the relationship it affects.

Audience synchronization

Use record data to keep selected contacts aligned with Loops audiences instead of maintaining the same operational contact information manually in two places.

Transactional delivery through Loops

Keep Loops responsible for the email-delivery infrastructure while Kato supplies the workspace context and workflow that determine when a message should be sent.

Connect Loops

Paste a Loops API key from Settings → API. Kato validates it, encrypts it, and stores it for your workspace. On a Client record, sync the contact into selected mailing lists or pick a transactional template and send.

  1. 01In Loops, open Settings → API and generate a key (owners/admins only).
  2. 02In Kato, go to Settings → Integrations → Loops and paste the API key.
  3. 03Open a Client with an email, sync the contact into a mailing list, or send a transactional email from the record.

Made for your workflow

Lifecycle audiences

Sync eligible contacts from client or company records into the appropriate Loops audience when the workspace data represents their current relationship or stage.

Record-driven notifications

Send an approved transactional message from a record workflow and retain the operational context teammates need when they follow up later.

Consistent contact operations

Let account and operations teams manage the record while Loops remains the specialized system for audience membership and email delivery behavior.

Common questions

Does Kato become the email delivery provider?

No. Loops remains responsible for delivering supported email. Kato connects the recipient and message workflow to the records where teams manage their work.

How is Loops connected?

The workspace configures the integration with the appropriate Loops credentials. Those credentials should be scoped and managed according to the team's Loops account practices.

Can every record be synced automatically?

Synchronization depends on the workflow and record data the workspace chooses to use. Teams should define clear eligibility and consent rules before adding contacts to an audience.

Last updated Jul 17, 2026