Integrations

Your numbers already live somewhere.

StoriBot reads them where they are, drafts the update in your voice, and leaves the system exactly as it found it — every write is one you granted.
Book a walkthrough
Three kinds of source

Files, live systems, and the open web.

Most updates draw on more than one. A quarter’s numbers might come from a connected system, the commentary from a doc your team wrote, and one market figure from a cited source outside the business.

Uploaded files

PDFs, Word docs, spreadsheets, slides, Markdown — drop in the files you already have and StoriBot reads them.

Live systems

Connect the systems your numbers already live in, and the page reflects the latest figures rather than a stale export.

Grounded web research

StoriBot can search and fetch from the web while it drafts — with sources attached, so external facts trace back just like your own.

Whatever the source, every number traces back to it.

What connects today

Every connection, and what it’s allowed to do.

Each card shows what the connection reads, what it can write, and how you authorise it. The two are granted separately — a system can read without ever writing.

  • Stripe

    Reads

    Revenue, subscriptions and payouts.

    Connect with an API token

  • Xero

    Reads

    The ledger, invoices and the numbers finance signs off.

    Connect with OAuth

  • Shopify

    Reads

    Orders, products and store performance.

    Connect with an API token

  • HubSpot

    Reads

    Contacts, deals and where the pipeline actually moved.

    Connect with an API token

  • PostHog

    Reads

    Product usage, funnels and retention.

    Connect with an API token

  • Amplitude

    Reads

    Product analytics and cohort behaviour.

    Connect with an API token

  • Jira

    Reads

    Issues, releases and what actually shipped.

    Connect with an API token

  • Airtable

    Reads

    Bases and the operational trackers your team keeps by hand.

    Connect with OAuth

  • Zernio

    ReadsWrites

    Schedules the posts StoriBot composes, and reads back how they performed across platforms.

    Connect with an API token

Stripe, Xero, Shopify, HubSpot, PostHog, Amplitude, Jira, Airtable and Zernio are trademarks of their respective owners. StoriBot is not affiliated with or endorsed by them.

What it can change

It reads your systems. Every write is one you granted.

That is the whole of it. Reading is how the update gets drafted; writing only happens where you granted it — scheduling a post you approved, for instance. Nothing else in a connected system is touched.

One switch turns every write off

Write and irreversible operations can be disabled across your whole instance. Scheduling stops; everything else keeps working. The control sits with you, not with a promise from us.

Your data isn’t used for training

Connected data is processed inside your instance and is never used to train any model. Credentials are stored securely and scoped to your instance alone. See trust & controls.

The loop closes

What you sent becomes what you report on.

The artifact goes out through a connected system, and how it performed comes back in as a source for the next one — built from the same connection that sent it. Most drafting tools stop at the draft.

The same connected stack feeds both directions. Revenue from Stripe and usage from PostHog make the monthly investor update that goes to the market, and the weekly one that goes to your team.

Connect one system. See the difference.

Tell us where your numbers live and we’ll draft your next update from them.

Book a walkthrough