Let your customers connect to any web account in seconds.
San Francisco
Joined July 2025
- Tweets44
- Following49
- Followers125
- Likes26
Credentials Persistence is live in Deck.
Every login in an automated run is also a place it can stall on an MFA prompt, often the same one, run after run.
By default, every run starts from a clean browser and logs in fresh.
With credential persistence enabled, Deck saves the login state after a successful run and restores it on the next one. When the source honors that state, the run skips the login flow and the MFA prompt.
Deck.co retweeted
We integrated with @deck_agent to make importing from Substack effortless.
Writers can let an AI agent migrate their content without lifting a finger.
Launching this week.
Success metrics are now live in the Deck Console. Track success rate, task volume, credential creation, and errors, all in one view.
Filter by agent, task, source, or error type to dig into what's actually driving the numbers.
The Deck Console now includes an Agent Library: pre-built agent templates with ready-to-run tasks across categories like Energy & Utilities, Migration, Onboarding, and more.
Each task comes with a curated prompt, input and output schemas, and optional storage config. Browse the library in the console, or load templates straight from your terminal.
Evive Nutrition had the data, but accessing it was the real challenge.
Selling across 9 major retailers meant dealing with supplier portals, no APIs, 2FA, and bot detection that made automation nearly impossible.
So they plugged in Deck, and now every portal feeds their pipeline automatically.
9 portals automated. $250,000+ in manual costs avoided. Zero connector maintenance.
Rather than limiting tokenization to a fixed set of fields, you choose exactly which inputs get protected. Sensitive values like account numbers, personal identifiers, or payment information stay encrypted and never appear in plaintext in logs, webhooks, or API responses.
deck.co/changelog
Deck.co retweeted
A suite of giants were built in the open banking era:
The
@coinbase @RobinhoodApp @Venmo s of the world
All did it thanks to the layer that was previously missing @Plaid
Check out how @deck_agent creates this effect across industries beyond banking:
Music
deck.co/customers/patchbay
Energy
deck.co/customers/deepki.htm…
Procurement
deck.co/customers/rampart.ht…
@Techweek_ NY starts Today.
Our agents have been spotted in the city operating like humans, doing laundry, judging your coffee order.
For 3 days only, 4 Deck agents are in Manhattan running tasks, taking selfies, and doing what agents do.
Here's the game: spot one, snap a photo, tag hashtag#deckweek2026, and you're entered to win a helicopter tour over NYC.
Find a QR code on any poster (or on the agent himself) to get three entries. Launch a real Deck agent during the week and we'll bump you to five.
Where to find them:
→ Tues 6/2 — Events in Soho
→ Wed 6/3 — Unicorner AI day fireside chats + the Afterparty at Public Hotel
→ Thurs 6/4 — Chelsea + Javits Center at lunch
See you out there.
#NYTechWeek
Could these be for @Techweek_ ? I wonder who'll pick up if I call that number? 🤔
#NYTechWeek
Deck.co retweeted
Someone sent me this clip of a @deck_agent spotted in NYC
Should we send more?
@Techweek_
Deck.co retweeted
I was wondering why the H my condo bill was 30% higher this month
I asked Deck to figure it out. We have the culprit !
New: Auth Component v2 🔐
A drop-in React component for secure credential capture and source authentication. Handles source selection, credential collection, MFA, security questions, and error states. Credentials go straight to the vault, never touch your systems.
What's new:
→ Live view of the agent working after credential submission
→ Short-lived session tokens via POST /v2/token
→ Auto-fire verification task runs after credential creation
→ Update mode for re-collecting existing credentials
docs.deck.co/components/auth
Deck.co retweeted
Hookdeck Outpost shipped last week: Open-source, managed infrastructure for sending webhooks to customers.
Here's what it looks like running in the wild — a real install inside @deck_agent.
Deck's the exact kind of company we built Outpost for: where reliable webhooks are mandatory, but they'd rather spend cycles on the core product.