Automate almost anything that a person would do

Every Devoku employee has its own runtime and its own API key. One agent can talk to another, control it, ask it for data and put data back into it — like this: the research agent pulls the numbers and writes them into the build agent’s folder, and the build agent carries on without you copying anything. An agent can switch, in the middle of a job, between Cursor, Claude Code, Codex and Devoku Jet, and keep the same context through the switch. That workspace holds the context for years, so an agent that started the work in 2025 still knows the project in 2028. Agents install the tools they need on their own runtime. You reach all of it from the desktop app, from the phone app on iOS or Android, or by voice. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Your Devoku employee does the work from your words, and what it works out, it keeps. A procedure it has solved once goes into Devoku Knowledge. The keys go into Devoku Secrets. References and critical info go into Devoku Rules. Next time the job is the same, so it follows the procedure instead of working it out again. When it finds a better way to do something, it updates the procedure and uses that better way from then on, so the same job does not cost what it cost last month. It looks up what it has learned, updates those procedures automatically when the work changes, and keeps learning without you prompting it. You can hand it extra information at any point: it files that in Devoku Knowledge and uses it when it is relevant. It learns from its own mistakes, and it becomes very efficient. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every agent can have a second Devoku employee standing on top of it, supervising it. The supervisor does not do the work. It watches the agent that is doing the work. If the working agent fails, for any reason, the supervisor repairs it and sets it going again, so the job keeps running 24/7 instead of until the next crash. You can put another supervisor on top of that supervisor, and another above that, as many levels as the work needs. There is no limit. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

You do not set up the triggers yourself. You tell your Devoku employee in plain words when the work should happen — after an invoice arrives, every Monday, when a customer replies — and it decides what to watch and what to start. It writes the schedule, the condition and the retry for each step, and changes them when the work changes. When a step starts failing because a page moved or a field was renamed, your Devoku employee notices and fixes the trigger itself. No builder to learn, no flow chart to draw. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Most of the work that still needs a person happens in a browser. Your Devoku employee opens the site and sees the page the way you see it — the layout, the buttons, the message that appears after a click — not just the source code behind it. It fills the form, waits for the confirmation, reads the number and writes it where it belongs. When a page changes, it looks at the new page and finds the way through instead of failing on a selector. This works on supplier portals, government sites and the tools that never had an API. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every Devoku employee gets a backup without you asking for one. The backup holds all of the chats and all of the workspace files, and it grows as the workspace and the chats grow. It is deduplicated, so when the workspace gets lighter the backup copy gets lighter with it instead of keeping every old byte twice. You also get historical snapshots, so you can see how the folder looked last week or last year. How often the backup runs is yours to set, and so is how long the snapshots are kept. Nothing the agent has done, and nothing in its folder, depends on one machine staying alive. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every morning your Devoku employee opens your books — Xero, Sage or QuickBooks — and finds every invoice that is past its due date. It skips the ones you have already reminded in the last seven days, and it skips anything marked as a dispute. For the rest, it sends one email from your own inbox with the invoice attached, written the way a person in your company would write it. When your books show the invoice paid, it stops. Paid and disputed invoices are left alone until the next morning. If your accounting software has no API, your Devoku employee uses the screens like a person. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every morning your Devoku employee takes the new bank statement — from your inbox, or straight from the bank — and opens your books (Xero, QuickBooks or Exact). It matches each line to the ledger entry and writes the bank reference on it. A line with no obvious match is traced through supplier details until it finds its entry. Where one payment could belong to several entries, it shows you the candidates instead of guessing. What is left is the short list that really needs your eyes, and the next morning starts there. If the bank has no API, it fetches the statement in the Devoku browser. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

At the interval you choose, your Devoku employee opens your books (Sage, Xero, or any other) and reads the supplier statements that arrive in your inbox. It matches each line to a bill by supplier name, invoice number and amount. A bill on the statement that is missing from your books gets added, with the statement PDF attached. Where the statement amount and your amount differ, it marks the bill and writes both numbers in the comments. Where the statement says the bill is paid, it looks for that payment in Wise, Mercury or Airwallex and marks the bill paid when the bank shows it. A second Devoku employee can watch this one, and send it back to any statement that still has unmatched lines. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

