Automate Advocacy Request → Manager Approval + Coordination in n8n — Step by Step
Your customer advocacy program is only as strong as your ability to act on nominations quickly. When advocacy requests arrive by email, Slack, or form — and then sit in someone's inbox waiting for app
Your customer advocacy program is only as strong as your ability to act on nominations quickly. When advocacy requests arrive by email, Slack, or form — and then sit in someone's inbox waiting for approval — momentum dies. The manager doesn't see it, the customer never gets contacted, and nothing lands in your CRM. This workflow fixes that loop entirely.
The Problem: Advocacy Nominations Fall Through the Cracks
Most advocacy programs run on manual handoffs. A CSM spots a happy customer and emails the advocacy manager. The manager approves verbally in a meeting. Someone remembers to reach out to the customer — three weeks later. By then, the window is gone.
The root issue isn't effort. It's structure. There's no single trigger point, no enforced approval step, no automatic notification to the customer, and nothing gets logged unless someone manually updates the CRM. You end up with a scattered mix of emails, spreadsheets, and HubSpot contacts that don't tell the same story.
For ops teams and technical founders managing advocacy at scale, this is a compounding problem. Every nomination that slips costs you a case study, a reference call, or a G2 review that would have closed your next deal.
The Solution: A Fully Automated Advocacy Approval Pipeline in n8n
The Advocacy Request → Manager Approval + Coordination workflow in n8n replaces the manual chain with a structured, automated pipeline. Here's what it does end-to-end:
- Captures the advocacy nomination from any input source (form, webhook, or internal tool)
- Routes an approval request to the relevant manager via email with inline approve/reject links
- On approval, automatically sends a personalized outreach email to the customer
- Logs the full interaction — nomination, decision, and outreach — directly into HubSpot
No human needs to touch a keyboard between nomination and customer notification. The manager gets a clean decision point. The customer gets a timely, personalized message. Your CRM stays current without manual entry.
Step-by-Step Setup in n8n
Below is the full build, node by node. This assumes you have n8n running (self-hosted or cloud), with HubSpot and SMTP credentials already configured.
Step 1 — Webhook Trigger (Webhook node)
Add a Webhook node as your entry point. Set the method to POST and copy the generated URL into your nomination form or internal tool. The payload should include at minimum: customer_name, customer_email, company, nominator_name, and advocacy_type (reference call, case study, review, etc.). If you're pulling nominations from a Typeform or Tally, use their native n8n nodes instead and map the fields in a Set node downstream.
Step 2 — Build the Approval Email (Set node + Send Email node)
Use a Set node to construct two URLs: one for approval and one for rejection. These should point back to a second Webhook in your workflow (or a lightweight endpoint) with a query parameter encoding the decision and a unique request ID. Example:
https://your-n8n.com/webhook/advocacy-decision?id={{ $json.request_id }}&action=approveThen wire this into a Send Email node (SMTP). Configure the To field dynamically based on the advocacy type or the nominator's team — use an If node upstream if different nominations route to different managers. The email body should include the customer name, company, reason for nomination, and the two clickable buttons (approve/reject) as plain anchor tags. Keep it short — managers approve faster when there's less to read.
Step 3 — Decision Webhook (Webhook node)
Add a second Webhook node to receive the manager's click. Extract the action and id query parameters. Use an If node to branch: one path for approve, one for reject. On the reject branch, log the decision to HubSpot and terminate. On the approve branch, continue to customer outreach.
Step 4 — Customer Notification (Send Email node)
On the approval branch, add another Send Email node targeting the customer's email address captured in Step 1. Personalize the subject and body using the stored fields. A good starting template: thank them for being a customer, explain what you're asking them to participate in (reference call, review, etc.), and include a clear CTA — a Calendly link, a review platform link, or a reply-to response. Avoid generic "we'd love to feature you" language; specificity converts better.
Step 5 — Log to HubSpot (HubSpot nodes)
Use the HubSpot node with the Create/Update Contact operation to upsert the customer contact using their email as the unique identifier. Then use a second HubSpot node to create a Note or Engagement on that contact, logging the full advocacy request: nomination date, nominator, advocacy type, manager decision, and outreach timestamp. If your HubSpot setup uses custom properties for advocacy tracking, map them here using the Additional Fields section in the node configuration.
Step 6 — Error Handling (Error Trigger node)
Add an Error Trigger node connected to a notification channel (Slack or email) so that any failure in the pipeline — invalid email, HubSpot rate limit, webhook timeout — gets surfaced immediately rather than silently dropped. Set it at the workflow level under Settings → Error Workflow.
Benefits You'll See Within the First Week
Zero-latency approvals. The manager gets the request the moment it's submitted and clicks approve from their inbox. No login required, no tool to open. Approval-to-outreach time drops from days to minutes.
Consistent customer experience. Every approved customer gets the same well-crafted email, not whatever the CSM had time to write that afternoon. This matters for conversion — customers who receive clear, timely asks are far more likely to say yes.
CRM hygiene without discipline. The workflow logs every decision to HubSpot automatically. Your advocacy pipeline in the CRM reflects reality, not what someone remembered to enter last Friday.
Audit trail by default. Because every step is logged — nomination received, approval decision, customer contacted — you can pull a full report of your advocacy pipeline at any point without chasing anyone for status updates.
Scales without headcount. Whether you're processing 5 nominations a month or 500, the workflow handles the same volume without additional coordination overhead. The bottleneck shifts from operations to strategy — which is where your team's time should go.
Common Pitfalls and How to Avoid Them
Using the same webhook URL for all decisions. If multiple nominations are in flight simultaneously, you need a way to correlate each manager's click to the right nomination. Generate a UUID when the nomination comes in, store it in a Set node, and pass it through every step. Without this, approvals can be misrouted when two requests are pending at the same time.
Not handling the reject branch. A common mistake is building only the approval path and letting rejections fall into a dead branch. Always log rejections to HubSpot with the reason (you can add a free-text field to the rejection link via a query parameter or a short follow-up form). This data tells you which nomination types managers consistently reject — valuable signal for qualifying nominations upstream.
Sending customer outreach too fast. If your manager approval webhook and the customer send email are tightly coupled with no delay, there's a risk the manager's click is processed before the original nomination data is fully available in memory (especially with large payloads). Add a Wait node set to 2–5 seconds between the decision webhook and the customer send step to avoid race conditions.
Generic customer emails. The biggest conversion killer is a customer email that reads like it was automated — because it was, but it shouldn't feel that way. Use every field captured in the nomination (customer name, company name, what they achieved with your product) to personalize the message. n8n's expression editor makes this straightforward: {{ $json.customer_name }} in any text field renders the value at execution time.
Not testing the approval link expiry. If a manager sits on an approval for a week and then clicks the link, does it still work? By default, yes — unless you've added expiry logic. Consider adding a timestamp to the approval payload and checking it in the decision webhook branch. If the request is older than X days, send a new nomination confirmation email rather than routing an outdated approval.
Skipping HubSpot deduplication. If the same customer gets nominated multiple times, using Create Contact instead of Create or Update Contact will generate duplicate records. Always use the upsert operation with email as the unique key, and check your HubSpot duplicate settings before going live.
Ja construimos isso pra voce
Nao comece do zero. O Advocacy Request → Manager Approval + Coordination e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.
Instalar por $49 →
