Skip to content

Integrations and connectors

Updated · View as Markdown

Which source systems finstory can load figures from, how to connect one, and how to manage connections and scheduled loads. Connecting a source needs the Admin or Power user role.

finstory only reads from a source.

Source Type What it loads How you sign in
QuickBooks Accounting Chart of accounts and books, with companies, classes, locations and budgets At QuickBooks
Xero Accounting Chart of accounts and books, with organisations and tracking categories At Xero
Puzzle Accounting Chart of accounts and books At Puzzle
NetSuite Accounting Chart of accounts and books Keys on the card
DualEntry Accounting Chart of accounts and books, with customers, vendors and projects API key on the card
Rillet Accounting Chart of accounts and books, with Rillet’s own fields such as Department API key on the card
Adaptive Planning Planning Actuals; dimensions and versions can follow Login on the card
Stripe Billing Subscription metrics such as MRR, ARR and active customers At Stripe
Snowflake Data warehouse Finance tables you point it at: accounts, companies, books and budgets Keys on the card
Plausible Web analytics Visits, pageviews and goal conversions API key on the card
Google Analytics Web analytics Sessions, users, views and key events At Google

New sources are connected through Reeve, the built-in AI assistant.

  1. Open Reeve and ask it to connect the source, for example “Connect QuickBooks”.
  2. Reeve shows a card for the source. The card says which model the figures will go into; you can pick another model or a new one.
  3. Choose Connect.
    • For a source you sign in to, its own sign-in page opens, sometimes in a pop-up. Sign in, approve read-only access for finstory, and you return to the card.
    • For a source that uses keys, type them into the fields on the card. What you type there is not sent to the chat.
  4. Choose Load. A progress bar shows the load. If the model already holds figures for the months being loaded, the card first tells you what the load replaces.

For some sources a single button on the card connects and loads in one go.

Source What the card asks for
NetSuite Account ID, consumer key and secret, token ID and secret, RESTlet URL, script ID, deployment ID, retained earnings account and reporting currency. Your NetSuite administrator sets up finstory’s integration and RESTlet first.
Adaptive Planning Login and password of a user allowed to use the API, and the reporting currency.
Snowflake Account identifier, a user with key-pair login and read access to the finance tables, and its private key. Reeve then lists the tables it can read.
DualEntry A View-Only API key.
Rillet A Read-only API key.
Plausible A Stats API key and the site’s domain.
Google Analytics The GA4 property ID (the number, not the G- measurement ID).
  • Most sources load about the last two years, month by month.
  • NetSuite loads its last three months first. Ask Reeve for earlier quarters.
  • Snowflake, Plausible and Google Analytics load into a model of their own rather than the model that holds your books.

Open Settings > Connections. Each connection shows its source, its model and its status: Signed in, Needs its login or Login refused.

Button What it does
Reconnect Opens the source’s sign-in again, or asks for its keys again.
Change Changes a basic setting, such as the site or property ID. The next load uses it.
Test Checks now whether the login still works.
History Lists the connection’s recent loads. Full log shows the detail and Stop ends a running load.
Remove Stops the connection and its schedules. The figures it already loaded stay.

To make or change a schedule, ask Reeve to load a source on set days, for example each month’s actuals.

Open Settings > Schedules to see each schedule with its source, model, next run and last run.

  • Run now starts one run straight away.
  • Pause stops a schedule from running by itself; Resume switches it back on.
  • Delete removes the schedule. The loads it ran stay in the connection’s History.

For problems with a connection, see FAQ and troubleshooting.