Integrations & API Connectivity

Connect your systems. Keep your data moving.

Brilliance One connects CRM, ERP, CMS, communications, payments, AI, security, marketing, documents, reporting, and operational workflows through an API-first platform designed to reduce disconnected systems.

Use Brilliance-managed providers where they make sense, connect supported third-party services, or bring your own API credentials where available. The goal is practical interoperability without forcing every customer into one vendor path.

Explore Providers View Integration Core
API First • Provider Flexible • BYO API • Connected Workflows
Brilliance One integrations and API connectivity platform

Integration Philosophy

Your technology should connect. Not create another silo.

Brilliance One is designed to act as the operational layer between customer records, business workflows, external providers, websites, communication channels, payments, automation, and reporting.

Connect

Bring External Services Into the Workflow

Connect supported providers for communications, payments, AI, marketing, security, documents, reporting, and other operational services.

Control

Keep Provider Choice Flexible

Brilliance-managed services can provide convenience while supported bring-your-own-provider models can give customers more control over vendors, accounts, pricing, and infrastructure.

Automate

Turn Connectivity Into Action

Integrations become more valuable when external events and data can trigger communication, workflows, updates, tasks, records, reporting, and other operational activity.

API-First Architecture

Built to connect. Not built to trap you.

Brilliance One is designed around APIs so business data and platform capabilities can participate in broader technology ecosystems instead of requiring every workflow to remain isolated inside one user interface.

  • API-driven platform services
  • Authenticated endpoints
  • External provider integrations
  • Workflow-triggered actions
  • Data synchronization
  • Customer-specific credentials
  • Integration configuration
  • Structured request and response models
  • Operational logging
  • Expandable provider support

Platform Connectivity

The API should be part of the product, not an afterthought.

An API-first approach gives Brilliance One a foundation for integrations, automation, customer applications, portals, external services, mobile experiences, partner ecosystems, and future platform expansion.

Provider Standards

Managed providers when useful. Your providers when supported.

Brilliance One can provide managed connectivity for selected services while also supporting customer-owned API credentials for compatible providers. This gives organizations a path between convenience and direct vendor control.

Email Delivery

MailerSend SMTP

Email-delivery infrastructure for transactional messaging, campaign communication, and other supported business email workflows.

Brilliance Managed $0.00255 per email based on the current configured service rate.
Provider Choice Bring-your-own API capability is available where supported.

Threat Intelligence

Brilliance Security Firewall

Internal security workflows can evaluate IP reputation, suspicious activity, dark-web-related intelligence, and other available risk signals as part of broader security decision-making.

Platform Capability Included as part of applicable Brilliance security workflows.

Payment Tokenization

Brilliance Payment Vault

Payment-token workflows can help preserve reusable payment references across supported payment processors while reducing unnecessary direct handling of card information.

Platform Capability Available within supported payment workflows.

Bring Your Own Provider

Your vendor. Your credentials. Your choice.

Where supported, customers can connect their own third-party provider accounts instead of being required to purchase every external service through Brilliance.

  • Customer-owned provider accounts
  • Customer-specific API credentials
  • Provider-specific configuration
  • Credential protection
  • Integration testing
  • Connection status visibility
  • Controlled provider access
  • Account-specific usage
  • Provider replacement options
  • Reduced vendor lock-in

Provider Flexibility

Technology should be a choice, not a contract.

When a business already has a preferred provider, negotiated pricing, established account, compliance requirement, or infrastructure relationship, supported BYO-provider connectivity can help preserve that investment.

Integration Categories

Connect the systems your business already depends on.

Brilliance One is designed to support integration categories that affect daily operations, customer engagement, financial workflows, security, marketing, reporting, automation, and business growth.

Communications

Email, SMS, MMS, phone, deliverability, suppression, verification, campaign, and communication providers.

Payments

Payment processors, tokenization, invoices, recurring billing, merchant services, and transaction-related workflows.

Security

Authentication services, IP intelligence, reputation data, risk signals, validation, monitoring, and security-oriented provider data.

AI

AI models, content generation, enrichment, classification, workflow assistance, analysis, and operational intelligence.

Marketing

SEO data, analytics, campaign providers, advertising platforms, UTM tracking, short links, reputation, and local visibility services.

Commerce

Product catalogs, eCommerce platforms, inventory updates, marketplaces, orders, fulfillment, and related commerce workflows.

Documents

Storage, signing, file processing, secure delivery, document generation, versioning, and external document services.

Reporting

Analytics, dashboards, business intelligence, exports, data pipelines, metrics, and external reporting systems.

Calendars & Scheduling

External calendars, appointment systems, scheduling providers, availability data, and meeting-related integrations where supported.

Connected Workflows

Integrations should do more than move data.

The real value of connectivity comes when external systems can participate in business processes instead of simply existing as another data source.

1

Connect

Authenticate the provider, configure access, define the appropriate data scope, and establish the connection.

2

Synchronize

Exchange appropriate information between Brilliance One and the connected provider according to the integration design.

3

Automate

Use connected data and provider events to trigger communication, records, tasks, workflow actions, reporting, or other operational processes.

Communication Providers

One customer record. Multiple communication channels.

Communication integrations can connect external delivery services with Brilliance One customer records, automation, campaigns, notifications, and communication history.

  • Email delivery
  • Transactional email
  • Marketing email
  • SMS
  • MMS
  • Phone-related services
  • Email verification
  • Suppression data
  • Delivery activity
  • Communication history

Connected Communication

The provider delivers the message. Brilliance keeps the business context.

External communication providers can handle specialized delivery while Brilliance One connects that activity with the account, contact, campaign, automation, customer history, and workflow behind the message.

Payment Integrations

Keep payment providers connected to the customer relationship.

