Why use Deck
- Your users’ logins, handled safely. Credentials are stored in the Deck Credential Vault, never in your app. When a source asks for an MFA code, the agent asks your user through an interaction.
- Tasks in plain language. Describe what the agent should do and the output you want. Runs return structured JSON that matches your schema.
- Workflows and triggers. Chain tasks into workflows, and run tasks or workflows on a schedule across your users.
- Built-in observability. Watch runs live, and review screenshots and the agent’s reasoning afterward.
- Event-driven by default. Results are pushed to webhooks, queues, or any supported destination.
Get started
Quickstart
Create an agent, store credentials, and run your first task.
Concepts
Agents, sources, credentials, tasks, workflows, and triggers.
API reference
Endpoints, request formats, and response examples.
Guides
Building your auth flow
Collect and store user credentials in your application.
Verify credentials
Confirm credentials work before running other tasks.
Handling interactions
Respond to MFA prompts, security questions, and other mid-flow requests.
Build a workflow
Chain tasks, with later steps reading earlier outputs.
Automate runs
Schedule tasks and workflows across your credentials.
Storage & document extraction
Capture files from sources and extract structured data.
UI components
Auth Component
Drop-in UI to collect credentials and connect your users to sources.
Live View Component
Show your users a run you’ve already started, live.
Explore
How Deck works
Platform architecture, agent orchestration, and the execution model.
Events and destinations
Subscribe to events, configure destinations, and track deliveries.
Using the API
Authentication, pagination, idempotency, and error handling.
Build with AI
Ready-made context for building with AI coding agents.