Before you connect
Confirm the two accounts you intend to connect and make sure you can authorize both.
- Use an administrator account in the correct Hark workspace.
- In Klaviyo, use an Owner, Admin, or Manager role. Klaviyo permits only these roles to authorize an app through its secure permission screen.
- Confirm which Klaviyo account belongs to this Hark workspace.
- Before launching customer outreach, configure the “From” email address and email-sending domain in Klaviyo. Create a test customer profile that uses an internal email address.
Connect the accounts
- Open Hark integrations and select the Klaviyo integration.
- Select Authorize Hark for Klaviyo.
- In Klaviyo, choose the intended account and review every requested permission.
- If the account and permissions are correct, select Allow. Klaviyo redirects you to Hark.
- Confirm that Hark reports a successful connection. If Hark displays a Klaviyo account name or ID, compare it with the value you noted earlier.
Launch a Core Moment
A Core Moment is an automated Hark feedback request sent after a customer event, such as placing or receiving an order.
- In Hark, open Core Moments and choose the moment you want to configure.
- Select the available Klaviyo trigger, then configure the delay, email template, subject line, and preview text.
- Preview the message and check the trigger and delay. Use an internal profile or test event before enabling customer sends.
- Save the Core Moment and review the resulting status in Hark and Klaviyo.
- Launch only after confirming the audience, trigger, message, and sending status.
Use Feedback Assist
Feedback Assist sends a targeted feedback request to a customer group you choose. Open Feedback Assist in Hark and follow the in-product setup to select that group and the Klaviyo delivery option.
Before continuing, confirm in the interface:
- Which Klaviyo list, segment, or campaign will be used
- Whether the message will be saved as a draft, scheduled for later, or sent immediately
- How to preview the message and send to an internal test profile
Verify the integration
- Confirm that Klaviyo remains connected in Hark.
- In Klaviyo, confirm that the expected Hark-created flow or campaign exists and has the intended status.
- Trigger one internal test event or send to an internal test profile.
- Confirm that Klaviyo delivers the request.
- Complete the request and confirm that its response appears in Hark.
Reconnect or disconnect
Reconnect
If Hark reports an expired or invalid connection, return to Hark integrations and select Authorize Hark for Klaviyo. Confirm the account and permissions again.
Disconnect safely
- In Klaviyo, pause Hark-created flows or set their messages to draft or manual status.
- Cancel or stop any scheduled Hark-created campaigns that should not send.
- Revoke Hark's access from your Klaviyo account settings.
- Confirm in Hark that the integration no longer displays as connected.
Troubleshoot
Klaviyo returns a 403 authorization error
Sign in with a Klaviyo Owner, Admin, or Manager role, confirm that you selected the correct account, and start authorization again.
Authorization was denied or canceled
Return to Hark integrations, start authorization again, and select Allow.
Hark is connected, but a Core Moment is not sending
In Klaviyo, confirm that the automated flow is active, the triggering customer event has arrived, the test customer can receive marketing email, and the configured delay has passed.
The wrong Klaviyo account was connected
Pause related sends, revoke the connection, then authorize again while signed in to the intended account.
Permissions and data access
Klaviyo's authorization screen is the source of truth for the permissions Hark requests. Review every permission before selecting Allow.
Depending on the Hark features enabled for your workspace, access may include:
- Account information
- Lists, profiles, and subscriptions
- Email templates and campaigns
- Automated flows and event or performance information (called metrics)
Hark does not ask you to copy a private API key, which is a secret account credential. Instead, it uses OAuth—Klaviyo's secure permission process for connected apps. Learn how it works in the Klaviyo OAuth documentation.