Agency automation 24 of 25
How to ask for referrals from clients
To ask for referrals from clients, ask right after a documented win, when every invoice is paid and no complaint is open. Ask for one specific introduction, and write the short note the client can forward, so it takes them a minute. Most agencies ask at random, too late or never. A simple fix is to let plain rules in n8n watch for the right moment, let Claude draft the ask, and let you approve and send it. That way no client is asked twice in a few weeks, and no client is asked in the middle of a problem. This page shows the five checks that mark the right moment, why a person approves each ask, a sample email, and what to check before you build it. Referral fee and consent rules vary by country and are not covered here.
How the automation runs
To ask for referrals from clients, ask right after a documented win, when invoices are paid and no complaint is open. This automation finds that moment, drafts the ask with Claude, and sends it after you approve.
When is the right moment to ask a client for a referral?
The right moment is a happy, settled one. Here is the rule set our design uses. Every check must pass before an ask is drafted, and you can change any threshold.
| Check | Why it matters |
|---|---|
| Health score over your threshold | Rules score invoices paid on time, hours within budget, tasks delivered on time and a logged win. |
| A win logged in the last 14 days | The result is fresh, so the ask has a clear reason. |
| No open or overdue invoice | Never ask a client who owes you money. |
| No open complaint | Fix the problem first. |
| No ask in the last 180 days | Do not ask the same client again too soon. |
Why does a person approve each referral ask?
A referral ask is personal. It comes from you, to someone you work with, and it uses their goodwill. A badly timed or badly worded ask can cost more than it wins. So the automation never sends one by itself.
Plain rules decide who is asked and when. A score you can explain is better than one a model made up. Claude then writes the ask: a short note that names the win, requests one kind of introduction, and adds a three line blurb to forward. You read the draft in Gmail and press Approve. You know things the rules cannot see, such as a client having a hard week. If the draft is off, you decline it and nothing is sent.
How does the automation work, step by step?
The flow has five steps.
| Step | What happens | Who does it |
|---|---|---|
| 1. Score the client | A daily run adds points from invoices, hours, tasks and wins. | Rule |
| 2. Check the moment | All five checks pass, and the run is capped at 3 asks a week. | Rule |
| 3. Draft the ask | Claude writes the note and a forwardable blurb. | Claude AI |
| 4. Approve and send | You review the draft in Gmail. On Approve, n8n sends it. | Person |
| 5. Track and thank | A new HubSpot or Pipedrive deal with source Referral pings Slack. | App |
What do you need to build it?
You need n8n, a Claude API key, Stripe or another source of invoice status, Harvest for hours against budget, a Google Sheet for your wins log and referral ask log with dates, Gmail, Slack, and HubSpot or Pipedrive. Your CRM needs a lead source field that includes Referral and the referrer's name. Write down your ideal client in a few lines, so Claude can ask for the right kind of introduction. Zapier or Make can replace n8n, but we have not checked their connector coverage for these apps.
What should the referral ask say?
Name the win. Ask for one kind of introduction, such as a peer at a similar company. Give the client a three line blurb they can forward as it is. When a referred lead arrives, thank the client within a day.
Do not copy this selection logic into review requests. Choosing happy clients is fine for referrals but not allowed for reviews.
Referral fee and consent rules vary by country and are not covered here. A personal thank-you is often enough. If you plan to pay a fee, check the tax, contract and disclosure rules where you operate first. Also check this: we did not check HubSpot's built-in health score, so the design calculates its own score in n8n.
Our estimate for the build: 5 to 8 hours, based on the score rules and the client mapping across systems.
Sample email
Subject: One introduction, [First name]?
Hi [First name],
Congratulations on [the result we logged]. It was a pleasure to work on it with your team.
If you know one [type of person, for example a peer at a similar company] who has the same challenge, would you introduce us? Here is a short note you can forward as it is:
[Three line blurb]
Thank you either way. [Your name]
Frequently asked questions
When is the best time to ask a client for a referral?
Right after a documented win, when invoices are current and no issue is open. Our design also waits at least 180 days between asks to the same client.
Should I pay clients a referral fee?
You do not need to, and a personal thank-you is often enough. Fee and consent rules vary by country and are not covered here, so check the tax, contract and disclosure rules where you operate.
What if a client has an open complaint?
The ask does not go out. An open complaint or an unpaid invoice blocks the draft, so fix the problem first.
Does the AI send the referral email by itself?
No. Claude drafts the note and you approve it before n8n sends it. Plain rules decide who is asked and when.
Related automations
Review requests
Every client asked, rules followed
Client health checks
Weekly score, red flags first
Case study requests
Case study request and outline
Want these running in your agency?
Book a free call. We look at your process, pick the automations that fit and tell you what the build involves. There is no price on this page, because it depends on what you need.
Book your free call
Tell us a little about your agency. After you send it, you pick a time on the calendar.
Build times and time saved are estimates, tool plans and features change, so test every automation on your own plan before you rely on it.
