Data and sharing · Autessa Analytics
PostHog connection
Autessa Analytics connects to your PostHog project through a server-side Autessa script tool. The PostHog key lives in that tool, never in the browser; the dashboard sends only the query and its values, user-supplied values are bound as parameters, results are cached for a minute, and busy or rate-limited answers are queued and retried automatically.
The problem it solves
Most homemade PostHog dashboards put the key in the page
The quickest way to build a dashboard on an analytics API is to put a personal API key in the front end, which hands it to anyone who opens the page. Autessa Analytics was rebuilt so every read runs as an Autessa tool call: the key stays on the server, and access is controlled by who the tool and the app are shared with.
What you get
- Every PostHog query runs through one Autessa script tool that holds the key.
- Values from the page (dates, sources, searches, ids) are bound through named placeholders, never pasted into the query.
- Results are cached for 60 seconds; identical queries in flight are shared.
- At most three queries run at once; extra ones wait their turn.
- “Too busy” and rate-limit answers retry up to three times with backoff instead of showing an error.
- Errors that remain are shown as a message with a retry, never swallowed.
How it works
How does posthog connection work?
A report asks a question
For example: visitors per day for the last 30 days.
The tool runs it
The dashboard calls the Autessa script tool with the query and its values; the tool adds the key and asks PostHog.
Rows come back
Results return as rows, are cached for a minute, and fill the chart.
Busy? It waits
If PostHog is throttling, the request backs off and tries again.
Every option
Connection behavior
| Option | What it does |
|---|---|
| Key storage | In the server-side Autessa script tool only. |
| Parameter binding | Named placeholders for every user- or link-supplied value. |
| Cache | 60 seconds per query (20 seconds for Live now). |
| Concurrency | Up to three queries at once. |
| Retries | Up to three, with exponential backoff, on busy and rate-limit answers. |
| Deep links | “Open in PostHog” for people and replays. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Anyone the app is shared with | Open every report, switch the date range, filter and search, and open people and replays in PostHog. |
| App admin | Share the app and its PostHog query tool with teammates, at read or edit level, and decide which tables they can change. |
| Tool owner | Keep the PostHog key in the script tool and share the tool at read level with the people who use the app. |
Connected
How it connects to the rest of Autessa Analytics
FAQ
Questions about posthog connection
Does Autessa Analytics expose my PostHog key?
No. The key is held by a server-side Autessa script tool; the browser only sends the query and its values.
What happens when PostHog is busy?
Queries are queued, three at a time, and busy or rate-limit answers are retried with backoff before any error is shown.
Do I need a PostHog project?
Yes. Autessa Analytics reads events, people and recordings from your PostHog project.
100% customizable, code and all
Make Autessa Analytics fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours