Social & Community · Integration

Brilliant Directories

Add Brilliant Directories to your product for your customers, and give your AI agents governed access to it.

Brilliant Directories powers membership directory websites, and its API is per-site: calls go to the customer's own directory hostname under /api/v2/{model}, not to a shared vendor host, with the key sent in an X-Api-Key header and generated inside that site's admin area. Almost every object in the site is exposed as a model, including members, posts, comments, leads, membership plans, forms and form inquiries, email lists and pages. Filtering on the get endpoints uses four parallel arrays, property, property_value, property_logic and property_operator, where each index across the arrays forms one clause and clauses tagged OR are grouped separately from the AND bucket, so getting precedence right matters more than the individual comparisons. Member updates are handled one record at a time, which makes bulk edits a loop rather than a batch. The category nouns of posts, pages and comments hold here, though members and leads are what most integrations actually care about. fastn stores each site's hostname and key, keeps the connection working and governs which models an agent may write.

Start freeBook a demo

In your product

Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.

Let a customer connect their own Brilliant Directories site so member data stays on their host and their key.

Sync directory members and their membership plans into your billing or CRM records.

Push leads captured elsewhere into the site's leads model so directory members receive them.

Publish or update member posts and pages from your own content workflow.

For your AI agents

Governed, audited access for the agents you build, through the MCP server.

Let an agent search members with the correct AND and OR filter clauses and return matches, with every write audited per tenant site.

Have an agent update a single member's profile fields when a change comes from another system.

Allow an agent to read leads and form inquiries without permission to delete members or plans.

Example prompt

Which members on our directory have expired plans but still have live listings?

Set up Brilliant Directories in 4 steps

  1. 01Enable the Brilliant Directories connector from your fastn dashboard.
  2. 02Have each customer authorise their own Brilliant Directories account, so calls run under their credentials rather than a shared key.
  3. 03Decide which posts, pages and comments your product needs, map those fields, then enable the actions and triggers you want.
  4. 04Call it from your product and expose it to your agents through the same governed connection.

Why teams use the Brilliant Directories integration

What you get by embedding it with fastn instead of building it yourself.

  • Ship a Brilliant Directories integration without building it. Your customers connect their own Brilliant Directories account inside your product and work their posts, pages and comments there, with no per-customer code on your side.
  • Handle the part that actually costs time: anything published is public immediately, and each network gates access behind its own review process. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Brilliant Directories update is not your on-call problem.
  • One integration serves your product and your agents. The same governed Brilliant Directories connection powers in-product features and gives AI agents scoped, audited access, so you publish and listen from inside your product instead of a separate social tool without wiring it twice.

Used by these teams

MarketingCustomer Support

Compare with

BufferHootsuiteFacebook

Often used alongside

Tools the same teams tend to run next to Brilliant Directories, across other categories.

SalesforceHubSpotPipedriveZoho CRM

Brilliant Directories integration FAQ

How do I add a Brilliant Directories integration to my product?

Enable the Brilliant Directories connector in your fastn dashboard, then let each customer authenticate their own Brilliant Directories account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Brilliant Directories client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

Do my customers each connect their own Brilliant Directories account?

Yes. Every connection is scoped to the individual customer, so each authorises their own Brilliant Directories account and only ever sees their own posts, pages and comments. 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 Brilliant Directories integration?

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent search members with the correct AND and OR filter clauses and return matches, with every write audited per tenant site.

Who maintains the Brilliant Directories integration?

fastn does. When Brilliant Directories 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 publish to a customer's own Brilliant Directories account?

Yes. Each customer authorises their own account, so a post goes out as them, under their permissions, never from a shared account you own. That also means a customer revoking access affects only their own connection.

Can I read engagement back from Brilliant Directories?

Yes. Comments, reactions and reach come back scoped per tenant, so your product can act on them or show them in your own reporting without one customer's numbers mixing with another's.

What can I build with the Brilliant Directories integration?

A common starting point: let a customer connect their own Brilliant Directories site so member data stays on their host and their key. 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 Brilliant Directories integration cost?

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Brilliant Directories does not change your per-connector cost. You can start free with 3 connected accounts.

Add Brilliant Directories to your product

Start free with 3 connected accounts. No sales call required, and no per-customer integration code.

Start freeRead the docs
← All integrations