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

Botpress to Salesforce automation for sales teams that run on Salesforce

Botpress to Salesforce automation that upserts leads on an external ID, logs the conversation and routes the owner by your rules

Botpress can run JavaScript in an Execute Code card and send requests to an outside API with Axios, so reaching Salesforce's REST API through a connected app is a matter of design and not of plugins. BoldBellows notes the email, the campaign and the conversation ID before a lead is written, upserts on an external ID so a repeat finds the same lead, then upserts the lead on an external ID field so a repeat visit finds the same record, writes the source and campaign, logs the conversation summary as a task with a link to the transcript, routes the owner by territory or round robin, flags a lead whose email already belongs to a contact so it can be reviewed and not duplicated, and uses collection requests when a backlog arrives.

View Pricing

From $870, paid once. Send Botpress to Salesforce.

Botpress to Salesforce automation that upserts leads on an external ID logs the conversation as a task routes the owner by your rules and stays inside Salesforce API limits, built by BoldBellows

The standards the Botpress route is held to

  • Upsert on external ID one lead each
  • Conversation logged as a task
  • Owner routed by your rules
  • Existing contacts flagged not duplicated
  • Honest reporting Failed runs are reported with their cause, not hidden
  • One invoice from $870, invoiced once, with documentation included

01 · the duplicate-lead problem

A new lead for every chat and an org full of duplicates

A chatbot connected with a create step adds a lead every time someone types an email, including customers who already exist as contacts. Reps then chase a customer as a new prospect, and reports count the same person twice. The conversation stays in the bot, so the first conversation starts from nothing, and ownership depends on whoever notices the lead first. Sending records one at a time uses up the daily API allowance on a busy launch.

Duplicate leads

Every chat created one.

A customer chased as a prospect

Contacts were not checked.

Reps starting blind

The conversation stayed in the bot.

Before Botpress to Salesforce automation: manual messages exports, duplicates and broken formulasThe old way: an avalanche of near-identical export files piling up, with the question of which one is the latest.EXPORTS · INCOMING37 files38 files.csvmessages.csvqueue.csvFINAL.csvqueue.csvFINAL.csvv2.csvFINAL.csvv2.csvcopy.csvv2.csvcopy.csvstatus change.csvcopy.csvstatus change.csv(3).csvstatus change.csv(3).csvmessages.csv(3).csvmessages.csvqueue!Which one is the latest? Nobody knows.
Before every hook is a write
  • Each notice is trusted as it stands
  • Each chat creates another lead
  • The conversation never leaves the bot
After Botpress to Salesforce automation: one clean org that matches BotpressThe new way: a live console table of messages streaming in with synced and status change statuses.messages · liveMESSAGECONTACTREPLIESSTATUS#1042Mia Rowe8synced#1043Jon Kessler13synced#1044Ana Silva-2status change#1045Lee Wong21synced#1046Ivy Park5synced#1047Kai Petrov7synced$matches botpress · 0 duplicates
After one event, one outcome
  • Matching uses an external ID field holding the conversation ID, with the lead matched on email; titles and labels are ignored
  • Leads are upserted on an external ID
  • The conversation is logged on the lead

02 · how it works

How a Botpress chat becomes a clean Salesforce lead with an owner

The sequence is fixed so that a replay reaches the same answer every time.

How Botpress to Salesforce automation works: messages in, one clean record each, on a scheduleData flows from a tank for your Botpress bot through a dedupe gate in the BoldBellows sync into a tank for your Salesforce org.Your Botpress botYour Salesforce orgDEDUPE+ status changesBoldBellows syncchecks on a scheduleREAD-ONLY1 RECORD / MESSAGEHow Botpress to Salesforce automation works: messages in, one clean record each, on a scheduleTank, dedupe gate, tank.Your Botpress botDEDUPE+ status changesYour Salesforce org
  1. 01

    Filter at the door

    The Botpress event is authenticated and recorded first; only a Botpress event that matches the rule continues.

  2. 02

    Upsert, log, check

    The lead is upserted on the external ID, the conversation is logged, and existing contacts are checked.

  3. 03

    Route, batch, protect

    The owner is routed, backlogs are batched, and credentials stay in configuration variables.

