# Deck Tasks & Automation: Put an agent to work with a prompt

> Tell Deck what to do on a site and what you want back. It runs the task on any website, even without an API, and returns JSON your product can use.

Source: https://deck.co/tasks-and-automation

Tasks & Automation

Tell Deck what to do on a site and what you want back. It runs the task on any website, even ones with no API, and returns the result in the format your product expects.

[Get Started](https://console.deck.co/)

[Talk to Sales](https://deck.co/contact)

## Write a task for any site

A task has two parts: a prompt that says what to do, and a schema that says what comes back. Deck runs it in a browser, signed in as your user, and returns JSON in the same structure every time, ready to use as-is.

*Diagram: a task has two parts, a prompt that says what to do and a schema that says what comes back. Deck runs it in a browser signed in as your user, working through each step on the site, and returns JSON that matches the schema to your product.*

## Sign in once, run many tasks

Logging in is often the slowest and most fragile part of a task. With Deck, you can run several tasks in the same session. An agent signs in once, downloads this month’s pay stubs, exports the payroll register, and adds a new hire, then logs out.

Fewer logins also means fewer MFA prompts for your users.

[Learn about sessions](https://docs.deck.co/concepts/sessions)

## Files, ready to use

Agents can also download files. When one grabs an invoice or a monthly report, Deck stores it so you can retrieve it whenever you need it. Scanned PDFs get run through OCR, so the numbers inside them end up in your schema. If the same invoice gets downloaded twice, you only get one copy back.

[Learn about file storage](https://docs.deck.co/guides/storage)

## Automations

Most tasks shouldn’t wait for someone to click a button. Set a task to run on a schedule, or trigger it through the API when something happens in your product, like a new customer signing up or a bill coming due. You can create workflows by chaining tasks together, so the output of one feeds the next.

### Triggers

Set a task to run on a schedule, like every weekday at 6am. Deck starts the runs for you each time and limits how many run at once.

[Learn about triggers](https://docs.deck.co/guides/triggers)

### Workflows

Chain tasks into steps that run in order. Each step can use the output of the one before it, and run only when a condition is met, like rebooking a reservation when the price drops and then emailing the guest the new total.

[Learn about workflows](https://docs.deck.co/guides/workflows)

## Describe it once, and let it run

Start building or talk to us about automating at scale.

[Get Started](https://console.deck.co/) · [Talk to Sales](https://deck.co/contact)

## More from Deck

- [Deck home](https://deck.co/)
- [Auth](https://deck.co/auth)
- [Browser Agents](https://deck.co/agents)
- [Observability](https://deck.co/observability)
- [Pricing](https://deck.co/pricing)
- [Security](https://deck.co/security)
- [Customers](https://deck.co/customers)

Docs: https://docs.deck.co · Site index for agents: https://deck.co/llms.txt