Klavio (Marketing Automation)

Klaviyo: Marketing Platform | Email, SMS & B2C CRM

Symbol Configs

• RunKlaviyoDaemon - True/False - turn the Klaviyo daemon on/off

• KlaviyoBatchSize - the number of records to send to Klaviyo in a single call (batch). The total number of records to import are broken up into batch size chunks

• KlaviyoErrorEmailRecipients - a comma separated list of email addresses to email Klaviyo errors to

• KlaviyoSuccessEmailRecipients - a comma separated list of email addresses to email Klaviyo successfully imported records to

• KlaviyoTestMaxRecords - used when API is set to test mode to limit the total number of records to import into Klaviyo

• KlaviyoLastSync - the last time Klaviyo was synchronised (updated by system)

Integration settings on Host Company

• Integration API : set to Klaviyo

• Mode: set to Test or Production (test mode will only send through a subset of records)

• Password is the Private API key as issued within Klaviyo

External Website Posting transactions directly to the system or asking for information

Where an external system would like to post transactions directly into our system they need on their server code to generate an EDI key and to pass this to our system along with client code and XML.

This key allows an external system to create a session and then pass XML to create transactions directly in the system.

SaaSplications screens communicate with the system using XML and the traffic exposes the XML format used by the system for all transactions.

However the EDI connection objects allowed to be submitted all require to be setup for each customer.

The process is as follows:

1. Identify the transaction the external system wants to create

2. View the current XML used by the existing screens to create that transaction.

   1. Where the system does not currently support the creation, new screens will be created to mimic the process for testing

   2. View the responses provided to determine if more information is required

3. Create any process required in the external system to create the XML that will be submitted

   1. Where this is different from our standard XML a converter can be created by you (before you submit) or by us (after you submit including any specific responses required)

4. Testing by drag and drop the xml onto screens specifically for testing xml import

5. SaaSplications will then enable your EDI connection to submit the working xml after creating a session.

   1. Note - only xml that has been reviewed and tested will result in any action in the system. All other xml will not even make it to the server.

6. Your system will then (1) establish a session (2) submit the XML and wait for a response (3) the session will be closed

This capability will allow any external system to (1) ask questions (2) create transactions. Examples include:

1. Create Sales Order

2. Create Payments

3. Create Customer

4. Change Order Status

5. Create invoice

6. Add booking

7. Respond with

   1. available stock

   2. Customer credit amount

   3. etc

Shopify

See Shopify Integration with SaaSplications