The rules of the two platforms

  • Upsert needs an external ID

    Salesforce upserts through an external ID field, and the REST API accepts up to 200 records in an sObject collection, which lets the route write a lead without creating a second one.

  • Secrets stay in variables

    The connected app credentials live in Botpress configuration variables and are read in code through env, never typed into a card.

  • Reconciliation step

    An unsure result is reconciled by matching an external ID field holding the conversation ID, with the lead matched on email in Salesforce and recording the verdict.

03 · what ships in the build

The anatomy of a Botpress to Salesforce route, in seven parts

Each layer adds one job: Kickoff decides, Build-out delivers, Review verifies.

What lands in your org: messages, reports and reports from BotpressMessages report in Salesforce as a dark console: message, date, contact, Template, quantity and net, with a new record arriving and a scan line moving down the records.fx=SYNC("messages")LIVEABCDEFMessageDateContactTemplateSentReplies#10423 MarMia RoweTPL-WELCO28#10433 MarJon KesslerTPL-VERIF113#10444 MarAna SilvaTPL-MESSAGE36#10454 MarLee WongTPL-WELCO121#10465 MarIvy ParkTPL-REMIN25#10475 MarKai PetrovTPL-SUPPO17#10485 MarZoe LinTPL-VERIF412#10496 MarRavi ShahTPL-VERIF3MessagesMessagesDaily messagesQueueStatus changesReports

Covered on this page: botpress Salesforce connected app, botpress Salesforce integration, botpress to Salesforce error handling. Related searches include botpress to Salesforce consultant, Salesforce chatbot botpress, botpress Salesforce task, botpress to Salesforce historical migration, botpress to Salesforce Zapier, botpress to Salesforce service, botpress to Salesforce, botpress Salesforce lead capture, botpress to Salesforce implementation, sync botpress conversations to Salesforce, botpress Salesforce automation, chatbot to Salesforce lead, botpress Salesforce CRM sync, botpress Salesforce rest API, botpress Salesforce upsert, botpress Salesforce contact create, botpress Salesforce, botpress to Salesforce duplicate prevention, botpress lead to Salesforce, botpress Salesforce workflow, botpress Salesforce lead, botpress users Salesforce mapping, botpress execute code Salesforce and botpress Salesforce opportunity.

Qualification check

Applies the written qualification rule to each event and keeps the result beside it.

Kickoff

Stable identity ledger

Logs the key that ties a Botpress change to its Salesforce outcome, ready for audit.

Kickoff

Mapping documentation

Produces the field map as plain documentation your team can read and keep.

Kickoff

Lead writer

Upserts the lead and logs the conversation.

Build-out

External-ID matcher

Checks an external ID field holding the conversation ID, with the lead matched on email in Salesforce before any write, which is what makes replays harmless.

Build-out

Territory and owner matrix

Decides who owns each lead.

Build-out

Lead register

Flags any record whose content no longer mirrors Botpress, and says since when.

Review

Limit monitor

Flags API usage that is climbing toward the allowance.

Review

Exception alerts

Notifies the right person when an exception appears, not the whole team.

Review

04 · who it's for

Fits recruitment teams and whoever must send Botpress leads into Salesforce cleanly: upsert the lead on an external ID, log the conversation as a task, convert or route it by your rules and avoid duplicates

Botpress is where prospects say what they want, and Salesforce is where your team works the pipeline.

Sales rep

"Give me context."

The conversation is on the lead.

Sales manager

"Stop the duplicates."

Leads upsert on an external ID.

RevOps lead

"Respect the API limits."

Backlogs are batched.

Admin

"Keep it secure."

Secrets stay in variables.

Marketing lead

"Know the campaign."

It is set on every lead.

Sales director

"Every lead needs a name on it."

Routing puts one there.

What changes the price: visitors, leads and tasks