Where payment capabilities are configured, Brilliance One can connect supported processors with customers, invoices, subscriptions, orders, POS activity, accounting workflows, and reusable payment-token references.

Payment Providers Connect supported processors according to the capabilities available for each provider.
Tokenization Use supported tokenized references to reduce unnecessary direct handling of reusable payment credentials.
Invoices Connect payment activity with invoice-related workflows where Accounting capabilities are enabled.
Recurring Billing Support recurring-payment and subscription-related workflows where available.
POS Connect supported payment providers with point-of-sale and order workflows where configured.
Transaction History Maintain appropriate payment activity alongside the business records that created it.

AI Connectivity

AI should understand the business context.

AI providers become more useful when their capabilities can participate in controlled workflows rather than operating as isolated chat interfaces.

  • Content generation
  • Classification
  • Summarization
  • Operational assistance
  • Workflow decisions
  • Data enrichment
  • Customer communication assistance
  • Reporting assistance
  • Business-context prompts
  • Configurable AI workflows

Controlled AI

The model is one component. The workflow belongs to the business.

Brilliance One can provide the business context, permissions, workflow rules, and operational boundaries surrounding an AI provider rather than allowing the external model to become the system of record.

Integration Security

Every connection creates a trust boundary.

External integrations expand what a platform can do, but they also introduce credentials, permissions, external availability, data transfer, provider behavior, and additional security considerations.

Credential Protection

API credentials and integration secrets should be protected rather than exposed through ordinary application content or frontend code.

Minimum Access

Connections should request only the access and data scope needed for the intended integration where provider capabilities allow it.

Authentication

Integrations should use supported authentication and authorization mechanisms appropriate to the external provider.

Logging

Operational logging can help identify connection failures, unexpected activity, provider errors, and synchronization problems.

Failure Handling

Integration workflows should account for unavailable providers, invalid credentials, rate limits, timeouts, and unsuccessful requests.

Provider Review

External providers can be evaluated according to their purpose, security posture, data handling, reliability, cost, and operational fit.

Data Flow

Connect data without losing ownership of the workflow.

An external provider may supply specialized functionality, but Brilliance One can remain the operational system connecting that provider back to customers, products, invoices, projects, campaigns, communication, and other business records.

  • Customer context
  • Account context
  • Provider request data
  • Provider response data
  • Synchronization status
  • Workflow activity
  • Operational history
  • Error handling
  • Audit-oriented visibility
  • Business reporting

System of Record

Integrate specialized services without fragmenting the business.

Brilliance One can coordinate external systems while keeping business context, customer history, workflow state, and operational relationships inside the broader platform.

Integration + Automation

When systems connect, workflows can react.

External provider activity can become significantly more valuable when it can participate in automated business processes.

Communication

Trigger email, SMS, notifications, or internal communication after configured provider or business events.

Record Updates

Update appropriate business records when external provider data changes or synchronization completes.

Assignments

Create tasks or internal notifications when integration activity requires human review.

Reporting

Bring available provider activity into broader operational reporting and dashboard workflows.

Error Handling

Surface failures so integration problems can be investigated instead of silently disappearing.

Follow-Up

Use provider activity as another signal for customer, sales, service, marketing, or operational follow-up.

Brilliance One Core

One operational foundation for connected services.

The Brilliance Core System provides the shared accounts, communication, automation, users, security, settings, and platform services that allow external provider connections to participate in the same business environment.

Core Workspace

Workspace modules. The shared foundation of Brilliance One.

Manage the core relationship, communication, automation, security, administration, and user capabilities that support the rest of your Brilliance One workspace.

Accounts

Accounts

Centralize customers, leads, vendors, partners, organizations, and contacts in one connected relationship record with communication history, activity, documents, tasks, financial context, and operational workflows.

Learn about Accounts

Automations

Automations

Build repeatable workflows that handle routine follow-up, trigger communications, apply actions, and move work forward based on defined business events and timing.

Learn about Automations

Addresses

Addresses

Store and organize physical locations for customers, vendors, facilities, offices, service locations, and other business relationships so address data stays connected to the records and workflows that use it.

Learn about Addresses

Communications

Communications

Manage email, SMS, MMS, replies, templates, campaigns, delivery activity, and communication history while keeping conversations connected to the customers, contacts, and workflows behind them.

Learn about Communications

Security

Security

Protect business and customer data with authentication, role-based permissions, security groups, controlled access, audit visibility, privacy-oriented controls, and security practices that extend across the Brilliance One platform.

Learn about Security

Settings

Settings

Configure organization-wide preferences, branding, defaults, system behavior, connected services, and other administrative options that shape how Brilliance One works across your business.

Learn about Settings

Tools

Tools

Access practical utilities for imports, exports, validation, data management, operational cleanup, and other administrative workflows that help teams maintain accurate information and work more efficiently.

Learn about Tools

Users

Users

Manage user identities, roles, permissions, security access, and workspace responsibilities so each person can access the Brilliance One capabilities and information appropriate to their role.

Learn about Users

Integration Principles

Connect. Control. Automate.

1

Connect What Matters

Integrate external systems when they provide useful specialized functionality or important business data.

2

Keep Operational Control

Protect credentials, control access, understand data movement, monitor failures, and preserve the business context around the integration.

3

Turn Data Into Work

Use provider activity to support automation, customer communication, reporting, tasks, decisions, and connected business workflows.

Brilliance One Integrations

Your systems. One connected operation.

Connect communications, payments, AI, security, marketing, documents, commerce, reporting, calendars, and specialized providers with the CRM + ERP + CMS platform running the business behind them.

Discuss an Integration Explore the Platform

Brilliance One • API First • Provider Flexible • Connected by Design