How do I sign up for mindSDB Cloud Free and connect Snowflake and Salesforce?

Most teams ask this question when they’re ready to move beyond dashboards and see what conversational analytics over Snowflake and Salesforce actually feels like in practice—without committing a budget or touching ETL. The good news: with MindsDB Cloud Free, you can get from “no account” to “querying both systems in plain English” in under an hour if you follow a clear path.

Below is a step‑by‑step walkthrough of how to sign up for MindsDB Cloud Free and connect Snowflake and Salesforce, plus some practical examples of what you can do once everything is wired together.

Why start with MindsDB Cloud Free for Snowflake and Salesforce?

If your data lives in Snowflake and Salesforce, your bottleneck isn’t storage—it’s how long it takes to get answers. Traditional BI wants you to:

Move data into new warehouses or “analytics copies”
Build and maintain dashboards
Wait on analysts for cross‑system questions

MindsDB flips that model:

Query‑in‑place: We execute where your data already lives—directly in Snowflake and via Salesforce APIs. No data movement, no ETL.
Natural language + SQL: Ask questions in plain English or SQL across both systems in one shot.
Free entry point: MindsDB Cloud Free is built for getting started: zero cost, single user, and support for both Snowflake and Salesforce as integrations.

The Free plan is perfect for a proof‑of‑concept: validate that conversational analytics across Snowflake and Salesforce actually reduces time‑to‑insight before you scale to the Pro or Teams tiers.

Step 1: Sign up for MindsDB Cloud Free

You’ll start with a Cloud instance of Minds Enterprise on the Free tier. This gives you:

$0/month pricing
Single user
Supported integrations including:
- Snowflake
- Salesforce
- PostgreSQL
- MySQL
- MS SQL Server
- Google BigQuery

1.1 Create your MindsDB Cloud account

Go to: https://mindsdb.com
Click Get started, Try for free, or head straight to the Minds Enterprise: Cloud section.
Choose the Free plan (for getting started).
Sign up with your work email (recommended) and set your password, or use SSO if available in your environment.
Confirm your email if prompted to activate the account.
After sign‑in, you’ll land in your MindsDB Cloud workspace.

At this point, you have a fully managed MindsDB Cloud instance running in our infrastructure, with no data hosted or stored by MindsDB itself—connections reach out to your Snowflake and Salesforce environments, and queries execute against your systems.

Step 2: Get your Snowflake details ready

Before you connect Snowflake to MindsDB Cloud Free, you’ll want to have the basics on hand. The setup is fastest if you prepare:

Account identifier
Your Snowflake account name / URL form, e.g. xy12345.us-east-1 or xy12345.us-east-1.aws.
Warehouse
The name of the virtual warehouse MindsDB should use to execute queries, e.g. ANALYTICS_WH.
Database & schema
The database and schema(s) where your analytics tables live, e.g. PROD_ANALYTICS.PUBLIC.
User credentials
A Snowflake user with:
- USAGE on the warehouse, database, and schema
- SELECT on the tables you want to query
- No write privileges required for read‑only analytics

For most teams, I recommend creating a dedicated Snowflake role and user like MINDSDB_READONLY so you can tightly scope access.

Step 3: Connect Snowflake to MindsDB Cloud Free

Now that your account is live and you’ve collected your Snowflake information, you can connect Snowflake as a data source.

3.1 Open the data connections view

In MindsDB Cloud, go to your workspace home.
Navigate to Data Sources, Connections, or similar (this may be labeled slightly differently over time, but you’re looking for where you add integrations).
Click Add data source or New connection.

3.2 Add the Snowflake connection

Choose Snowflake from the list of supported integrations.
Fill in the connection details:
- Account / Host: your Snowflake account identifier or full host.
- Warehouse: the warehouse name (e.g., ANALYTICS_WH).
- Database: the default database to use.
- Schema: the default schema (you can still reference others in queries if permissions allow).
- Username: the dedicated MindsDB user.
- Password or Key‑based auth: depending on how your org manages access.
- Role (optional but recommended): e.g. MINDSDB_READONLY.
Test the connection:
- Click Test connection to ensure MindsDB can reach Snowflake and execute a simple query.
- If there’s an error, check:
  - Network access (allow outbound access from MindsDB Cloud to Snowflake)
  - Credentials (user, password, and role)
  - Privileges on the database, schema, and warehouse
Save the connection:
- Give it a clear name like snowflake_prod so you know which environment it’s pointing at.
- Save and confirm it appears in your list of data sources.

Now MindsDB can run query‑in‑place analytics against your Snowflake warehouse—no replication, no new pipelines.

Step 4: Prepare Salesforce for integration

Salesforce is central for most GTM and service teams, but it’s also a silo. To plug it into MindsDB Cloud Free, you’ll need either:

A Salesforce connected app and OAuth credentials, or
Direct username/password + security token (if your org still allows it)

The exact flow depends on your Salesforce security posture, but the common pieces include:

Salesforce instance URL
Something like https://yourdomain.my.salesforce.com.
Client ID and Client Secret (OAuth)
If using a connected app.
User with API access
Typically a service account with:
- API enabled
- Read access to the objects you want to analyze (Account, Opportunity, Case, Contact, Lead, etc.)

Again, I recommend a dedicated API user + profile with minimum necessary read permissions.

Step 5: Connect Salesforce to MindsDB Cloud Free

With your Salesforce credentials ready, add Salesforce as a second data source.

5.1 Add the Salesforce connection