When a supplier invoice arrives, your Devoku employee finds the purchase order by its number and the delivery note by the order number. If the three agree on quantity and price, it posts the invoice in Xero, Sage or Exact and writes the order number on the ledger entry. If the delivery note has not arrived, it holds the invoice and finishes the match the moment the note lands. If they disagree, it marks the invoice with both numbers and tells you. Nothing is posted twice, and nothing sits in a pile waiting for a quiet afternoon. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Customers email a remittance advice naming the payment and the invoices it covers. Your Devoku employee reads it next to the bank statement and finds each invoice in Xero, QuickBooks or Sage. Where the invoices add up to the payment, it applies the payment across them and writes the bank reference. Where one invoice number is missing, it applies the payment to the ones it can match and tells credit control which number is missing, with the remittance attached. Where a remittance covers invoices from two systems, it reconciles both before it writes anything. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Enquiries arrive by email from the property portal. Your Devoku employee finds the property on your sheet, reads the agent’s Google Calendar and offers times inside the viewing hours for the next few days. When the enquirer picks a date, it sends the invitation to both and records the viewing. An enquirer who has not replied in two days gets a reminder, and after that the lead goes to the alternate agent with everything known about it. An enquiry for a property already let is answered with the two nearest matches on the sheet. Viewings end up in the diary, not in a thread. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every two hours your Devoku employee reads the new return emails and finds the order in Shopify by its number. If the order is inside the return window and the SKU is on your returns sheet, it creates the return in Shopify and replies with the return address. If the order is outside the window, or the SKU is not on the sheet, it writes that rule on the Shopify order instead of replying with an address. When the parcel arrives, it writes the refund amount, the currency and the Stripe charge id on the order. When Stripe shows the refund succeeded, the order is refunded. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Whenever a Stripe dispute email is forwarded, your Devoku employee takes the disputes that have no folder yet. It saves the Shopify order, the tracking page and the email thread into a Dropbox folder named with the dispute id, and adds those files to the dispute in Stripe. It writes the reply-by date on the Shopify order. If Shopify has no matching order, it keeps the folder and writes “order missing” on the dispute. When Stripe shows the dispute submitted, it writes the submission time on the order. A second Devoku employee can watch this one: for each open dispute it checks the dispute id, the folder name and the reply-by date, and sends back any dispute that is missing one. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every week your Devoku employee reads the week’s tickets in Zendesk and groups them by what was asked. It compares each group with your existing articles. A question your help centre does not answer yet becomes a draft, written from the replies your team already sent. A question that matches an article adds to that article’s demand count, so you can see which enquiries come up most. You review the drafts and publish what you like. Your articles stay in your voice. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every morning your Devoku employee reads Shopify stock for the SKUs on your reorder sheet. If stock is above the reorder level, it skips the row. If stock is at or below the level and the order date is empty, it emails the supplier the SKU and the quantity. If an order date is already filled, it does not chase the supplier again. When the supplier’s delivery email arrives, it clears the date and writes how many arrived. You see what was ordered and what is still short. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

At the interval you set, your Devoku employee reads the rows of your Google Sheets price list and compares each price with the price in Shopify. Where the two differ, it updates the product in Shopify and writes the old price, the new price and the time on the row. Where they already agree, it leaves the product alone. Nothing is changed twice, and the sheet always shows what the store is actually charging. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

When a customer emails asking to cancel, your Devoku employee finds the order by its number in Shopify. If the order has not shipped, it cancels it and emails the customer to confirm. If it has already shipped, it emails the customer the return instructions and asks the carrier to send the parcel back to you. Either way the customer hears back the same hour, and the order carries the reason. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

As paid orders arrive, your Devoku employee runs each one against your checks: billing and delivery countries, a first order above a value, several orders to one address on one card. An order that trips nothing goes straight to dispatch. An order that trips a check is held in Shopify with the reason noted, and your Devoku employee gathers the Stripe risk signals, the order history and the address check into one message for you. When you release the hold, it records who released it and when, and the order moves on. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

