BeBranded avatar
Integrations · API

Connect BeBranded to Well

Push company record, person record, invoice, and document into Well through BeBranded, ready to query and act on in your workspace.

What Well pulls from BeBranded

BeBranded feeds company record, person record, invoice into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke BeBranded’s access.

From BeBrandedIn Well
Company record
Customer
Person record
Contact
Invoice
Receivable
Document
Source document
BeBranded avatar
Sync mode
incremental polling
Refresh
scheduled
Direction
BeBranded → Well

What Well does with your BeBranded connection

Connect

Connect BeBranded over API key: you generate a BeBranded key and paste it into Well, where it is stored encrypted at rest and never returned in responses.

Sync

Well brings company record, person record, and invoice in from BeBranded on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each BeBranded entity into customer, contact, and receivable, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from BeBranded lands in the workspace as customer, contact, and receivable you can search, chart, and automate.

Questions BeBranded unlocks

Ask in plain language. Well answers from your connected BeBranded connection, resolved against the rest of your stack.

Ask Well

Ask anything about your BeBranded connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your BeBranded connection…

1 agent skill runs on BeBranded.

Well lists BeBranded in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connect BeBranded in three steps

  1. 01

    Generate an BeBranded API key

    In BeBranded, generate an API key with the scopes Well lists in the trust section below. In Well's Connections > BeBranded, paste the key. Well validates it against BeBranded's API and confirms with a sample fetch.

    • AuthAPI key
    • Validationsample fetch on save
  2. 02

    Map your entities

    Well brings company record, person record, invoice, and document from BeBranded into your workspace using the canonical mappings defined in Well's data-views layer.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Use what you bring in from BeBranded in conversation, records tables, or agent runs. Rotating the key in BeBranded requires updating the key in Well; nothing else.

    • First syncstarts as soon as connect completes

Keys are never returned in API responses. Rotate freely; Well will prompt for the new key.

How BeBranded stays secure with Well

Well calls BeBranded with the API key you provision, scoped to company record, person record, invoice, and document. The key is never logged and never returned in API responses. BeBranded validates the key on every request; rotating the key in BeBranded immediately invalidates Well's access. No write access unless the key explicitly grants it.

API keyEncrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requests
  • Read BeBranded records

    Endpoints the BeBranded API token grants, scoped by your consent.

    granted
  • Resolve company record, person record, invoice, and document across your stack

    Match identifiers in BeBranded against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete BeBranded records

    Not granted; BeBranded is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Read API keys from BeBranded's settings

    Well only sees the keys you paste in. The keys never leave Well's secret store back to BeBranded's admin surface.

    refused
Disconnect any time from Well settings or BeBranded’s admin panel.

Frequently asked questions about BeBranded and Well

How do I connect BeBranded to Well, and how long does it take?

In BeBranded, generate an API key with read access (scoped to what's listed in the security section below). In Well, open Connections > BeBranded, paste the key, and save. Well validates the key against BeBranded's API and pulls a first sample as confirmation.

What does Well pull into the workspace from BeBranded?

Well brings in company record, person record, invoice, and document from BeBranded and reshapes each entity into your workspace: company record becomes customer; person record becomes contact. Every record arrives with the source identifier preserved, so BeBranded stays the source of truth while Well lets you query the data alongside the rest of your stack.

What does BeBranded unlock once it is connected to Well?

Once BeBranded is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its BeBranded source, so you can always trace a workspace record back to the original.

What happens when BeBranded updates a company record that Well already pulled in?

Well watches for updates to company records and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right customer. Edits flow in incrementally; nothing is duplicated, and the BeBranded source identifier is retained on every revision.

How often does BeBranded sync with Well, and what triggers a refresh?

Well polls BeBranded regularly for company record, person record, invoice, and document. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on BeBranded's side stays modest.

Can I disconnect BeBranded and what happens to the data Well already pulled?

Open Connections > BeBranded in Well, click Disconnect, then rotate the API key on BeBranded's side. Well stops calling BeBranded as soon as you disconnect; rotating the key on the provider's side guarantees Well cannot resume access. The company record, person record, invoice, and document already synced stay in your workspace until you ask Support to purge them.

How does Well protect what it pulls in from BeBranded?

The BeBranded records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.

BeBranded avatar

Ready to build with the BeBranded?

Connect once. Every company record, person record, invoice from BeBranded becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.