Build Apps
- “Add a grid-connection tab to the opportunity page”
- “Build a custom journey block with IBAN validation”
- “Show live meter readings as a customer portal widget”
- “Call an external API from a flow action, keeping credentials server-side”
Agent Toolkit for epilot
Give your AI assistant the context to work with epilot
Focused workflows and live platform tools for configuring epilot, creating customer journeys, and building integrations. Choose the customer, administrator, or developer setup below.
Built on Agent Plugins 1.0Skills + MCPOpen source ready
CodexChatGPTClaude
Agent Toolkit for epilotSkills route the workOnly the relevant guidance is loaded
epilot MCPDocs, APIs, org state
Volt UI MCPComponents and tokens
Use cases
Describe the outcome. The agent does the epilot part.
Everyday tasks from real epilot projects — phrased the way you would ask for them, executed against current APIs and your organization's actual configuration.
Build integrations
- “Sync ERP orders into epilot entities with stable unique IDs”
- “Update the JSONata mapping for inbound meter readings”
- “Receive and verify epilot webhooks in an external service”
- “Import a small dataset of contacts without writing a script”
Configure epilot
- “Extend the contact schema after checking what depends on it”
- “Create products and prices for a new tariff”
- “Wire a journey submission to an automation that starts a workflow”
- “Find every journey and automation that uses an email template”
Why it matters
Platform expertise without a giant static prompt
The toolkit keeps stable decision guidance close to the agent and retrieves changing facts from their authoritative source when they are needed.
Start with the right architecture
Route a requirement to native configuration, an epilot App, or an external integration before writing code.
Build against current contracts
Discover epilot documentation, OpenAPI operations, entity schemas, and UI components instead of guessing from stale examples.
Understand the connected organization
Use the epilot MCP to inspect the organization's actual schemas and configuration when the task depends on live state.
Included workflows
One toolkit, six focused skills
Each skill stays focused on one workflow, so the agent loads only the epilot guidance that is relevant to the current task.
Understand epilot
Explains entities, relations, journeys, workflows, Apps, and the boundary between configuration and code.
Build an App
Scaffolds, extends, validates, and troubleshoots Apps with the current CLI, manifest schema, and App Bridge.
Connect a System
Designs reliable inbound, outbound, batch, webhook, and bidirectional connections without requiring an App.
Configure epilot
Sets up schemas, journeys, products, pricing, workflows, automations, portals, and permissions end to end.
Build a Journey
Creates and updates customer-facing forms and funnels, including steps, logic, copy, and design.
Design an Interface
Uses live Volt UI component and token guidance to make custom surfaces feel native to epilot.
Get started
Choose the setup for your team.
For everyday work, ask your administrator to enable epilot in ChatGPT. Administrators can import the toolkit for a desktop rollout. Developers can install it directly in Codex or Claude Code.
- Customer setup starts in the ChatGPT interface
- Each user connects their own epilot account
- Available actions follow your epilot permissions
Use epilot in ChatGPT
Start with your ChatGPT workspace administrator. The current setup uses the ChatGPT desktop app; you do not need to run a terminal command yourself.
- Ask your administrator to make the epilot plugin available to your team and prepare the desktop setup.
- Open Plugins in the ChatGPT desktop app, choose your workspace, and install epilot if it is not already installed.
- Connect your epilot account when prompted, then start a new chat and describe what you want to do.
A public ChatGPT directory installation link is not yet provided for this toolkit. For now, use the administrator-assisted desktop route. Your epilot permissions still determine which data and actions are available.
Start with an epilot App
Use the current CLI scaffold, then let the toolkit guide implementation, validation, and native UI design.