View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

BoldBellowsAcuity Scheduling to Salesforce automation for multi-location businesses that measure acquisition

Acuity Scheduling to Salesforce automation that upserts each client by External ID, records where they heard of you from the intake form, and attaches the right campaign status

Acuity Scheduling to Salesforce automation tells a growing business where its clients come from. An intake form can ask how a client found you and returns the answer in the appointment's forms array, while a Salesforce CampaignMember can only take a status that the campaign defines. BoldBellows holds the service, the calendar and the appointment as one identity, holds the change until the appointment has stopped changing, then fetches the appointment, finds or creates the Lead or Contact under an External ID, records the source, and adds the campaign member at the status you chose.

View Pricing

One-off setup from $870
No monthly subscription

  • Record Acuity client sources in Salesforce
  • Upserted by External ID
  • Campaign status set correctly
An Acuity client upserted into Salesforce by External ID with the intake-form source and a campaign member status, built by BoldBellows
Acuity Scheduling to Salesforce: synced, zero duplicate recordsStatus chip: a wax seal marks the org as synced 2 minutes ago with zero duplicate records.SIGNED OFFSynced 2 min ago0 duplicate records
Plate I. An Acuity intake answer upserted into Salesforce as a Lead with its campaign source.
  • Upsert, not insert an External ID turns a repeat into an update
  • Source recorded the intake answer becomes the lead source
  • Valid statuses only a campaign member gets a status its campaign defines
  • Lead or Contact the path follows what Salesforce already holds
  • No lock-in The configuration stays yours if you stop working with us
  • Paid one time starting at $870, with the runbook handed over as a PDF

Chapter 01 the unknown-source problem

A booked client whose source nobody recorded is a marketing budget you cannot measure

The intake form asks how the client found you. The answer stays in Acuity, so the marketing team spends on channels without knowing which of them produce bookings. When someone exports it, the client is created as a new Lead beside an existing Contact, the campaign membership is rejected for a status the campaign does not define, and a retried integration inserts the record again.

We knew who booked and never why they had chosen us.

From a business-development review

A budget with no attribution

The source answer stayed in Acuity.

A Lead beside a Contact

The export ignored what was already there.

A campaign status refused

The status was not one the campaign defines.

Before

Before Acuity Scheduling to Salesforce automation: manual bookings exports, duplicates and broken formulasThe old way: a Monday calendar page saying rebuild the report, struck-through drafts and crumpled paper balls, and a note asking who has the latest file.MONDAY8:47rebuild the reportTotal for SepReschedules (check)Which bookings?Availability countsWho has thelatest one?
Fig. 2a. A booking with no source.

After

After Acuity Scheduling to Salesforce automation: one clean org that matches Acuity SchedulingThe new way: a printed weekly report with net bookings of 1842, up 8.2 percent, a daily bar chart and a seal marking it as matching Acuity Scheduling.THE WEEKLY REPORTKept bookings are up18421847up 8.2% on last week · matches Acuity SchedulingMTWTFSS“BusiestFriday yet”
Fig. 2b. A lead with its campaign.

Before

  • The same change can land more than once
  • Source answers stay in the booking system
  • Imports duplicate existing people

After

  • What is already there is found by a Salesforce External ID holding the Acuity client ID on each Lead and Contact, with a CampaignMember for the source
  • Each client's source is recorded on the lead
  • Campaign membership uses valid statuses

Chapter 02 How it works

How an Acuity client becomes a Salesforce lead with a source and a campaign status

What reaches Salesforce has passed a rule, a key check and a search.