In MindsDB Cloud, go back to Data Sources / Connections.
Click Add data source or New connection.
Select Salesforce from the integration list.

5.2 Enter Salesforce connection details

Depending on your auth method, you’ll see slightly different fields, but generally:

Environment: Production vs Sandbox.
Instance URL: Your Salesforce base URL.
Auth type:
- OAuth (preferred)
  - Client ID
  - Client Secret
  - Redirect URI (configured in your connected app)
  - Login via browser and grant access
- Username/Password + Security Token (legacy-friendly method)
  - Username
  - Password
  - Security token
API version: You can usually leave this at the recommended default unless your org requires a specific version.

After filling these in, click Test connection:

If the test fails, verify:
- The user has API access and is not locked out.
- The connected app is configured with the right OAuth scopes.
- The IP restrictions in Salesforce allow connections from MindsDB’s Cloud environment (if your org uses IP whitelisting).

5.3 Save and name the Salesforce connection

Give it a recognizable name like salesforce_prod or salesforce_sandbox.
Confirm it appears in your data source list alongside Snowflake.

At this stage, MindsDB can pull structured data from Salesforce objects and join it conceptually with Snowflake facts and dimensions.

Step 6: Start asking cross‑system questions

Once Snowflake and Salesforce are both connected in MindsDB Cloud Free, you can start doing what legacy BI made painful: cross‑system questions in plain English.

6.1 Example questions you can ask

You can now ask MindsDB questions that span both systems, like:

“Show me pipeline revenue from Salesforce opportunities by marketing channel from Snowflake for the last 90 days.”
“Compare closed‑won deals in Salesforce to invoiced revenue in Snowflake, by account, for this quarter.”
“List accounts where Salesforce shows high NPS but Snowflake shows declining usage in the last 30 days.”
“For each sales rep in Salesforce, summarize their opportunity velocity alongside average invoice size from Snowflake.”

Behind the scenes, MindsDB’s cognitive engine:

Understands your question in natural language.
Plans the query steps across Salesforce and Snowflake.
Generates SQL for Snowflake, plus appropriate Salesforce API calls.
Validates the plan.
Executes query‑in‑place against your systems.
Returns citation‑backed answers so you can verify the source.

You’re not moving data; you’re orchestrating it where it already lives.

Step 7: Use SQL when you need full control

If you’re a developer or analyst, you can combine the NL interface with raw SQL to get precise control:

Reference your Snowflake connection by name (e.g., snowflake_prod).
Reference Salesforce as a set of tables/objects (e.g., salesforce_prod.opportunity, salesforce_prod.account).

Typical patterns might include:

Joining Salesforce Opportunity with Snowflake revenue tables by AccountId / Account Name.
Comparing Sales forecast vs actuals: Salesforce forecast fields vs Snowflake billing or invoicing tables.
Building a single, reusable query for a recurring executive view you previously had to stitch together in Excel.

In MindsDB, you can see the SQL that gets executed, review it, and keep a human in the loop. This is a core part of how we keep AI analytics verifiable and defensible.

Governance, trust boundary, and the Free plan

For many teams, signing up for a free cloud service raises obvious governance questions—especially when Salesforce and Snowflake contain sensitive customer and financial data.

Here’s the important framing for MindsDB Cloud Free:

No data hosting or training on your data
MindsDB’s design is to query in place. We don’t host, store, or transfer your Snowflake or Salesforce data for training. We execute analytics against your systems.
Read‑oriented access
For this type of analytics, you can operate with read‑only credentials in both Snowflake and Salesforce. That means no changes to your live data.
Transparent execution
Every step—planning, generation, validation, execution—is logged. You can inspect the underlying SQL and API calls, not just accept black‑box answers.

When you outgrow the Free plan and start thinking about org‑wide rollout, you can move to the Teams tier with Minds Enterprise: Deploy Anywhere, running within your own VPC or on‑prem so your data never leaves your trust boundary. But the workflow and the cognitive engine are the same.

When to move from proof‑of‑concept to rollout

Once you’ve connected Snowflake and Salesforce in MindsDB Cloud Free, a few signals usually tell you it’s time to move beyond a single user:

Stakeholders are asking for access so they can self‑serve instead of waiting on analysts.
You’ve identified 2–3 recurring cross‑system questions (pipeline vs revenue, churn vs usage, NRR by segment) that you want to standardize.
You’re hitting practical constraints of a single‑user, free environment and want RBAC, SSO, and higher question volumes.

At that point, the upgrade path is straightforward:

Pro for a business leader / no‑code, plug‑and‑play experience in the cloud.
Teams for org‑wide deployment in your own infrastructure, with governance controls, RBAC, and SSO.

The underlying benefit doesn’t change: you keep querying Snowflake and Salesforce in place, without ETL sprawl or new dashboard projects.

Bringing it all together

To recap the path for “How do I sign up for MindsDB Cloud Free and connect Snowflake and Salesforce?”:

Sign up for MindsDB Cloud Free from mindsdb.com and create your single‑user, $0/month instance.
Prepare Snowflake credentials with a read‑only role, then add a Snowflake connection and test it.
Prepare Salesforce API access (connected app or API user), then add a Salesforce connection and test it.
Start asking cross‑system questions in plain English and SQL, leveraging query‑in‑place execution.
Verify outputs via visible SQL, reasoning steps, and source citations.
Scale up to Pro or Teams once you’ve proven the value across Snowflake and Salesforce data.

If you’re ready to see this wired up for your environment and data model, the fastest path is to walk through it live with our team.

Get Started