When a supplier sends a price change, your Devoku employee reads the SKUs and the new costs, writes the old and new cost on each row with the date, and recalculates the margin. Where the new margin is still above your floor, it leaves the selling price alone. Where it falls below the floor, it works out the price that restores the margin, sends you the SKU at that price, and applies it across Shopify and Amazon once you confirm. Your floor holds, without a spreadsheet exercise every time a supplier writes. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

When the warehouse emails its count, your Devoku employee matches each SKU to Shopify. Where the counted quantity and the Shopify quantity differ, it writes both numbers next to that SKU. Where the row is marked Apply, it sets the Shopify quantity to the counted quantity and writes the time. A SKU on the count that Shopify does not have is written back as missing from Shopify. The count comes back complete, with every difference visible in one place. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

A quote request lands in your sales inbox. Your Devoku employee finds the company in HubSpot and reads your price list. Each SKU on the list goes onto a HubSpot quote at the sheet price and lead time, and the quote goes back to the customer. A SKU that is not on the list stays off the quote, and your Devoku employee tells you which one it skipped. The customer gets one clear quote, priced the way your list says. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

When a quotation request arrives, your Devoku employee builds the quote from your price list and finds the company in Salesforce. A SKU missing from the list is left off and marked “no price”, and you are told which one. When the quote goes out, the clock starts. If the customer confirms, the quote is marked won. If there is no reply after the days you set, it marks the quote for follow-up and drafts the nudge. No quote goes quiet without someone noticing. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Your Devoku employee works through your revisit sheet, finds each deal in HubSpot and drafts the email from the template set for that stage. Every draft waits for your review before it is sent, so nothing leaves in a voice you have not approved. When a customer replies, the reply is added to the deal and the row is marked as contacted. The list gets shorter every week, and nobody has to remember it. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Your Devoku employee reads the new reviews on Google and the ones that arrive by email from Trustpilot. A review of four or five stars gets a short thank-you posted straight away. A review of three stars or fewer comes to you as a draft, so you can answer it in your own words. Each review is marked answered, and the ones waiting for you sit in one list. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

At the interval you set, your Devoku employee opens each competitor page you follow, records the price on your Google Sheets sheet and compares it with the last reading. A change is written down with the new price, the date and a copy of the page. When a competitor redesigns and the price moves elsewhere on their site, your Devoku employee looks for it again and tells you where it found it. Your view of the market stops depending on someone remembering to check. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Enquiries arrive as emails, from your website or from your ads. Your Devoku employee reads each one and checks the address against your HubSpot contacts. A new address becomes a new lead in HubSpot. An address already in the CRM gets an immediate reply built from that enquiry, so a returning customer is answered the same hour. Every enquiry is logged, and none sits unread over a weekend. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Each morning your Devoku employee checks the rate at Wise, Mercury or Airwallex for every supplier invoice row still marked Pending. Where the rate is at your target or better, it completes the conversion, writes the bank reference and the rate on the row, and marks it Converted. Where the rate is short, it writes the rate it saw with the date and looks again next morning. When the bank shows the transfer complete, it writes the amount received and marks the row Paid. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Your Devoku employee reads your brokerage account and works out what you hold by position, by sector and by currency. Everything inside your limits is stamped on the row with the date. Anything over a limit comes to you with the actual figure, the amount it is over, and the trades that would bring it back inside. Where you have written a rule for a breach, your Devoku employee follows that rule and tells you what it did. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.

Every hour your Devoku employee reads the Sentry issues opened since the last check. If a GitHub issue already exists for that error, it comments the new event count and the release on that issue. If the error is new and appears again on a second attempt, it opens one GitHub issue with the stack trace, the release and a failing test. If the second attempt passes, it opens one issue that starts with “not reproduced”, plus the stack trace and the release. You get one issue per error, not one per event. Your logins and passwords go in Devoku Secrets — a safe place inside your Devoku employee.