Duplicate leads
Every session created one.
Dialogflow to Salesforce automation for teams that run sales and service on Salesforce
Dialogflow to Salesforce automation that upserts leads on an external ID, logs the session and creates one case for a support issue
A Dialogflow CX webhook can authenticate to Salesforce through a connected app and use the REST API, which gives you both sObject upserts and collection requests that carry many records at once. BoldBellows notes the email, the campaign and the session ID before a lead or case is written, upserts on an external ID so a retry finds the same record, then upserts the lead on an external ID field, writes the source and campaign, logs the session summary as a task with a link to the conversation, creates a single case when the session is a support issue and links it to the matching contact, flags an email that already belongs to a contact so it is reviewed and not duplicated, routes the owner by territory or round robin, and sends backlogs as collection requests.
View Pricing
From $870, paid once. Send Dialogflow to Salesforce.
- Send Dialogflow to Salesforce
- Upsert on an external ID
- One case per support issue
Evidence the Salesforce route is dependable
- Upsert on external IDone lead each
- Session loggedas a task
- One case per issuenever two
- Existing contacts flaggednot duplicated
- Transferable buildEverything is documented so your team can run it without us
- Transparent pricingthe entry package is $870; the calculator shows each add-on before you pay
B2Before and after
A new lead for every conversation and an org full of twins
An agent connected with a plain create step adds a lead every time a caller gives an email, including customers who are already contacts. Representatives then chase a customer as a prospect and reports count one person twice. The conversation stays in the agent, so the first message from your side starts from nothing, and a support issue that arrives by chat becomes a lead instead of a case. Sending records one by one uses up the daily API allowance on a busy launch.
Sound familiar?
A customer chased as a prospect
Contacts were not checked.
Reps starting blind
The session stayed in the agent.
A support issue filed as a lead
Nothing chose between lead and case.
API allowance spent
Records were sent one by one.
Credentials in the webhook
Secrets were not kept apart.
The same team, working records that arrive with context
Before
- Each event is treated as brand new
- Each session creates another lead
- The conversation never leaves the agent
After
- An external ID field holding the session ID, with the lead matched on email is stored before anything is written
- Leads are upserted on an external ID for Dialogflow to Salesforce
- The session is logged on the record
D4How it works
How a Dialogflow session becomes a clean Salesforce record with an owner
Each event passes the same gates: rule, key, lookup, write, proof.
1. Catch the event
The Dialogflow notification is received, confirmed as genuine and matched against the list of changes that should act.
2. Upsert, log, check
The lead is upserted on the external ID, the session is logged, and existing contacts are checked.
3. Case, route, batch
A support issue becomes one case, the owner is routed, and backlogs are batched.
E5Inside your org
What you are buying: the Dialogflow to Salesforce route in parts
Connect covers admission and the key, Resolve covers construction and matching, and Safeguard covers comparison and ownership.
Connect
Change classifier
Sorts each Dialogflow event into act, ignore or review, with the reason saved.
Connect
Stable identity ledger
Gives each Dialogflow record a stable identity inside Salesforce that survives edits and retries.
Connect
Typed field translator
Converts Dialogflow values into the exact types Salesforce expects, so nothing arrives as the wrong kind of data.
Resolve
Record writer
Upserts the lead, logs the session and creates the case.
Resolve
External-ID matcher
Looks up an external ID field holding the session ID, with the lead matched on email first, then chooses the one safe action for the event.
Resolve
Territory and owner matrix
Decides who owns each record.
Safeguard
Record register
Checks Salesforce against Dialogflow at intervals and raises anything that diverges.
Safeguard
Limit monitor
Flags API usage climbing toward the allowance.
Safeguard
Exception ageing
Tracks how long each unresolved case has been open and raises the oldest first.
This build speaks to dialogflow entities Salesforce mapping, dialogflow to Salesforce historical migration and dialogflow Salesforce workflow. Related searches include dialogflow Salesforce lead, dialogflow Salesforce upsert, dialogflow lead to Salesforce, dialogflow to Salesforce duplicate prevention, sync dialogflow intents to Salesforce, dialogflow to Salesforce Zapier, dialogflow Salesforce integration, dialogflow Salesforce CRM sync, Salesforce chatbot dialogflow, dialogflow Salesforce opportunity, dialogflow to Salesforce, dialogflow webhook Salesforce, dialogflow Salesforce, dialogflow Salesforce lead capture, dialogflow Salesforce automation, dialogflow to Salesforce consultant, dialogflow Salesforce case, dialogflow to Salesforce implementation, dialogflow Salesforce contact create, dialogflow cx Salesforce, dialogflow to Salesforce error handling, dialogflow Salesforce connected app, dialogflow Salesforce task and dialogflow to Salesforce service.
G7Who it is for
Suited to busy insurers and claims teams, and to those who send Dialogflow leads and support issues into Salesforce cleanly: upsert the lead on an external ID, log the session as a task, create a case for a support issue and route the owner by your rules
Sales and service teams live in Salesforce, so what the agent learns has to land there as a clean lead or case.
Sales rep
"Give me context."
The session is on the record.
Service manager
"One case per issue."
Support sessions become cases.
RevOps lead
"Respect the API limits."
Backlogs are batched.
Administrator
"Keep it secure."
Secrets stay in Secret Manager.
Marketing manager
"Know the campaign."
It is set on every lead.
Sales director
"Every lead needs a name."
Routing puts one there.
Pricing depends on callers, leads and cases
Your Dialogflow to Salesforce price, as you choose it
Begin with Connect at $870 and add only what your rollout needs.
View Pricing
One setup fee
I9Your options
Not a web-to-lead form behind a chat window, not a basic zap, but a Dialogflow route that upserts on an external ID
Each can create a lead. Only one upserts on an external ID, logs the session and files a single case.
| Where the work starts | a web-to-lead form behind a chat window | A one-step Dialogflow to Salesforce zap | Built as a Dialogflow Salesforce upsert route |
|---|---|---|---|
| What starts the work | Someone remembers | All events of the chosen type | The Dialogflow event you defined, nothing else |
| How identity is decided | Looked up in a spreadsheet | A convenient field, unchecked | External ID holding the session ID, matched on email |
| What reaches Salesforce | Only what was noticed | Plain values with no types | One lead or case with a task, a campaign and an owner |
| After an uncertain result | Check each tool in turn | Halts and waits | Verifies the result, then fixes or escalates |
A stale event shows up last
Time is checked before anything is written: the stale event is logged with its reason and the current record stays as it is, in the Dialogflow to Salesforce route.
Someone already on file as a contact asks about an upgrade
The email matches the contact, no lead is created, the session is logged against it, and the account owner is notified. Matching on an external ID field holding the session ID, with the lead matched on email, the route sorts the situation into absent, present and correct, present but different, or ambiguous. If the Dialogflow record exists and matches, nothing more is written.
An external ID field holding the session ID, with the lead matched on email is the one thing that cannot change after launch, so it is settled on day one.
Pricing
Build your Dialogflow to Salesforce price
Pick a package, answer three short questions about how Dialogflow data should reach Salesforce, and your price and turnaround move as you choose.
J11The process
Six steps that turn a pile of Salesforce leads into one tidy org
Brief, access, design, test, launch and review: six steps, each with a deliverable.
-
Day 1
Map the objects
We list the lead, contact, case and task fields the webhook may write and the external ID to use.
-
Access review
Approve access
We inspect the Dialogflow objects and the Salesforce target, then fix the identifiers that connect them.
-
Build phase
Fix the rules
Routing, duplicate handling, when a case is created and what the webhook must never change are written out and approved first.
-
Before you review
Run the hard cases first
Repeats, stale events and permission changes are tested before the easy cases, in a copy of Salesforce.
-
Release day
Launch with notes
Release is timed to a checkpoint, and the administrator PDF explains what to watch and whom to ask, on the Dialogflow to Salesforce route.
-
Day 1
Check the live results
The first runs are compared record by record with the source so you can see the route doing its job.
K12Turnaround
Time to launch, by package
Delivery windows start when the connections are in place, on the Dialogflow to Salesforce route.
Connect
6 to 10 business days
Resolve
10 to 16 business days
Safeguard
16 to 24 business days
L13Getting started
To start the Salesforce build, have these ready
Permission for us to read the relevant Dialogflow records
A Dialogflow CX agent, a Salesforce org with a connected app, and an external ID field on the lead object
A Dialogflow user or token limited to the objects in scope
Two real cases: one Dialogflow event that should act and one that should not
Your preferred naming for statuses, tags or labels in Salesforce
Contact details for whoever manages Salesforce access
M14Safety and ownership
The Dialogflow record gets only what it needs, and nothing inside Salesforce is altered
On this Dialogflow to Salesforce route, the connection has a short list of permissions, all written down, all revocable, and none that reach beyond this route.
Supported connections, nothing more
Access runs through the approved connection points on both sides, so an update to Dialogflow or Salesforce does not undo the build.
Scoped, revocable access
Access is scoped to what the Dialogflow field map needs and no further.
Private details stay private
Internal notes, payment information and anything outside the map remain in Dialogflow and never appear in Salesforce.
Doubt goes to a lookup
When a write might have landed, the answer comes from Salesforce, matched on an external ID field holding the session ID, with the lead matched on email, not from a second attempt.
Minimal logging
With Dialogflow to Salesforce in place, what we log is enough to repair a problem and no more.
Full handover
For Dialogflow to Salesforce, the route is yours from day one, and the documentation proves it.
N15In their words
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.
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.
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.
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.
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.
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.
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.
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.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
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.
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.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
P16FAQ
Dialogflow and Salesforce: what sales operations ask
Common questions from teams in your position, answered directly, on the Dialogflow to Salesforce route.
Does a Dialogflow to Salesforce Zapier route prevent duplicates?
Every qualified session in Salesforce as one lead or one case with its history and owner is well within a zap's reach. It does not upsert on an external ID, log the session or stay inside the API limits. The build is the part that handles what a simple zap cannot.
How does Dialogflow reach Salesforce?
Through a webhook that uses Salesforce's REST API with a connected app.
What prevents a second lead for the same person in the Dialogflow to Salesforce route?
The Dialogflow lead is upserted on an external ID and the email is checked against contacts.
Where does the session go?
Into a task on the record, with a link to the conversation.
When is a case created?
When the session is a support issue, one case per issue.
What about API limits?
Records are sent in collection requests of up to 200, and usage is watched, for this Dialogflow to Salesforce route.
Where are credentials kept?
In Secret Manager, outside the agent.
How do you test the mapping?
Mapping is never an extra. The Dialogflow Salesforce field mapping service is included in the fixed price, and every field is matched to a Salesforce place before anything is written.
How custom can the Dialogflow to Salesforce route get?
Yes. Branching by region, value or product gives you a custom Dialogflow workflow for Salesforce, scoped and then built by the same Dialogflow Salesforce integration consultant. Packages start at $870.
What if Dialogflow alters a field we depend on?
For Dialogflow to Salesforce, the notes name every interface and version assumption.
Q17Make every Dialogflow lead land in Salesforce exactly once
Hand your reps records that need no detective work
Describe the outcome you want in Salesforce, and we build the pipeline that automates Dialogflow data to Salesforce so it arrives every time. Entry pricing is $870.
- From $870, paid once
- Upsert on external ID
- One case per issue
- No monthly fee from us
On this Dialogflow to Salesforce route, if your case is bigger than the packages allow, ask for a custom quote.