How Acuity Scheduling to Salesforce automation works: bookings in, one clean record each, on a scheduleYour Acuity Scheduling account, drawn as a seed packet, sends bookings through read-only access to the sync we build, a sprouting engine, which writes one record per booking into your Salesforce org, drawn as a full bloom.ACUITY SCHEDULINGBOOKINGSYour Acuity Scheduling accountBookings, clients,services, reschedules,cancellationsThe sync we buildAdds new bookings, fixesedited ones, double-checkson a scheduleYour Salesforce orgBookings, reports, dailytotals, reportsREAD-ONLYACCESSONE RECORDPER BOOKINGHow Acuity Scheduling to Salesforce automation works: bookings in, one clean record each, on a schedule, stacked: your Acuity Scheduling account, the sync we build, then your Salesforce org.ACUITY SCHEDULINGBOOKINGSYour AcuitySchedulingaccountBookings, clients,services, reschedules,cancellationsThe sync webuildAdds new bookings,fixes edited ones,double-checks on aYourSalesforce orgBookings, reports,daily totals, reportsREAD-ONLYACCESSONE RECORDPER BOOKING
Fig. 3. The External ID turns a repeat into an update.

Open the event properly

Identifiers and time are recorded, the source state is read and the appointment event is assessed against the route brief.

Verify, fetch, look up

With the signature confirmed, the appointment is retrieved along with the intake form, and Salesforce is searched for an existing Contact or Lead by email.

Upsert, source, campaign

The record is upserted under its External ID, the source is written, and the campaign member is added at a status the campaign defines.

Platform notes behind the Salesforce route

  • Services and calendars are separate: An appointment type is the service and a calendar is the person or place providing it, and the route keeps both IDs because the same service can run on several calendars.
  • Statuses belong to the campaign: A Salesforce CampaignMember accepts only a status that its campaign defines, so the route reads the campaign's list first and never sends a status Salesforce would refuse.
  • Safe to repeat: Repeating an event is harmless because Salesforce is consulted through a Salesforce External ID holding the Acuity client ID on each Lead and Contact, with a CampaignMember for the source before any change.

Chapter 03 What ships in the build

The pieces that make Acuity Scheduling to Salesforce dependable

Clear is the minimum for live use; Careful and Continuous add the parts that matter once volumes grow.

What lands in your org: bookings, reports and reports from Acuity SchedulingAppointment types and availability report in Salesforce on ledger paper, with open slots counts, level gauges and two appointment types flagged as underbooked.APPOINTMENT TYPES & AVAILABILITYWhat's on the shelf2 RUNNING LOWAPPOINTMENT TYPEServiceON HANDLEVELStrategy sessionSVC-STRAT208Site tourSVC-STRAT96Check-upSVC-CONSU24LOWFittingSVC-WORKS58OnboardingSVC-STRAT11LOWWorkshopSVC-INTRO74Trial classSVC-FOLLO140BookingsIntake answersAppointment types & availabilityReschedulesDepositsDaily bookingsDashboard

Entry rule checker

Tests every event against the entry rule and records which clause it passed or failed.

Clear

Stable identity ledger

Remembers which Salesforce item came from which Acuity Scheduling record, and when it last changed.

Clear

Redaction rules

Applies redaction rules for sensitive Acuity Scheduling values before anything leaves for Salesforce.

Clear

Lead and Contact upserter

Chooses the Lead or Contact path from what Salesforce holds and upserts under the External ID.

Careful

Source and campaign mapper

Maps each intake answer to a lead source and each location to a campaign and member status.

Careful

External-ID guard

Writes the Acuity client ID into the External ID field and holds a multiple-match answer for review.

Careful

Lead register

Turns silent drift between Acuity Scheduling and Salesforce into a short, dated worklist.

Continuous

Campaign and rule watch

Notices a changed duplicate rule or a removed member status before the next upsert is refused.

Continuous

Open-case summary

Gives the route owner a short summary of open cases and their ages.

Continuous