Shape the Botpress to Salesforce scope, price updates as you go

Prices start at $870.

View Pricing
  • One setup fee
  • Range shown first
  • PDF handover included

05 · compare your options

Side by side: a web-to-lead form behind a chat window, a zap and a Botpress route that upserts on an external ID

Each can create a lead. Only one upserts on an external ID, logs the conversation and routes the owner.

Comparison table: Side by side: a web-to-lead form behind a chat window, a zap and a Botpress route that upserts on an external ID
How it is set offa web-to-lead form behind a chat windowA basic two-step zapA route built around a Botpress Salesforce upsert route
What starts the workAn owner checking dailyAny update at allApproved Botpress events only
How identity is decidedDecided case by caseThe display textExternal ID holding the conversation ID, matched on email
What reaches SalesforceA fraction of the recordA minimal recordOne lead with a task, a campaign and an owner
After an uncertain resultRe-run and hopeRetries on a timerProves the outcome before repeating anything
By handAutomatedTime each week3 hours10 minErrors a month120Files to juggle371

A delayed event meets a newer record

The stored time of the last confirmed change guards every write, so a late event cannot regress the record.

A known customer chats with a sales question

The email matches an existing contact, no lead is created, the conversation is logged against the contact, and the account owner is notified. Searching Salesforce on an external ID field holding the conversation ID, with the lead matched on email shows whether the record is already there, and whether it is right. Nothing new is created unless the lookup comes back empty.

We begin by fixing an external ID field holding the conversation ID, with the lead matched on email, and every test afterwards checks that it still holds.

Pricing

Build your Botpress to Salesforce price

Pick a package, answer three short questions about how Botpress 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 Botpress to Salesforce route.

A focused production route for one Botpress environment and one Salesforce destination, delivering Botpress to Salesforce automation that upserts leads on an external ID, logs the conversation as a task, routes the owner by your rules and stays inside Salesforce API limits with identity and failure controls from day one.

  • One approved Botpress event family and business-state admission rule within the Botpress to Salesforce service.
  • One authorized account, workspace, organization, or base boundary within the Botpress to Salesforce service.
  • One Salesforce object contract with field and relationship mapping within the Botpress to Salesforce service.
  • Stable matching through Botpress workspace plus bot, conversation, user, message, execution, integration, or event ID and a Salesforce External ID mapped to the source identity
  • Tests for duplicates, stale events, malformed data, denied access, and timeouts within the Botpress to Salesforce service.
  • Implementation map, test record, and premium PDF operations handover within the Botpress 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 Botpress to Salesforce automation that upserts leads on an external ID, logs the conversation as a task, routes the owner by your rules and stays inside Salesforce API limits.

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

Adds reconciliation and governance for teams that now depend on Botpress to Salesforce automation that upserts leads on an external ID, logs the conversation as a task, routes the owner by your rules and stays inside Salesforce API limits, with drift detection and an exception register for Salesforce.

  • Everything in Controlled Flow
  • Scheduled source-to-destination reconciliation
  • Schema, field, scope, and webhook drift checks within the Botpress 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 Botpress 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 Botpress events should reach Salesforce?Required

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

How should Salesforce recognize a Botpress record it has already handled?Required

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

Which Botpress 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.

06 · process & getting started

Six steps that turn a pile of leads into one tidy org

Six steps from kickoff to a monitored route, each with a written result.

  1. Step 01

    Map the objects

    We list the lead, contact, task and campaign fields the bot may write and the external ID to use.

  2. Step 02

    Approve access

    On this Botpress to Salesforce route, both products are connected in a sandbox first where one exists, then in production, with scoped access.

  3. Step 03

    Fix the rules

    Routing, conversion, duplicate handling and what the bot must never change are written out and approved first.

  4. Step 04

    Acceptance runs

    Normal and awkward records are pushed through a test Salesforce, and you sign off the results before go-live.

  5. Step 05

    Launch with notes

    With Botpress to Salesforce in place, after sign-off the route runs live from the agreed starting point, with plain-language notes for your team.

  6. Step 06

    Close the loop

    A final review confirms the success measures agreed at the start and records what to watch next.

