Integrations

Eny — AI receipt scanner

Snap a photo of a receipt, get a transaction in Flow. Eny does the parsing; Flow stores the result.

What Eny is

Eny is a separate, paid product made by the same team as Flow. It uses an AI vision model to read receipts you photograph or upload — line items, totals, dates — and turn them into Flow transactions via Flow's first-party integration.

You get 10 free scans when you sign up at eny.gege.mn. After that it's a paid service. Once you connect to Flow, the in-app Eny screen shows your remaining credits and the email/account the credits belong to.

Connecting Flow to Eny

The connection is initiated from the Eny side, not Flow:

1. Sign up or log in at eny.gege.mn.
2. In the Eny dashboard, find the Connect with Flow button.
3. On a phone with Flow installed, tapping the button deep-links straight into Flow and confirms the connection.
   On a computer, the dashboard shows a QR code instead — open the camera on the phone where Flow is installed, scan the QR, and Flow opens to confirm.

Behind the scenes, Eny generates an API key during the connection flow. Flow stores that key locally on the device and uses it to talk to Eny's API. The key never leaves your phone — it's not in your iCloud backup ZIP, not on a server somewhere.

Configuring it from Flow

Once connected, the integration's settings live at Profile → Preferences → Eny. The screen also surfaces your Connected status (with the Eny account email), Credits Remaining, and a link to the Eny Dashboard so you don't have to switch tabs to check.

Two toggles control how parsed receipts land in Flow:

• Create a transaction per item — when off (the default behavior), each receipt becomes one Flow transaction whose total matches the receipt total, with the line items written into the notes field as a list. When on, every line item becomes its own Flow transaction. The toggle's own subtitle warns it can be "chaotic for long receipts" — set this based on whether you actually want per-item granularity.
• Mark transactions as pending — when on, parsed transactions land in the Pending group so you can sanity-check them before they hit your balance. Even when this is off, transactions whose parsed date is more than 6 hours old still land as pending — a safety net so a forgotten old receipt doesn't quietly rewrite your past.

Privacy disclosure inside Flow

The Eny preferences screen reminds you that this is an external service: "Flow does not send anything on your behalf, only the images/data you choose is sent." The data you scan goes to Eny and Google (Eny's underlying vision provider). The page links out to Eny's Terms of Service and Privacy Policy — read them once before sending receipts that contain anything sensitive.

Scanning a receipt

After connecting, you can optionally add a scan button to the FAB menu (the + button at the bottom of the screen). Once enabled, opening the FAB shows a camera-icon entry alongside the normal transaction creation options.

Tap that scan button and you can:

• Take a fresh photo of a receipt with the camera.
• Upload from your photo library — up to five images at a time.

From there, parsing happens server-side at Eny:

• If you keep Flow open, a toast appears when parsing finishes and the transactions land immediately.
• If you close the app, Flow remembers what you sent. The next time you open Flow, the parsed transactions appear — there's no push notification, only the in-app toast.

Disconnecting

Scroll to the bottom of Profile → Preferences → Eny and tap the red Disconnect Eny button. That wipes the locally-stored API key. Existing transactions Eny created stay in Flow exactly as they are — the integration only governs how new scans get in.