Whether it is acuity scheduling Salesforce opportunity, acuity scheduling to Salesforce or acuity scheduling Salesforce contact create, start here. Related searches include acuity scheduling to Salesforce consultant, acuity to Salesforce without Zapier, acuity Salesforce integration, sync acuity scheduling appointments to Salesforce, acuity scheduling Salesforce integration, Salesforce campaign member from acuity, acuity webhook Salesforce, acuity lead source Salesforce, acuity scheduling to Salesforce duplicate prevention, acuity scheduling to Salesforce error handling, acuity scheduling to Salesforce implementation, acuity intake form Salesforce, acuity scheduling bookings Salesforce mapping, acuity scheduling Salesforce CRM sync, acuity scheduling to Salesforce historical migration, acuity scheduling Salesforce workflow, acuity scheduling to Salesforce service, acuity scheduling Salesforce lead capture, acuity scheduling to Salesforce Zapier, acuity scheduling Salesforce automation and send acuity clients to Salesforce.

Chapter 04 Who this fits

For driving and flight schools booking lessons through Acuity Scheduling, then for those who record where each client heard of you and move them into the right campaign

Acuity records who booked and how they found you; Salesforce is where that becomes attribution.

Marketing director

"Which channels bring clients?"

The intake source lands on the lead, so attribution is a report.

Salesforce admin

"Respect my duplicate rules and statuses."

The route reads campaign statuses and rule outcomes, and never forces a record past them.

Location manager

"Our site, our campaign."

Each location maps to its own campaign.

Account executive

"Is this person already known?"

Existing Contacts are updated, so you see one history and not a fresh Lead.

Agency owner

"Each client has an org."

A business's clients reach only that business's Salesforce org.

Founder

"Spend where it works."

Marketing spend follows real bookings.

Chapter 05 The options

A CSV import, zap or a source-aware lead route: which carries Acuity Scheduling into Salesforce?

Each can create a record. Only one upserts it, records the source and uses a valid campaign status.

Comparison table: A CSV import, zap or a source-aware lead route: which carries Acuity Scheduling into Salesforce?
Question a CSV import A free-form Salesforce zap BoldBellows, centred on a source-aware lead route
What starts the work Somebody with a spare minute Events without a qualification step An appointment event matching the route brief
How identity is decided Hunted through both tools Email alone A Salesforce External ID holding the Acuity client ID
What reaches Salesforce Whatever seemed important One row of raw values One Lead or Contact per client with source and campaign member status
After an uncertain result Left for the next person Reports an error, nothing more Searches, compares, repairs or hands to a named owner
By handAutomatedTime each week3 hours10 minErrors a month120Files to juggle371

Late event, settled state

A notice that arrives after the record has moved on is logged and closed; the lead in Salesforce stays correct.

An intake answer names a source that has no matching lead source

The record is saved with the source held in a text field, the unmapped answer is flagged to marketing operations, and nothing is refused or lost. The verdict comes from a Salesforce External ID holding the Acuity client ID on each Lead and Contact, with a CampaignMember for the source: absent, matching, differing or ambiguous, all recorded. The result is recorded either way, so the decision can be audited.

A Salesforce External ID holding the Acuity client ID on each Lead and Contact, with a CampaignMember for the source goes in first, then the mapping, then the branches.

Interlude Priced by leads, contacts and campaigns

How much is Acuity Scheduling to Salesforce? Answer it here

Work out the cost yourself in about two minutes. The Clear package begins at $870 and nothing is billed afterwards.

View Pricing

One setup fee · Range shown first

Pricing

Build your Acuity Scheduling to Salesforce price

Pick a package, answer three short questions about how Acuity Scheduling data should reach Salesforce, and your price and turnaround move as you choose.


Choose your packageRequired

The three packages differ by how much routing, reconciliation and governance sits around the Acuity Scheduling to Salesforce route.

A focused production route for one Acuity Scheduling environment and one Salesforce destination, delivering Salesforce Leads and Contacts upserted by External ID from Acuity clients, with the source taken from the intake form and a CampaignMember added at the right status with identity and failure controls from day one.

  • One approved Acuity Scheduling event family and business-state admission rule within the Acuity Scheduling to Salesforce service.
  • One authorized account, workspace, organization, or base boundary within the Acuity Scheduling to Salesforce service.
  • One Salesforce object contract with field and relationship mapping within the Acuity Scheduling to Salesforce service.
  • Stable matching through owner account plus appointment ID and calendar ID and a Salesforce External ID mapped to the source identity
  • Tests for duplicates, stale events, malformed data, denied access, and timeouts within the Acuity Scheduling to Salesforce service.
  • Implementation map, test record, and premium PDF operations handover within the Acuity Scheduling to Salesforce service.

