Skip to main content
sieving.ai

Designed for the tools you already use.

Sieving will connect to business apps through each provider’s official sign-in. Here’s what’s available today, what’s planned, how connections will work and how we’ll decide what comes first.

Available today

None yet

No connectors are live. Sieving is in development, and when the first connector is ready to use it’ll be listed here with exactly what it can and can’t do.

Planned

Planned

6 categories of business software, listed below. We’ll choose specific apps from what early-access businesses tell us they use, and we have no official partnerships with any software provider.

The categories we plan to support first.

Each category lists the kind of work a connector would let Sieving take on. Examples are illustrative, not features you can use yet.
Examples · planned
  • Email

    Turn incoming messages into tasks, records and timely replies.

    • Supplier bill arrives → draft it in accounting
    • New enquiry → create a lead
    Planned
  • Calendar

    Act on new bookings, cancellations and reschedules as they happen.

    • Booking made → send confirmation
    • Cancellation → offer the slot to the waiting list
    Planned
  • CRM

    Keep contacts, deals and customer history accurate without retyping.

    • Invoice paid → update the customer record
    • Deal won → start onboarding
    Planned
  • Accounting

    Create draft invoices and bills, and keep payment status in sync.

    • Job completed → draft an invoice
    • Bill approved → schedule payment reminder
    Planned
  • Payments

    React to successful payments, refunds and failed charges.

    • Payment failed → notify the account owner
    • Refund issued → update records
    Planned
  • Spreadsheets

    Log activity and keep shared sheets current automatically.

    • New booking → add a row
    • Weekly summary → refresh the dashboard sheet
    Planned

Your accounts, on your terms.

Rules every connector will follow, whichever apps come first.
  • Official authorisation only

    You’ll connect each app through the provider’s own authorisation, usually its sign-in page. Sieving won’t ask for, or store, your app passwords.

  • Only the access a workflow needs

    Each workflow will ask for the narrowest access its steps use, and you’ll see what that is before you agree.

  • Disconnect at any time

    Every connection’s status will be in one place. Disconnecting will delete Sieving’s stored access, revoke it with the provider where the provider allows, and pause the workflows that relied on it.

  • Credentials kept on the server

    Connection credentials will be encrypted on Sieving’s servers. They’ll never be sent to your browser or written to logs.

  • Published APIs and provider rules

    Connectors will use each provider’s official, documented interfaces and follow its usage limits and review requirements. No scraping and no workarounds.

Chosen by what early-access businesses need.

We’d rather build a few connectors that work reliably than many that don’t. These are the questions that decide the order.
  1. 01How often the work comes up in early-access answers.
  2. 02How much a reliable automation would be worth to the business.
  3. 03How many early-access businesses already use the app.
  4. 04Whether the provider offers suitable official access, and what review it requires.
  5. 05The ongoing cost of keeping the connector reliable.

Tell us which tools you rely on.

Your early-access answers decide which connectors we build first. It takes about a minute.

Free to join. No payment details, no commitment.