# Integrations

> Camelus works with Vicunia, n8n, Zapier, Make, Linear, GitHub Issues, Slack, Discord, Polar, MCP clients and any HTTPS endpoint.

- [Vicunia](/integrations/vicunia) (Destination): Send a theme to the agent that builds it. Progress and the shipped link come back, and requesters get an email.
- [n8n](/integrations/n8n) (Destination): Receive theme events in an n8n workflow and do anything with them. Ready-made workflows for Linear and GitHub.
- [Zapier](/integrations/zapier) (Destination): Catch theme events with a Zapier webhook trigger and connect them to thousands of apps.
- [Make](/integrations/make) (Destination): Start a Make scenario when a theme is created, rises, or reaches your threshold.
- [Linear](/integrations/linear) (Recipe): Turn a theme into a Linear issue with an n8n recipe, and mark it shipped when the issue is done.
- [GitHub Issues](/integrations/github-issues) (Recipe): Open a GitHub issue for a theme, and close the loop when it's closed.
- [Slack](/integrations/slack) (Notifications): Post new and rising themes to a Slack channel, formatted for Slack.
- [Discord](/integrations/discord) (Notifications): Post theme events to a Discord channel through a channel webhook.
- [Polar](/integrations/polar) (Source): Plan and revenue on every requester, MRR affected per theme, and cancellation reasons as feedback.
- [MCP](/integrations/mcp) (Agents): Let Claude or any MCP client ask what your users want, with a read-only key.
- [Alpaga](/integrations/alpaga) (Agents): Use Alpaga's and Camelus's MCP servers together: what your traffic shows, next to what users say.