Adds branching, matching and a bounded historical pass for teams whose route into Salesforce cannot be one straight-through action, while still delivering Salesforce Leads and Contacts upserted by External ID from Acuity clients, with the source taken from the intake form and a CampaignMember added at the right status.

  • Everything in Signal
  • Up to four approved routing or state-transition branches within the Acuity Scheduling to Salesforce service.
  • Existing-record resolution and one bounded historical checkpoint within the Acuity Scheduling to Salesforce service.
  • Lookup-before-replay protection for uncertain writes
  • Named exception ownership and a decision-ready evidence packet within the Acuity Scheduling to Salesforce service.
  • Field, permission, and destination-state validation before mutation within the Acuity Scheduling to Salesforce service.

Adds reconciliation and governance for teams that now depend on Salesforce Leads and Contacts upserted by External ID from Acuity clients, with the source taken from the intake form and a CampaignMember added at the right status, with drift detection and an exception register for Salesforce.

  • Everything in Routing
  • Scheduled source-to-destination reconciliation
  • Schema, field, scope, and webhook drift checks within the Acuity Scheduling to Salesforce service.
  • Volume-aware retry ceilings and stale-event protection
  • Aged-exception reporting with ownership status
  • Thirty-day release watch and operating review

For Acuity Scheduling to Salesforce, multi-business-unit routing, unrestricted bidirectional synchronization, regulated archives, unsupported extensions, or additional destination systems receive a separate written quote. Third-party subscriptions and usage charges are excluded.

Which Acuity Scheduling events should reach Salesforce?Required

Governed lifecycle set: Use this when several approved Acuity Scheduling transitions must converge on one Salesforce record.

How should Salesforce recognise an Acuity Scheduling record it has already handled?Required

Ambiguity queue: Route zero-match and multi-match cases to an owner instead of letting Salesforce guess.

Which Acuity Scheduling events should reach Salesforce?Required

Managed repair case: Capture evidence, ownership and a safe next action whenever a Salesforce write is uncertain.

How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your rollout needs, watch the total, switch it back off.

Chapter 06 The process

Six steps from a booking to measured acquisition

No surprises: six steps, with the output of each one agreed in advance.

  1. About 30 minutes

    Choose the source map

    We agree which intake question records the source, how answers map to lead sources and which campaign each location uses.

  2. Access review

    Approve access

    We link Acuity Scheduling and Salesforce through supported interfaces and record exactly what each connection can do.

  3. Most of the project

    Agree objects and rules

    The External ID field, the Lead-or-Contact rule, the member statuses and the duplicate-rule handling are written down and signed off.

  4. Before you review

    Prove it on a copy

    Every path, including the failing ones, is run against a copy of Salesforce before production is switched on.

  5. Handover day

    Launch with notes

    Launch is a checkpoint, not a cliff: the route starts from a known point and the notes arrive with it.

  6. About 30 minutes

    Live check-in

    In the Acuity Scheduling to Salesforce route, we compare live behaviour with the brief and update the handover wherever reality differed.

Chapter 07 Turnaround

Turnaround by package, in business days

Timing begins when both connections are approved.

Clear

6 to 10 business days

Careful

10 to 16 business days

Continuous

16 to 24 business days

Chapter 08 Getting started

The short list we need from you

Access to Acuity Scheduling sufficient to read the fields we agree

A Salesforce user who can create the External ID field and authorise the app, plus Acuity credentials

Approval to read the Acuity Scheduling fields listed in the map

Your current manual steps for this appointment event, so we can match them

Who signs off the handover notes at the end

A backup contact for approvals

Chapter 09 Trust

Secure by being small: few fields, few permissions

Scope is deliberately narrow: approved Acuity Scheduling fields in, one Salesforce destination out, no side stores.

