Tell each user when the thing they asked for has shipped

The person who asked for something is the one most likely to come back when it exists, and the least likely to notice a changelog. The loop from their sentence to your entry is the part worth automating.

How do I automatically notify a user when their feature request ships?

Collect feedback with an email field. When you publish the changelog entry that answers it, link the feedback item to that entry (a select in the dashboard, linked_entry_id over the API, or update_feedback from an agent). Launch emails the person once, with their own words quoted and a link to the entry, and never again for that item.

01Collect feedback with an email

The feedback widget and POST /v1/feedback accept an optional email. Each item is classified (bug, feature request, praise, billing, support) and summarised on arrival, and routed to email, Slack, Linear or GitHub if you set a destination.

<script src="https://cdn.nordva.dev/v1/feedback.js" data-key="nv_pub_live_…" data-user-id="usr_123" async></script>

02Ship it, then link it

Publish the changelog entry as usual. On the feedback item, pick the entry under Shipped in, or over the API:

curl -X PATCH https://api.nordva.dev/v1/feedback/fb_01K5… \
  -H "Authorization: Bearer nv_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "linked_entry_id": "ce_01K5…" }'
# the item becomes "resolved" when that entry is published

03The email goes out once

A sweep every five minutes finds linked items whose entry is published and whose person has not been told. The email quotes their feedback, names the entry and links to it. The item is marked before sending, so a retry cannot send twice. Items without an email are linked for your records and nothing is sent.

04From an agent

“Which feedback items does this release answer?” With the MCP server connected, the agent reads the inbox with list_feedback, matches items to the entry, and calls update_feedback with linked_entry_id for each, after you confirm.

Questions

Can I edit the email?

Not yet. It is a short plain-text email in the project's name: their words quoted, the entry's title and its link, and nothing else. Builder's email templates cover the waitlist emails only.

What if several people asked for the same thing?

Link each item. One email per person, each quoting their own words. An agent can do the linking in one pass across the inbox.

Is the submitter's email ever sent to Slack or Linear?

No. Routing destinations and webhooks receive the classification and summary and a has_email flag. The address stays in Launch and is used only for this email and for your reply from the dashboard.