Tabductor

For inbox & documents

Forward an email, get the work back

Every workflow can have its own email address. Forward an invoice, a list or a question; the run starts on its own, saves the attachments as files, and replies in the same thread with the result, the rows it changed as a spreadsheet, and any files it produced.

Where it fits

From the sites you use to results you can use

Sites you use today

  • Forwarded emails
  • PDF and spreadsheet attachments
  • Portals behind a sign-in
  • Requests from your team

Tabductor

  1. Agent runLearns the task once in a stealth browser
  2. Distilled scriptReruns it in seconds, the same way each time

What you get

  • A threaded reply with the result
  • Changed rows as an .xlsx file
  • Files saved to your library
  • A signed webhook to your systems
From the sites your team already works in to results you can use, without an integration on their side.

The difference

Do it once, not every time

The work by hand repeats in full on every round. In Tabductor, you describe it once and the schedule does the rest.

6 steps, every time

By hand

  1. Open the email and download the attachment
  2. Sign in to the portal it refers to
  3. Look up or enter the details by hand
  4. Save the documents somewhere findable
  5. Reply with what you found
  6. Do it again for the next email

3 steps, once

With Tabductor

  1. Turn on the workflow's email address once
  2. Forward mail to it; each email starts a run
  3. The answer, a spreadsheet and the files come back in the same thread

Over time

Agent once, script after

The first run is an agent finding its way. Every run after is the distilled script: seconds, not minutes, and a fraction of the cost. When the site changes, the agent repairs the script and steps aside again.

Run historyOn email · as it arrives
  1. Email 1Agent run · Agent learns the task
  2. Email 2Distilled script
  3. Email 3Distilled script
  4. Email 4Distilled script
  5. Email 5Agent repair · Portal moved its order search
  6. Email 6Distilled script
  7. Email 7Distilled script
Illustrative. Bar length shows run time relative to the first agent run. The agent comes back only when a guard trips, then hands the job back to the script.

Examples

Workflows to start from

Each one starts as a sentence like these. Change the site, the schedule or the fields to fit your work.

  • Invoice to rowOn email
    When an email arrives with a PDF invoice, read the vendor, invoice number, amount and due date and add them to the invoices table.
    • vendor
    • invoice_number
    • amount
    • due_on
  • Order lookup by emailOn email
    When an email arrives with an order number, sign in to the supplier portal and reply with the order's status, carrier and tracking number.
    • order_number
    • status
    • carrier
    • tracking
  • Statement downloadsMonthly
    On the 1st of each month, sign in to each bank portal, ask me to finish the sign-in if it needs a code, and save each statement PDF as a file.
    • account
    • period
    • statement

Try it on your own work

Describe one job your team repeats. The first run shows you exactly what the agent did.

More solutions

Inbox & documents use cases · Tabductor