Read-only Acuity Scheduling to Salesforce access: your data stays yoursA brass keyhole plate with a key turning in it and a key ring of tags for you, your team and your accountant, marked named people only and read-only.YouTeamAccountantNAMED PEOPLE ONLY · READ-ONLY

Only what the platforms allow

Every action taken in Acuity Scheduling and Salesforce is one their own documentation supports; nothing relies on an unofficial shortcut.

Scoped, revocable access

Tokens cover only the named objects and can be revoked whenever you choose.

A deliberately small payload

Keeping the payload small reduces risk and makes each write to Salesforce faster to check and easier to repair.

Reconcile, do not resend

A retry reconciles what Salesforce already holds against what was intended, then writes only the difference.

Minimal logging

We record what happened and when, never the private details of your records.

Full handover

Everything we built is documented and belongs to your team.

"A lead is only useful if it knows where it came from, so the build records the source from the intake form."

Steven GrratFounder, BoldBellows

Chapter 10 In their words

What BoldBellows clients say

Verified reviews from business owners who use BoldBellows automations every day, from marketing and data to support and operations.

AI Workflow Automation for Agencies

Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.

Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.

Samuel BoatengVerifiedAccra, Ghana

AI CRM Automation

Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.

Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.

David KimVerifiedSeoul, South Korea

AI Translation & Localisation

When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.

The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.

Kenji NakamuraVerifiedOsaka, Japan

AI HR & Recruitment Automation

Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.

It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.

Olivia MartinezVerifiedAustin, USA

AI Accounting & Invoice Automation

BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.

Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.

Ravi PatelVerifiedNew Delhi, India

AI Data Entry & Reporting Automation

We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.

The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.

Sarah MüllerVerifiedZurich, Switzerland

AI E-commerce Listings Automation

BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.

It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.

Pedro LimaVerifiedSão Paulo, Brazil

AI Customer Journey Automation

We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.

It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.

Nadia HassanVerifiedCairo, Egypt

AI Document & Contract Automation

Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.

What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.

Michael O’ConnorVerifiedDublin, Ireland

Chapter 11 Questions

Acuity Scheduling and Salesforce: what marketing operations ask

What to know before choosing a package, in plain language.

Is access read-only?Who owns the result?What happens after handover?Can it be changed later?Open any question
Is a build better than an Acuity Scheduling to Salesforce Zapier task?

A zap delivers a lead for every booking. It leaves you to upsert the client under an External ID, record the source from the intake form and attach the right campaign status. It is that layer the packages price.

How do I get Acuity clients into Salesforce with their source?

Each client is upserted as a Lead or Contact under an External ID, with the source taken from the intake form and a campaign member added.

What are campaign member statuses?

Each campaign defines the statuses a member can have. The route reads them first and only uses one that exists, such as Booked or Attended.

How is the right person found?

Contacts are searched by email first, then Leads. A Lead is created only when no one matches, and an unclear match is held for review.

Are duplicate rules respected?

Yes. The route never forces a record past a rule. A refusal is recorded with its reason and the booking is flagged.

Can past clients be loaded?

Yes. Existing clients are upserted in checkpointed batches using the same External ID rule.

Can Salesforce edits affect the appointment?

No. Nothing flows back, so changes in Salesforce never alter Acuity.

How detailed is the field map?

Yes. The Acuity Scheduling Salesforce field mapping service is where we agree formats, required values and owner rules before any build work starts.

Can we send some records elsewhere?

Yes. Our packages assume a custom Acuity Scheduling workflow for Salesforce, and the consultancy is included: an Acuity Scheduling Salesforce integration consultant on your side from $870.

What if either platform updates its API?

The safest reaction to change is to stop and report, so that is what the route does. Ongoing maintenance beyond the review period is separate.

Give Salesforce clients that arrive with their source

Your brief sets the scope, your answers set the price. To automate Acuity Scheduling data to Salesforce with us starts at $870.

  • From $870, paid once
  • Source recorded
  • Valid statuses
  • No monthly fee from us