Step 1 - integrate mode

Inside the Alvas platform, you should go -> Emails.

Click on an email, and go into Texts.

Now you should turn on Integration Mode by flipping the "Integration Mode" switch:

Once the switch is flipped, your screen will display the URL, Headers, and Payload buttons. When you click a button, you copy the part

In the middle of your screen, you can see the URL, Headers, and Payload.

Step 2 - add HTTP Post and 10-minute wait in the Drip flow

You should now go to the tab with your Drip workflow, and open the editor.

For this example, I will show you a Browse Abandoned flow, yet it could be any other event-triggered flow.

 A simple flow would look something like this:

You should add a 10-minute wait above the email.

Then, add an HTTP Post Action above the 10-minute wait. 

Note you will need 1 HTTP Post for each email template that you want to personalize using Alvas.

Step 3 - Configuring the Drip HTTP Post

Inside the HTTP Post actions, you need to add five things:

• Endpoint URL

• Custom Data (Name + Value)

• Custom Headers (Name + Value)

Now you should go back into Alvas and click on the Endpoint URL - which will copy it to your clipboard.

Then you should insert it into the "Endpoint URL" inside Drip.

Similarly, you should do the same with the Headers.

Inside Alvas, click on the Header Name. 

First, click on "Add Custom Headers"

And insert the Name you copied from Alvas.

The Header Name will always be:

Then, go back into Alvas and copy the Header Value.

 And add it to the Drip HTTP Post.

Lastly, you should add Custom Data by clicking on "Add Custom Data".

Then go into Alvas and Copy the Payload Name.

Paste it into the Custom Data Name inside the Drip HTTP Post.

It will always be this text:

Heading back into Alvas, you should copy the Payload Value.

Which for Drip always will be:

 And add it to the Custom Data Value in the Drip HTTP Post.

Finally, click on Update Action.

Step 4 - Send test request to Alvas

You have now added the option for Drip to send over data to Alvas, and trigger the generation of a new email, with the HTTP Post.

This step will help you trigger the HTTP Post, so you can see what an AI-generated email for your brand will look like. 

Drip makes it a little tough to trigger the HTTP Post Action, compared to other platforms. We will need a real visitor on your website to enter the workflow and trigger the action. 

A person must enter the flow with the Trigger (e.g. Viewed Product) because the event data is sent over to Alvas. If you add them manually, Alvas does not receive information about the product they are looking at. 

Since we don't want to send an actual email to them yet, we're going to turn the flow on and turn the Email Action off. 

On the top right corner, you can turn the Drip workflow on.

You can flip the switch on the email, to turn it off.

Remove the 2-hour wait (temporarily)

In this example flow, we want the email to be sent 2 hours after the person triggered an event. Your flow might be different, but you should remove all waits that are before the HTTP Post Action so that a person triggers it instantly. 

In my case, I remove this: 

So the flow looks like this, where the HTTP Post Action is right after the Trigger. 

Wait for a person to trigger the Action

A hot tip is to just trigger the action yourself on your website. 

Typically it takes Drip a minute or two to register that a person has triggered the trigger and send the HTTP Post. 

Check for logs inside Alvas

Once a person has entered the flow and triggered the Action, you can see a log being generated inside Alvas -> Logs.

You might encounter errors in this step that will be displayed on the log. If you do that, feel free to reach out to villads@alvas.ai for help.

It typically takes between 3-4 minutes for Alvas to generate an email.

Next step: Prompting

After adding Alvas to your Klaviyo flow, you should start prompting Alvas, to make the emails have your desired message.

You can follow this guide.