Reference & Lookup Data · Integration
Bombora
Add Bombora to your product for your customers, and give your AI agents governed access to it.
Embed a Bombora integration so your customers can pull their own intent data, topics, and account-level surge signals into your product and act on them where their go-to-market work happens, with governed agent access to the same signals. Intent data arrives in volume, so pagination and throttling are handled for you and every call is logged per tenant. fastn handles each customer's credentials and API upkeep, so onboarding another account is configuration rather than code.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Bombora account and read account-level intent signals into your product.
Read topic-level intent so your product can score and prioritise accounts against the topics that matter to them.
Map each customer's own topic selection and account list as configuration rather than code.
Trigger your product when an account surges on a tracked topic so outreach starts while the intent is fresh.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reads intent signals for an account before drafting outreach for a rep.
An agent builds a prioritised account list from surge data within governed permissions.
An agent reacts to a surge event and adds the account to the right campaign.
Example prompt
List accounts surging on our top three topics this week and show which topic drove each.
Set up Bombora in 4 steps
- 01Open the Bombora connector from your fastn dashboard.
- 02Have each customer authenticate their own Bombora account with read scopes.
- 03Map the topics, account fields, and intent scores your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Bombora integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Bombora integration without building it. Your customers connect their own Bombora account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Bombora update is not your on-call problem.
- One integration serves your product and your agents. The same governed Bombora connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Works well with
Oracle BlueKai
Salesforce
HubSpotOften used alongside
Tools the same teams tend to run next to Bombora, across other categories.
Notion
Snowflake
Box
ShopifyBombora integration FAQ
How do I add a Bombora integration to my product?
Enable the Bombora connector in your fastn dashboard, then let each customer authenticate their own Bombora account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Bombora client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Bombora account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Bombora account and only ever sees their own lookups, results and reports. 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 Bombora integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reads intent signals for an account before drafting outreach for a rep.
Who maintains the Bombora integration?
fastn does. When Bombora 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.
Whose credentials does a Bombora lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Bombora results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Bombora is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Bombora integration?
A common starting point: connect their own Bombora account and read account-level intent signals into your product. 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 Bombora integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Bombora does not change your per-connector cost. You can start free with 3 connected accounts.
Add Bombora to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.