Handover for Botpress to Salesforce automation: notes, a checked run and a health checkHandover pack: a terminal checklist where every item is ticked, a PDF to keep, and a sync health card showing the last sync completed.handover.check[]event trigger confirmed[]reports and fields mapped[]48 test events replayed[]duplicate replay blocked[]failure path names an owner[]plain-English pack written$PDFHandover packPDF · yours to keepSYNC HEALTHlast sync 06:00 · all OK

07 · turnaround

Turnaround you can plan around

Turnaround is measured from the moment access is ready, for this Botpress to Salesforce route.

Kickoff

6 to 10 business days

Build-out

10 to 16 business days

Review

16 to 24 business days

08 · before we start

Your checklist before we start

  • An administrator's approval to connect Botpress

  • A Botpress workspace and bot, a Salesforce org with a connected app, and an external ID field on the lead object

  • The Botpress account owner's sign-off for the connection

  • A list of the statuses or stages that matter to you

  • A short description of how the team works in Salesforce today

  • Your retention rule for anything the route logs

09 · security and ownership

Only listed fields move, and every permission is explained

Data moves from Botpress to Salesforce only as far as the field map allows.

Read-only Botpress to Salesforce access: your data stays yoursAn access card for a named viewer being read by a reader that says read-only access.READ-ONLY ACCESSNamed personVIEWER · READ-ONLYID 0042 · 9F2C

Outside the core

The route runs beside Botpress and Salesforce, not within them, so neither vendor's own updates collide with it.

Scoped, revocable access

For Botpress to Salesforce, you can rotate or remove every credential without asking us.

Only approved values cross

What appears in Salesforce is exactly what the field map lists, and the map is part of the handover.

Doubtful writes are verified

If a response goes missing, Salesforce is searched by an external ID field holding the conversation ID, with the lead matched on email and the outcome recorded before anything else happens.

Minimal logging

No Botpress message bodies, contact lists or payloads are stored in our logs.

Full handover

Ownership passes to you with the written runbook, in the Botpress to Salesforce route.

10 · verified reviews

What BoldBellows clients say

Verified reviews from business owners who use BoldBellows automations every day, from marketing and sales 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 Booking & Scheduling Automation

Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.

No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.

Emily CarterVerifiedLondon, United Kingdom

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

11 · questions

Botpress and Salesforce: what sales operations ask

Practical answers on scope, price, access and what happens later, on the Botpress to Salesforce route.

What can a custom build do that a Botpress to Salesforce Zapier path cannot?

Every qualified chat in Salesforce as one lead with its conversation and owner is easy. The hard part, which a zap skips, is to upsert on an external ID, log the conversation or stay inside the API limits. That is the extra we deliver on top of the trigger.

How does Botpress reach Salesforce?

Through an Execute Code card that uses Salesforce's REST API with a connected app.

What prevents a second lead for the same person?

The lead is upserted on an external ID and the email is checked against contacts.

Where does the conversation go?

Into a task on the lead, with a link to the transcript.

Can leads be routed?

Yes, by territory, round robin or your own rules.

What about API limits?

Records are sent in collection requests of up to 200, and usage is watched.

Where are credentials kept?

In Botpress configuration variables.

Do you provide a Botpress Salesforce field mapping service?

Every package covers a Botpress Salesforce field mapping service: a field-by-field plan you approve, then a build that follows it exactly.

Can we add approval steps or thresholds in the Botpress to Salesforce route?

Yes. Branching rules turn this into a custom Botpress workflow for Salesforce, and you get the advice of a Botpress Salesforce integration consultant with it. Packages start at $870.

Who fixes it when a platform changes on the Botpress to Salesforce route?

For Botpress to Salesforce, we design for change by making failure visible.

Make every Botpress lead land in Salesforce exactly once

Hand your reps leads that need no detective work

We design the way to automate Botpress data to Salesforce around it, from $870.

We price those individually.