How do first-party integrations (Cursor, Freshdesk) work?
TL;DR: Ballet includes first-party integrations beyond the MCP registry — notably Cursor (AI coding agent) and Freshdesk (support ticketing). These integrations support playbook steps, triggers, and credential management tailored to each provider.
Who this is for
Builders automating developer workflows (Cursor) or customer support workflows (Freshdesk).
What is the Cursor integration?
The Cursor integration lets playbooks interact with Cursor's AI coding agent — useful for automations that involve code generation, repository changes, or developer workflows. Configure it as a workspace connector and reference it in playbook steps.
What is the Freshdesk integration?
The Freshdesk integration connects Ballet to your Freshdesk helpdesk:
- Triggers — start playbooks when Freshdesk events occur (new tickets, updates).
- Steps — read and update tickets, contacts, and conversations.
- Credentials — store your Freshdesk API key as a workspace secret.
How do I set up Freshdesk?
- Add your Freshdesk API key in Secrets.
- Connect Freshdesk in Connectors or configure it as a playbook trigger in the Trigger panel.
- Build or run a playbook that reacts to Freshdesk events.
How is this different from MCP connectors?
First-party integrations are built and maintained by the Ballet team with tailored UX — trigger providers, credential docs, and step helpers. MCP connectors use the generic MCP protocol for any compatible server.