How to Set Up Advocacy Request → Manager Approval + Coordination in n8n

Your customer success team just spotted a perfect advocacy candidate — a happy customer ready to give a testimonial, join a case study, or speak on a webinar. Then reality hits: the account manager needs to approve it first (nobody wants a customer double-tapped for asks), someone has to actually reach out to the customer, and the whole thing needs to land in HubSpot so marketing and sales can see it. Do this manually and 40% of nominations die in a Slack thread. This article shows you how to automate the entire path — nomination to manager approval to customer outreach to CRM logging — using a single n8n workflow.

The Problem: Advocacy Dies in the Handoffs

Advocacy is one of the highest-ROI motions in any B2B company. A single reference call closes deals faster than any ad. Yet most teams run it on tribal knowledge and good intentions, and it breaks at every handoff:

• No gate. A CSM nominates a customer without checking whether that account is mid-renewal, in an escalation, or already tapped twice this quarter. The account manager finds out after the ask is sent.
• Approval limbo. The nomination sits in a DM. The manager is in meetings, forgets, and the momentum — the customer's fresh enthusiasm — evaporates.
• Dropped coordination. Even when approved, nobody owns the next step. The customer never hears back, or hears back three weeks late.
• Invisible in the CRM. None of it lands in HubSpot, so you can't report on advocacy pipeline, tag reference-friendly accounts, or trigger follow-up sequences.

The core issue isn't effort — it's that the process spans three people and two systems with manual glue in between. Automation removes the glue.

The Solution: One Workflow, Three Stages

The Advocacy Request → Manager Approval + Coordination template models the whole flow as a state machine inside n8n:

1. Capture — a nomination comes in via a form (or an internal Slack/API trigger) with the customer, the advocacy type, and the nominating CSM.
2. Approve — the account manager receives an email with two one-click links: Approve or Decline. No login, no dashboard.
3. Coordinate — on approval, the customer is notified automatically and the record is written to HubSpot with the right properties and owner.

Because n8n waits on the manager's decision natively, there's no polling, no cron job checking a database. The workflow pauses, holds state, and resumes the instant the manager clicks. That single behavior is what makes this reliable.

Step-by-Step: Building It in n8n

Here's how the nodes fit together. If you install the template you get this pre-wired; if you're building it yourself, this is the skeleton.

1. Trigger the nomination. Use an n8n Form Trigger node as the entry point. Configure fields for customer_name, customer_email, advocacy_type (a dropdown: Testimonial / Case Study / Reference Call / Webinar), account_manager_email, and nominated_by. If your nominations originate elsewhere, swap this for a Webhook node so your CRM or Slack workflow can POST the payload directly.

2. Enrich and validate. Add a Set node to normalize the incoming data and build the links you'll need downstream. Optionally drop in a HubSpot node (operation: Get Contact) to pull the account owner and confirm the customer exists before you route anything for approval. An IF node then short-circuits bad data — missing email, unknown account — before a manager is ever bothered.

3. Send the approval request and wait. This is the heart of the template. Use n8n's Wait node set to On Webhook Call mode (the "resume URL" pattern). n8n generates a unique resume URL; you append a query parameter to distinguish the two outcomes:

• Approve link → {{$execution.resumeUrl}}?decision=approve
• Decline link → {{$execution.resumeUrl}}?decision=decline

Before the Wait node, place a Send Email node (SMTP or Gmail) addressed to the account manager. Build an HTML body with the nomination summary and two buttons wired to those URLs. Set the Wait node's timeout to something sane — 72 hours — so stale requests don't hang forever. When the manager clicks, execution resumes at the Wait node with the query parameter available in the incoming data.

4. Branch on the decision. A Switch node reads {{$json.query.decision}} and routes to one of three paths: approve, decline, or the timeout branch (fed from the Wait node's fallback output). Keep the three paths visually separate — it makes the workflow readable when you hand it to a teammate.

5. Coordinate the approved path. On approval, fan out:

• A second Send Email node notifies the customer (or the CSM to reach out, if you prefer a human touch on the outbound). Personalize with the advocacy type so the ask is specific.
• A HubSpot node (operation: Create or Update Contact, or Create Deal if you track advocacy as pipeline) writes the outcome. Set custom properties like advocacy_status = approved, advocacy_type, and advocacy_approved_date. Assign the owner so it shows up in the right rep's view.
• Optionally, a Slack node posts to a #customer-advocacy channel so the team sees momentum.

6. Handle decline and timeout gracefully. On decline, write advocacy_status = declined to HubSpot and notify the nominating CSM with the reason (add a comment field to the manager's decline link if you want structured feedback). On timeout, send the manager a reminder or escalate to their lead — silence shouldn't kill a good nomination.

The Benefits: What Changes on Day One

Once this is live, the difference is immediate and measurable:

• Zero nominations lost to inboxes. Every request is a live workflow execution with a state, not a message someone might scroll past.
• Manager approval in minutes, not weeks. One-click links from the phone during a meeting break beat any dashboard that requires a login.
• Guaranteed follow-through. Approval mechanically triggers customer outreach. There's no gap where "someone was supposed to reach out."
• Reportable advocacy pipeline. Because everything lands in HubSpot with structured properties, you can finally build a dashboard: nominations this quarter, approval rate, advocacy type mix, time-to-approval.
• An audit trail for free. Every n8n execution logs who nominated, who approved, and when — useful when legal or a customer asks how consent was obtained.

Common Pitfalls (and How to Avoid Them)

Resume URLs need a reachable host. The Wait node's webhook resume only works if your n8n instance is publicly reachable at the URL in WEBHOOK_URL. On self-hosted setups behind a firewall, set the WEBHOOK_URL environment variable to your public domain, or the approve/decline links will 404. Test this before you go live — it's the single most common failure.

Don't let executions hang forever. Always set a timeout on the Wait node. Without it, a manager who never clicks leaves an execution open indefinitely, which clutters your execution list and can hit instance limits over time.

Secure the resume links. The resume URL contains a unique execution ID, but treat it as a bearer token — anyone with the link can approve. Don't post it in public channels. If your advocacy program is sensitive, add a lightweight signed token check in a Function node after the Wait resumes.

Make HubSpot writes idempotent. Use Create or Update rather than Create so a re-run (or a double-click on the approve link) doesn't spawn duplicate contacts or deals. Key on email.

Handle the double-click. Managers sometimes click twice or forward the email. Once an execution resumes, the link is spent — but add a friendly response page (via a Respond to Webhook node) confirming "Decision recorded" so they aren't left staring at a blank screen and clicking again.

Rate-limit your email node. If nominations arrive in bursts (e.g., after a big customer win), batch or throttle the outbound so you don't trip your SMTP provider's sending limits.

Set this up once and advocacy stops being a thing you chase. Nominations flow in, managers approve from their phones, customers hear back the same day, and your CRM finally reflects the reference pipeline you've been building all along.

PRONTO PARA USAR

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 $79 →