BoldDesk Connector

Sync BoldDesk tickets, contacts, agents, activities, and chat conversations into your warehouse, with incremental sync on core ticketing objects.

SourceBronze

Start for Free View Documentation

Evaluating against Fivetran? See how Supaflow handles BoldDesk pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Read-Only API Key Authentication

Connect with a BoldDesk API key and your tenant domain. The connector is read-only and never creates, updates, or deletes data in BoldDesk. Use a dedicated licensed agent as a service account so the pipeline keeps running as individual agents come and go.

Incremental Ticketing Sync

Tickets, contacts, contact groups, agents, and activities sync incrementally on their last-updated time, so each run pulls only what changed. Supporting objects like brands, groups, roles, and ticket statuses run full refresh.

Lookback for Late Updates

BoldDesk stamps the updated time a few seconds after a record changes. An optional Lookback Period re-checks a trailing window on each run so edits made right at a sync boundary are not missed.

Custom Fields Included

Per-account custom fields on tickets, contacts, and contact groups are discovered on each schema refresh and land as typed columns in your warehouse, so account-specific data is preserved instead of dropped.

Chat Conversations and Messages

BoldDesk live chat conversations and their individual messages sync as their own tables, so you can report on chat volume and content alongside ticket activity.

Readable Lookups for Joins

Brands, groups, roles, ticket statuses, ticket priorities, and ticket sources sync alongside tickets, so you can turn the IDs on each ticket into readable names in your reporting.

Scheduled Schema Refresh

The connector re-discovers your BoldDesk schema, including newly added custom fields, on a cadence you choose. New fields flow into the warehouse without manual reconfiguration.

Supported Objects

Incremental

tickets

Support tickets, including custom fields.

contacts

End users and requesters, including custom fields.

contact groups

Groups that organize contacts, including custom fields.

agents

Help-desk agents in your account.

activities

Activity records associated with tickets.

Full Refresh

brands

Brands configured in your account.

groups

Agent groups used for ticket assignment.

roles

Agent roles and their definitions.

ticket statuses

The set of ticket statuses.

ticket priorities

The set of ticket priorities.

ticket sources

The channels tickets can arrive through.

chat conversations

Conversations from BoldDesk live chat.

chat messages

Individual messages within chat conversations.

Not Yet Supported

knowledge base articles, canned responses, ticket templates, satisfaction surveys, SLA policies, automation rules, email and notification templates, webhooks, audit logs

Not currently synced. Email support@supa-flow.io with the objects you need -- expansion is prioritized by customer demand.

How It Works

Create a BoldDesk API key

Sign in to BoldDesk as a licensed agent whose profile has the Manage API Keys permission. Click your profile avatar, choose View profile & Settings, open the API Keys tab, click Create API Key, enter an Identification Name, and copy the key immediately -- BoldDesk will not show it again. API keys require a paid BoldDesk plan.

Enter your domain and API key in Supaflow

Add a new BoldDesk source and enter your tenant host (such as mycompany.bolddesk.com) and the API key. The key is stored encrypted.

Configure advanced settings

Optionally set Schema Refresh Interval in minutes (0 means refresh before every run, which is right when custom fields change often) and a Lookback Period in seconds to re-check a trailing window on each incremental run.

Test and save

Click Test & Save. Supaflow verifies the connection and saves the source, then schema discovery runs so you can select objects in the pipeline wizard.

Use Cases

Support performance and SLA reporting

Land tickets alongside agents, groups, statuses, and priorities to build first-response and resolution-time dashboards, agent workload reports, and SLA attainment trends in your warehouse instead of exporting CSVs from BoldDesk.

Unified ticket and chat analytics

Combine tickets with chat conversations and messages to see the full support picture across channels, measure chat-to-ticket conversion, and analyze conversation content with warehouse-side enrichment.

Customer 360 with support context

Join BoldDesk contacts and tickets with CRM and product data already in your warehouse to give sales and success teams a complete view of each account, including open issues and recent support history.

Frequently Asked Questions

What objects does the BoldDesk connector sync?

Tickets, contacts, contact groups, agents, and activities sync incrementally. Brands, groups, roles, ticket statuses, ticket priorities, ticket sources, and chat conversations and messages sync with full refresh.

Does the connector sync BoldDesk custom fields?

Yes. Per-account custom fields on tickets, contacts, and contact groups are discovered on each schema refresh and land as typed columns. Other objects do not carry custom fields.

How does incremental sync avoid missing updates?

Tickets, contacts, contact groups, agents, and activities sync on their last-updated time. Because BoldDesk stamps that time a few seconds after a change, you can set a Lookback Period (for example, 60 to 300 seconds) to re-check a trailing window so boundary edits are not missed.

What permissions does the API key need?

The key must belong to a licensed BoldDesk agent whose profile has the Manage API Keys permission, with read access to the objects you want to sync. The connector never writes to BoldDesk. For long-term stability, use a key from a dedicated licensed agent (a service account) rather than an individual so the pipeline does not break if that person leaves.

Can I sync knowledge base articles, SLA policies, or satisfaction surveys?

Not yet. The connector focuses on tickets, contacts, agents, activities, and chat. Knowledge base articles, canned responses, ticket templates, satisfaction surveys, SLA policies, automation rules, templates, webhooks, and audit logs are not currently synced. Email support@supa-flow.io with what you need.

How does the connector handle BoldDesk rate limits?

BoldDesk applies API rate limits per minute and per hour. Supaflow retries automatically with backoff when a request is rate-limited, but very large initial syncs can take longer and may benefit from off-peak scheduling or narrower object selection.

Can I run the BoldDesk pipeline natively inside Snowflake?

Yes. Supaflow runs as a Snowflake Native App via Snowpark Container Services, so your BoldDesk data is extracted and loaded without leaving your Snowflake account. See our Snowflake Native ETL guide for details.