Integrate iPaaS.com with Klaviyo to synchronize customer profiles and order activity, keeping profile records aligned in both directions and pushing order events into Klaviyo for marketing.
How to Connect
To connect Klaviyo with iPaaS.com, you can use either OAuth or an API Key. Follow the steps below to gather the required credentials and configure the integration.
Prerequisites
Before setting up the Klaviyo integration in iPaaS.com, ensure you have the following:
A Klaviyo account with access to the Settings area, so you can either authorize the OAuth connection or generate a private API key.
The Klaviyo API URL:
https://a.klaviyo.comOne of the following authentication credentials:
OAuth: Authorize iPaaS.com directly through the Klaviyo account authorization flow. No credential is entered manually; iPaaS.com stores and refreshes the access token for you.
API Key: A private API key generated in the Klaviyo dashboard.
For details on Klaviyo authentication, see the Klaviyo developer documentation at https://developers.klaviyo.com/en/docs/authenticate_api_requests.
Configuration Details
Each value you provide when configuring the subscription:
API URL: The base address for the Klaviyo API. Enter
https://a.klaviyo.com.API Key: A private API key created in the Klaviyo dashboard, used when you authenticate with an API key instead of OAuth. Example:
pk_xxxxxxxxxxxxxxxxxxxxxxxxxx.API Revision: The Klaviyo API revision date the integration sends with each request. Leave it blank to use the default revision, or enter a specific revision date when you need to target a particular Klaviyo API version. Example:
2023-10-15.Generate Events (TRUE/FALSE): Controls whether the integration creates Klaviyo events (such as order activity) when records are synchronized. Enter
TRUEto enable event creation orFALSEto disable it.
Configure Subscription Settings
Navigate to the Klaviyo subscription settings in iPaaS.com and provide the following information:
Field | Description | Required | Example |
Name | A unique name for the subscription. | Yes | Klaviyo Integration |
Version | The integration version to use. | Yes | v1.0 |
API Url | Base URL for the Klaviyo API. | Yes | |
API Key | Private API key used for API-key authentication. Leave blank when authenticating with OAuth. | No | pk_xxxxxxxxxxxxxxxxxxxxxxxxxx |
API Revision | Klaviyo API revision date sent with each request. When left blank, the integration uses the default revision 2023-10-15. | No | 2023-10-15 |
Generate Events (TRUE/FALSE) | Determines whether the integration creates Klaviyo events when records are synchronized. Set to TRUE to enable event creation or FALSE to disable it. | No | TRUE |
Authentication Methods
Method 1: OAuth Authentication
Open the Klaviyo subscription in iPaaS.com and click the Authenticate button in the top toolbar.
If prompted by Klaviyo, click Continue to proceed.
On the permissions page, click Allow to authorize iPaaS.com.
iPaaS.com will confirm a successful connection.
Refresh the subscription settings, and an Access Token and Refresh Token will now be visible. iPaaS.com uses these tokens to authenticate each request and refreshes the access token automatically when it expires.
Method 2: API Key Authentication
Log in to the Klaviyo Dashboard.
Navigate to Settings > Account > API Keys.
Click Create Private API Key.
Provide a name for the key.
Ensure all scope permissions are selected.
Click Create and copy the generated API key.
Enter the API Key in the Klaviyo subscription settings in iPaaS.com.
Save the subscription to finalize the connection.
OAuth Removal
To unlink the integration from Klaviyo:
Navigate to Profile > Integrations in the Klaviyo dashboard.
Use the three-dot menu on the right to select Remove Integration.
Confirm removal when prompted.
Initialization Support
Currently, initialization is not supported for Klaviyo in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
Throttling
Throttling ensures that Klaviyo's API isn't overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
While the throttling fields are required, the values are pre-populated by the integration settings. For more details, refer to Subscription Configuration – Edit.