Vicunia integration: from user feedback to a shipped change
Last updated October 25, 2026
Vicunia is the agent in the same suite that turns a request into a reviewed, merged and deployed change. Connected to Camelus, it closes the whole loop: users ask, Camelus ranks, Vicunia builds, and everyone who asked hears that it shipped.
What it does
- Send to… → Vicunia on a theme creates a Vicunia request with the theme's title, summary, counts and a few representative quotes, without personal data.
- Vicunia reports back as the job moves: the theme goes to in progress while it's built and reviewed, and to shipped with the deploy link and the pull request once it's live.
- When it ships, Camelus drafts the email to the people who asked to hear back. You read it and send it, or let it go automatically.
- If Vicunia declines the request, the theme page asks whether to decline the theme too. Nothing changes on its own.
Set it up
- In Vicunia, create a webhook source and copy its URL and signing secret.
- In Camelus, open Settings → Destinations → Add destination, pick the Vicunia preset, and paste both.
- Send a theme. Its page shows the job under Linked work.
Step-by-step instructions, the status mapping and a local setup: Vicunia docs.