Destinations
Data sources
AI insights
About us
Careers
Security
Customer reviews
Contact us
Affiliate program
Solution partners
Template gallery
Looker Studio templates
Power BI templates
Excel templates
Google Sheets templates
Tableau templates
Facebook Ads templates
Google Ads templates
Data fields & Metrics
AI prompt library & Guides
Product documentation
API documentation
Case studies
Blog
Data models
Windsor vs Supermetrics
Windsor vs Funnel.io
Windsor vs Fivetran
Windsor vs Rivery
Windsor vs Portermetrics
Windsor vs Coupler.io
Last updated: 8 September 2026 
Windsor’s Salesforce connector can update records, not just report on them. Once connected, ChatGPT, Claude, or Copilot can change field values on any object, Opportunity, Lead, Contact, Account, Case, or a custom object, straight from a chat, with the exact change shown to you before it saves.
What you can do
One action, update_object, covers every standard and custom object in your org. Give it an object type, a record id, and the fields to change, and only those fields are touched; everything else on the record stays as it was. Passing null for a value clears that field.
Prompts worth running
Move Opportunity 006... to Closed Won and set the Amount to 42000.This lead's phone number is wrong, update it to +1 555 0100 on
Lead 00Q...Log today's call on Case 500...: set Status to "Escalated" and add
this resolution note to the Description field: [notes]Clear the NextStep field on Opportunity 006... now that the deal is
closed.This is one of the most reliable actions on the whole platform
update_object succeeds close to every time it’s tried, more consistently than most write actions across Windsor’s connectors. When it does fail, it’s almost never a Windsor problem, it’s your org’s own Salesforce configuration doing exactly what it’s set up to do: a required custom validation field that wasn’t filled in, a picklist value that doesn’t match your org’s exact allowed values (a common one: a Lead Source Detail picklist rejecting “ChatGPT” or “Claude” because that value was never added to the list), a field locked by your profile’s security settings, or Salesforce’s own duplicate-detection catching a record that looks like one that already exists.
The other real cause is a field name mismatch: Salesforce fields have to be addressed by their exact API name, not the label you see in the UI, and custom fields end in __c. A field that’s valid on one object (like ActivityDate on a Task) will be rejected outright on an object it doesn’t belong to.
You’re always in control
Your assistant shows you the exact object, record, and field changes before anything saves. Nothing updates without your confirmation, and the list of actions available to it is pulled live from Windsor’s API, so it always reflects what your connected org can currently do.
