Salesforce and Autonomy.
For groups that run on Salesforce, Autonomy pushes website enquiries and confirmed reservations into the dealer's Salesforce org as leads, updates Salesforce vehicle records with the website URL after every stock sync, and accepts price, published, reserved and sold updates back in real time.
What it does.
Three independent integrations, each with its own credentials. Lead export sends enquiries and confirmed reservations to a custom endpoint in the dealer's Salesforce org, with the customer's details, the vehicle of interest, any part-exchange valuation, the page URL, UTM values and the dealer ID for the dealership. Test-drive dates and times are passed as a timestamp. A test mode points leads at the Salesforce sandbox.
Stock export runs after each stock sync completes and updates Salesforce vehicle records in batches, so Salesforce holds the website URL for every car. The inbound vehicle webhook lets Salesforce push price, published, reserved and sold changes straight back to the matching vehicle on the site. On one group site, the vehicle stock itself also arrives from Salesforce.
What flows where.
| Data | Direction | How often |
|---|---|---|
| Enquiries as leads (customer, vehicle, valuation, page URL, UTM values, dealer ID) | Autonomy to Salesforce | On submission |
| Confirmed reservations as leads | Autonomy to Salesforce | On confirmation |
| Vehicle records updated with website URLs, in batches of 200 | Autonomy to Salesforce | After every stock sync |
| Vehicle price, published, reserved and sold updates (webhook) | Salesforce to Autonomy | Real time |
| Vehicle stock feed from Salesforce | Salesforce to Autonomy | Hourly, through the site's stock import map (file on FTP or HTTP API) |
Service bookings are not forwarded to Salesforce, and marketing preferences are not currently transmitted with leads. Every attempt is logged in the dashboard's API notifications under the Salesforce provider.
What the dealer sees.
Nothing changes for the customer. Leads and reservations appear in the dealer's Salesforce against the right dealer ID; the Autonomy dashboard shows each enquiry's processing log and the API notification log for every send.
Who runs it.
Setup and ownership.
The dealer's Salesforce admin creates a connected app and API user, deploys the enquiry endpoint in the org and agrees the feed source value. mtc. then configures the settings in the Autonomy dashboard, sets the Salesforce dealer ID on each dealership, attaches the Salesforce action to the forms and maps the questions, testing against the sandbox first.
What the dealer provides
- Salesforce API user credentials and connected app client ID and secret
- The enquiry endpoint deployed in the dealer's org by their Salesforce team
- Feed source value from the dealer's Salesforce admin
- Salesforce dealer ID for each dealership
- Sandbox access for testing
- Separate credentials for stock export, and a bearer token for the inbound webhook
