Skip to content

OpsMax is in development. This is how it works at launch.

Browse the docs

Connections

What each connection lets OpsMax do, and what it never does.

Official connections pending

  • QuickBooksReads

    You connect it from OpsMax: you sign in to it and approve on its consent screen. OpsMax reads your books. A change in your books is its own setting, off until your company turns it on, and a person in your company, or our team with OpsMax Agency, confirms each change.

  • RampReads

    You connect it from OpsMax: you sign in to it as an administrator and approve the access OpsMax asks for. OpsMax starts by reading from it; any change there is its own setting, off until your company turns it on, and a person in your company, or our team with OpsMax Agency, confirms each change.

  • GmailReads · drafts

    You connect it from OpsMax: you sign in to it and approve on its consent screen. The access you approve allows OpsMax to read your email and to save suggested replies as drafts. No email is sent until a person in your company sends it.

    When OpsMax changes something in one of your tools, such as a bill or a vendor's details, a person in your company, or our team with OpsMax Agency, confirms that change first. Two things are the exception once your company switches them on: OpsMax saves suggested replies as drafts, and saves papers into the one folder you chose, without a person confirming each one. No email is sent until a person in your company sends it, and no existing file is changed or removed.

  • Google DriveReads · saves

    You connect it from OpsMax: you sign in to it, approve on its consent screen and choose one folder in its own picker. OpsMax reads only that folder, the papers it saved there and the name of the account you signed in with. Saving papers there is its own setting, off until your company turns it on, and OpsMax never saves outside that folder. It removes no file and changes no one's access.

  • TelegramReads · sends

    You connect it with a bot you make in its official BotFather: you paste the bot's token into OpsMax, not on a consent screen. OpsMax reads the messages your bot receives, and the token allows it to send messages as your bot. A person in your company, or our team with OpsMax Agency, confirms each message; no message is sent before then.

  • PlaidReads

    You connect your bank from OpsMax, in its own window: you pick your bank, sign in to the bank and choose which accounts OpsMax reads. OpsMax reads your transactions and balances; the access it asks for starts no payment.

  • GeminiReads

    You connect it from OpsMax: you sign in to it and approve read-only access. OpsMax reads balances, transfers and trades; it places no orders and makes no withdrawals.

  • BlockscoutReads

    Needs no connection: you add each wallet address, and OpsMax reads its public blockchain data through the explorer's public API. OpsMax holds no wallet keys.

  • RipplingReads

    You connect it as an administrator: you sign in to it and approve read-only access. OpsMax reads your team's details, never a person's pay; a person runs it.

More integrations on the way