Lesson 6 of 7 · 6 min

Building a multi-step drip

Generate a multi-step drip as a set of full emails, and know you still have to send them from your own tool.

How a drip is built

Raise the Emails ruler above 1 and the run becomes a timed drip. The ruler goes to 20, but the drip renderer caps at 12, so asking for 20 gives you 12. Three to seven steps is the usual range.

A drip is not one prompt stretched thin across a week. One cheap planning pass lays out the arc first and gives each step its own subject, preheader, angle, and delay. Then every step is written by the same full renderer a single email gets, a few at a time. The viewer stacks the finished emails on a Day N rail so you can read the sequence in order.

Because each step is a full render, a drip costs close to one email times the number of steps, plus the single planning pass. The Generate button shows the count before you commit, so a five-step drip reads Generate 5.

The honest limit on sending

Here is the part to be careful with. A drip you generate is a stack of finished letters with dates written on the envelopes. Pinnora writes the letters and dates them, but nobody is standing at the mailbox dropping one in each week. There is no engine that sends step one, waits, and then sends step two to a list on its own.

To actually run the drip, take the finished steps somewhere that can automate timing: paste each step into your email platform's automation, or send them by hand. Inside Email Studio you can send a single email as a broadcast now or on a schedule, but that sends one message, not a self-running sequence. Do not plan around automated drip sending inside Pinnora, because it is not wired.

Reference

Keep going