Vercel · Agent stack · GA · Salesforce connector Beta
Today the website, the reporting script and the new agent all share one integration user’s password, pasted into settings months ago. Nobody knows who changed which record. With Connect, each app asks for a short-lived token when it needs one, as the app or as the person who asked. You see every token in a log and switch off access in one place. Connect has been generally available since 25 August 2026. Its Salesforce connector is still Beta.
Salesforce consulting partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE, India and US desks
The problem
What Connect is
Facts from Vercel’s own pages, checked on 16 October 2026. The sources are at the end of this page.
How it works
Five steps. The connector is set up once for the team. Each project gets only the connectors it is linked to, and each token is short-lived instead of stored for months.
Infographic
Step by step
Register
Register the connector once
Salesforce, Slack or Microsoft, set up at team level from the dashboard or the CLI.
Link
Link it to a project
Only the projects and environments you choose can use it. Production and preview can differ.
Ask
Code asks for a token
At runtime the app requests a token, signed in with its own deployment identity.
Check
Access and consent are checked
Connect checks the project link. If the token is for a person, that person consents the first time.
Use
A short-lived token comes back
The app calls Salesforce with it. The token expires and is never written to your settings.
How it fits together
Customers and staff talk to your app or agent. The app asks Connect for a token, then calls Salesforce, Slack or Microsoft with it. Every token lands in a log you can read.
Infographic
Use cases · worked examples
How Connect fits into the work of the industries we serve, one step at a time.
Example 1 · Real estate, Dubai · Infographic
Today: Brokers ask the Slack bot to move a deal to “Offer made”. Salesforce shows the integration user made the change, so nobody knows which broker did it.
After: The agent asks Connect for a token as the broker who asked. Salesforce records the change under her name, with her own permissions.
Worked example, step by step
Every stage change in the pipeline shows the broker who asked for it.
Example 2 · IT service desk, Bengaluru · Infographic
Today: Staff report problems in a Slack channel. Someone copies each message into a Salesforce case by hand, and some get missed on busy mornings.
After: A Slack trigger in Connect sends each new message to the agent. The agent opens the case in Salesforce with its own app token and replies in the thread.
Worked example, step by step
No message waits for someone to copy it, and the code holds no Salesforce password.
Example 3 · Marketing agency, Mumbai · Infographic
Today: Each client’s Salesforce login sits in a different project’s settings. When a client leaves, nobody is sure every copy of the key is gone.
After: Each client’s Salesforce is one connector, linked only to that client’s project. Ending the contract means removing one connector.
Worked example, step by step
A client who leaves takes their access with them, and the log shows it.
Is it for you
Good fit
Not for you yet
What Mindcat does
The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. After go-live, we keep it patched, watched and changing every month.
FAQ
Sources
Checked against Vercel’s own pages on 16 October 2026. Vercel changes fast, so we check again before any plan we write for you.
Vercel is a product of Vercel Inc. Mindcat builds and runs work on it for clients; we are not affiliated with or endorsed by Vercel.
Start here
One or two lines is enough. You hear back within 24 hours from the person who signs the work.
