← View All Guides
Drip logo
Integration Guide

How to Add Referral Links to Drip Broadcasts and Workflows

Drip’s Liquid reads GrowSurf fields, so one email can print a referral link and branch on referral count.

Want the full setup walkthrough?

Use these docs for exact setup steps, supported fields, and troubleshooting.

Once GrowSurf syncs into Drip, every person carries their referral link and progress as custom fields. Drip resolves them with Liquid, which is what lets a single broadcast say something different to a first-time reader and a repeat referrer.

The same syntax works in workflow emails, which is where most referral programs get their steady share volume.

Integration Steps

Check a person has the fields

The Drip integration card in GrowSurf
Drip lives in Program Editor > 4. Options > Integrations.

Open a synced person in Drip and confirm the GrowSurf custom fields carry values before you write against them.

Print the link where it is visible

Use {{ subscriber.grsf_share_url }} as both the href and the visible text, high in the email.

Branch on referral count

A Liquid if on {{ subscriber.grsf_total_referral_count }} separates people who have never shared from people already earning. The first group is larger and responds better to an invitation than to a progress report.

Move it into a workflow

A workflow email that fires a couple of weeks after signup keeps producing referrals long after a broadcast has stopped. Reward amounts and milestone copy stay in GrowSurf, so the offer can change without touching the workflow.

Code Snippets

The referral link

<p>Share your referral link:</p>
<a href="{{ subscriber.grsf_share_url }}">{{ subscriber.grsf_share_url }}</a>

One email, two messages

{% if subscriber.grsf_total_referral_count > 0 %}
  <p>You have {{ subscriber.grsf_total_referral_count }} referrals. {{ subscriber.grsf_next_milestone }}</p>
{% else %}
  <p>Share your link and earn your first reward.</p>
{% endif %}

A share button

<a href="https://twitter.com/intent/tweet?url={{ subscriber.grsf_share_url }}">Share on X</a>

Tips

Liquid renders empty, not broken

A typo in a field name produces a blank space and a clean send. Test as a real, synced person.

Condition on the count

{{ subscriber.grsf_next_milestone }} is empty on programs without milestone rewards, so it is a poor condition. The referral count is always populated.

URL-encode the message, not the tag

On share buttons, encode your own copy and leave the Liquid tag plain so Drip can substitute it.

FAQ

What Liquid object holds the referral fields?

subscriber, for example {{ subscriber.grsf_share_url }}.

Can workflows branch on referral count?

Yes. The counts are ordinary custom fields, so workflow conditions and Liquid both read them.

Which field should always be in the email?

The share URL.

Trusted by marketing and product teams that grow through customer, user, and partner referrals.