Workflow & Automation · Integration
Hex
Add Hex to your product for your customers, and give your AI agents governed access to it.
Hex's API base is app.hex.tech/api/v1, not api.hex.tech, which redirects, and single tenant or private deployment customers sit on their own host entirely, so the base URL has to be captured per connection. The surface is run orchestration rather than data access: you POST a run for a project id, optionally supplying inputParams that match the project's input elements by name, and then poll the run until it reports a terminal status. There is no endpoint that returns the contents of a cell or a dataframe, so anything you want out of a run has to be written to a warehouse or an export from inside the notebook itself. Concurrent runs of the same project are limited and a second request is refused rather than queued, so retries need backoff and a check on the existing run. Tokens are personal access tokens or workspace tokens, and a personal token only sees the projects that user can view, which makes a departing employee's token a silent cause of shrinking project lists. Of the available categories this is the least wrong fit: Hex is a data workspace, but its API genuinely exposes projects and runs rather than datasets. fastn holds each customer's host and token and keeps the run history attributed to the right tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Hex workspace so your product can trigger the analysis they already maintain.
Pass parameters such as a date range or account id into a Hex project run from your own UI.
Show the status and finished run link for a customer's scheduled analyses inside your app.
Kick off a Hex run when a data load in your product completes, so downstream reports refresh in order.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent start a named project run with checked parameters, with every run audited per tenant.
Let an agent report which runs errored in the last day and which project they belong to.
Allow an agent to list the projects a customer can run, with no ability to edit them.
Example prompt
Run the weekly churn analysis in Hex for last month and tell me when it finishes.
Set up Hex in 4 steps
- 01Enable the Hex connector from your fastn dashboard.
- 02Have each customer authorise their own Hex account, so calls run under their credentials rather than a shared key.
- 03Decide which processes, runs and queues your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Hex integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Hex integration without building it. Your customers connect their own Hex account inside your product and work their processes, runs and queues there, with no per-customer code on your side.
- Handle the part that actually costs time: runs are asynchronous and can fail long after they are accepted, so an outcome that never arrives must look different from one that succeeded. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Hex update is not your on-call problem.
- One integration serves your product and your agents. The same governed Hex connection powers in-product features and gives AI agents scoped, audited access, so you start work in the automation platform your customers already run, and get the outcome back without wiring it twice.
Used by these teams
Compare with
Ansible
Automation Anywhere
Microsoft Power AutomateOften used alongside
Tools the same teams tend to run next to Hex, across other categories.
Amazon SES
Resend
Mailgun
PostmarkHex integration FAQ
How do I add a Hex integration to my product?
Enable the Hex connector in your fastn dashboard, then let each customer authenticate their own Hex account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Hex client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Hex account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Hex account and only ever sees their own processes, runs and queues. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Hex integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent start a named project run with checked parameters, with every run audited per tenant.
Who maintains the Hex integration?
fastn does. When Hex changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product start a Hex run and read its outcome?
Yes. Your product can trigger a process in the customer's own Hex account, pass it input, and take the result back as an event rather than polling for it.
What happens when a Hex run is slow or fails?
The failure surfaces with its error rather than as a silent timeout, and the run keeps its own identifier so a retry can be matched to the original. That matters more here than in most integrations, because a run that half-completed is not the same as one that never started.
What can I build with the Hex integration?
A common starting point: let a customer connect their own Hex workspace so your product can trigger the analysis they already maintain. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Hex integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Hex does not change your per-connector cost. You can start free with 3 connected accounts.
Add Hex to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.