How do I sign up for mindSDB Cloud Free and connect Snowflake and Salesforce?
AI Analytics & BI Platforms

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

10 min read

For most teams, the real blocker isn’t buying an AI analytics platform—it’s getting from signup to connected data without weeks of setup. With mindSDB Cloud Free, you can go from “no account” to querying Snowflake and Salesforce together in minutes, with no ETL, no pipelines, and no schema gymnastics.

This guide walks through, step by step, how to sign up for mindSDB Cloud Free and connect both Snowflake and Salesforce so you can start asking cross-system questions in plain English or SQL.

Why start with mindSDB Cloud Free?

Before we get into the clicks and fields, it’s worth being explicit about what you’re getting:

  • Minds Enterprise: Cloud, Free plan
    • $0/month, single user
    • Supports: Snowflake, Salesforce, PostgreSQL, MySQL, MS SQL Server, BigQuery
    • Query-in-place: no data movement, no ETL
  • Use cases you can unlock on day one
    • “Show pipeline by stage from Salesforce and payment status from Snowflake”
    • “Which closed-lost opportunities last quarter had no follow-up activity logged in Salesforce but show recent invoices in Snowflake?”
    • “Summarize weekly ARR changes and top 10 at-risk accounts from Snowflake and Salesforce notes”

The Free plan is designed for exactly this: prove value in < 1 day, then decide if you want to scale up.

Step 1: Create your mindSDB Cloud Free account

1. Navigate to the signup flow

  1. Go to: https://mindsdb.com
  2. In the navigation, select Products → Minds Enterprise (or Pricing).
  3. On the pricing page, locate the Free tier under “Minds Enterprise: Cloud”.
  4. Click Try for free or Get started under the Free plan.

You’re now in the Cloud signup flow for the Free plan.

2. Complete account registration

Depending on the current UI, you’ll see one or more of:

  • Email-based signup
    • Enter your work email.
    • Set a strong password.
    • Agree to terms and click Sign up.
  • SSO-based signup
    • If presented, you can choose Google/Microsoft/enterprise SSO.
    • Approve the SSO request to provision your account.

3. Verify your email (if prompted)

  1. Check your inbox for a mindSDB verification email.
  2. Click the verification link.
  3. You’ll be redirected back into Minds Enterprise: Cloud and landed in your workspace.

At this point, you have a single-user Free workspace capable of connecting Snowflake and Salesforce.

Step 2: Understand the mindSDB Cloud workspace

Before wiring up Snowflake and Salesforce, orient yourself to the Cloud interface:

  • Data / Connectors section
    Where you add and manage data sources like Snowflake and Salesforce.
  • Ask / Chat or SQL console
    Where you ask questions in natural language and/or SQL.
  • Projects / Spaces
    Optional grouping for different teams or initiatives (e.g., “RevOps,” “Finance”).

For this guide, we’ll assume you’re in the main workspace and will add both connectors there.

Step 3: Prepare Snowflake for connection

The most common friction I’ve seen comes from missing or mis-scoped credentials. Take 3–5 minutes to align your Snowflake setup.

1. Decide which Snowflake environment to use

Pick the account where your analytics or core business tables live:

  • Example account URL:
    https://<account_identifier>.<region>.snowflakecomputing.com
  • Know which role, warehouse, database, and schema hold the tables you care about (e.g., ANALYTICS_ROLE, ANALYST_WH, PROD_DB, PUBLIC).

2. Create (or identify) a user for mindSDB

Work with your Snowflake admin if needed. You want a dedicated, least-privilege user, such as MINDSDB_USER, with:

  • Usage + read access (for analytics-only workloads) on:
    • The target warehouse
    • The target database and schemas

A minimal example (your admin will adapt to your standards):

-- Create role
CREATE ROLE MINDSDB_ROLE;

-- Grant access
GRANT USAGE ON WAREHOUSE ANALYST_WH TO ROLE MINDSDB_ROLE;
GRANT USAGE ON DATABASE PROD_DB TO ROLE MINDSDB_ROLE;
GRANT USAGE ON SCHEMA PROD_DB.PUBLIC TO ROLE MINDSDB_ROLE;
GRANT SELECT ON ALL TABLES IN SCHEMA PROD_DB.PUBLIC TO ROLE MINDSDB_ROLE;
GRANT SELECT ON FUTURE TABLES IN SCHEMA PROD_DB.PUBLIC TO ROLE MINDSDB_ROLE;

-- Create user with that role
CREATE USER MINDSDB_USER
  PASSWORD = '<STRONG_PASSWORD>'
  DEFAULT_ROLE = MINDSDB_ROLE
  DEFAULT_WAREHOUSE = ANALYST_WH
  DEFAULT_NAMESPACE = PROD_DB.PUBLIC;

GRANT ROLE MINDSDB_ROLE TO USER MINDSDB_USER;

Capture the following for the connector:

  • Account identifier (from your Snowflake URL)
  • Username (e.g., MINDSDB_USER)
  • Password (or key pair details if you use key auth)
  • Role (e.g., MINDSDB_ROLE)
  • Warehouse (e.g., ANALYST_WH)
  • Database (e.g., PROD_DB)
  • Schema (e.g., PUBLIC)

Step 4: Connect Snowflake to mindSDB Cloud Free

1. Open the Data / Connectors page

  1. In your mindSDB Cloud workspace, go to Data, Sources, or Connectors (label may vary slightly).
  2. Click Add data source, Connect data, or similar.

2. Select Snowflake

  1. From the list of supported integrations, choose Snowflake.
  2. You’ll see a configuration form for the Snowflake connection.

3. Fill in Snowflake connection details

Typical fields include:

  • Connection name
    • Example: snowflake_prod or sf_analytics
  • Account
    • Just the account identifier (not the full URL), e.g. ab12345.us-east-1
  • User
    • MINDSDB_USER
  • Password or Key
    • The credential you created earlier
  • Role
    • MINDSDB_ROLE
  • Warehouse
    • ANALYST_WH
  • Database
    • PROD_DB
  • Schema
    • PUBLIC

If the UI exposes advanced settings (timeouts, SSL), keep defaults unless your Snowflake team has custom requirements.

4. Test and save the Snowflake connector

  1. Click Test connection.
  2. If the test passes:
    • Click Save or Connect.
  3. If the test fails:
    • Double-check account identifier (common mistake: including the full URL).
    • Verify user/role permissions and that the warehouse is active.
    • Confirm network rules (if Snowflake is restricted by IP, you may need to allow the mindSDB Cloud IP range).

Once connected, Snowflake will appear as an available source in your workspace.

Step 5: Prepare Salesforce for connection

Salesforce is where governance usually bites: you want to leverage native permissions, not bypass them.

1. Decide which Salesforce org to connect

Use the org where your production CRM data lives:

  • Production vs Sandbox
    • Start with a sandbox if you’re just exploring; move to production when you’re ready to operationalize.
  • Make sure you know:
    • The instance URL (e.g., https://yourcompany.my.salesforce.com)
    • Whether you use SSO or standard Salesforce login.

2. Set up a dedicated integration user (recommended)

Best practice is an integration user like mindsdb.integration@yourcompany.com:

  • Profile/permission set with read access to:
    • Objects you care about: Account, Opportunity, Contact, Lead, Case, custom objects, etc.
  • Respect the principle of least privilege:
    • No broad admin rights if not needed.
    • Only grant object and field visibility required for analytics.

If your org prefers OAuth with a Connected App:

  • Your Salesforce admin can create a Connected App for mindSDB with:
    • OAuth scopes like Access and manage your data (api) and Perform requests on your behalf at any time (refresh_token, offline_access).
    • IP restrictions according to your security policy.

Step 6: Connect Salesforce to mindSDB Cloud Free

1. Open the Data / Connectors page again

  1. In the same Data / Sources / Connectors area, click Add data source.
  2. Choose Salesforce from the integration list.

2. Choose authentication method

You’ll typically see one of:

  • OAuth-based “Connect with Salesforce” button
    1. Click Connect Salesforce.
    2. A Salesforce login window opens.
    3. Log in with the dedicated integration user or your admin-approved account.
    4. Review and approve requested permissions (API/data access).
    5. You’re redirected back to mindSDB with the connection established.
  • Manual credentials / token-based config
    • Enter:
      • Instance URL: https://yourcompany.my.salesforce.com
      • Username: integration user email
      • Password + Security Token, or OAuth client/secret if configured.

Follow what your organization’s Salesforce admin recommends, as they’ll align this with your governance and SSO model.

3. Test and save the Salesforce connector

  1. Click Test connection.
  2. If successful, click Save or Connect.
  3. If it fails:
    • Confirm login works on Salesforce directly.
    • Check that the integration user is not IP-restricted beyond what mindSDB Cloud can reach.
    • Verify the Connected App scopes if using OAuth.

Once connected, you’ll see Salesforce objects exposed for analytics.

Step 7: Verify that Snowflake and Salesforce are both live

At this stage, your Free workspace should show:

  • Snowflake as a connected structured data source.
  • Salesforce as a connected application data source.

Confirm both:

  1. In the Data / Sources list, ensure both connectors show a healthy or active status.
  2. Optionally, drill into each to preview:
    • Snowflake: tables like OPPORTUNITY_FACT, INVOICE, SUBSCRIPTION.
    • Salesforce: objects like Account, Opportunity, Contact, Case.

Step 8: Start querying Snowflake and Salesforce together

This is where the “AI data solution” part becomes real: you’re not exporting CSVs or building a warehouse-on-top-of-a-warehouse. You’re querying in place.

1. Use natural language queries

Open the Ask or Chat interface and try prompts like:

  • “Show me total pipeline amount by stage from Salesforce, grouped by owner, for this quarter.”
  • “Combine Salesforce opportunities with Snowflake invoice data to identify deals that closed in the last 90 days but have no invoices yet.”
  • “List accounts with an open Salesforce case and more than $50,000 in ARR from the Snowflake subscription table.”

mindSDB’s cognitive engine will:

  1. Parse your question.
  2. Map your business terms (“pipeline,” “ARR,” “cases”) to Snowflake tables and Salesforce objects.
  3. Generate an execution plan and SQL.
  4. Run queries directly against Snowflake and Salesforce.
  5. Return answers with sources you can verify.

2. Use SQL directly (for analysts and engineers)

If you prefer seeing the raw queries:

  • Open the SQL view or console.
  • Reference Snowflake and Salesforce as separate sources (your exact syntax may vary by UI), for example:
SELECT
  sf.Opportunity.Name,
  sf.Opportunity.StageName,
  sf.Opportunity.Amount,
  sf.Account.Name AS account_name,
  sf.Account.OwnerId AS owner_id,
  snf.invoice_total
FROM salesforce.Opportunity sf
JOIN salesforce.Account sf_acc
  ON sf.AccountId = sf_acc.Id
LEFT JOIN snowflake.invoice snf
  ON sf_acc.Id = snf.account_id
WHERE sf.CloseDate >= DATEADD('day', -90, CURRENT_DATE())
  AND sf.StageName = 'Closed Won';

The key is that you’re not duplicating data; you’re using query-in-place execution across systems.

Step 9: Stay within Free plan limits (and know when to upgrade)

On mindSDB Cloud Free, keep a few boundaries in mind:

  • Single user
    • Ideal for an individual champion or early proof-of-concept.
  • Supported integrations
    • You’re already within scope: Snowflake and Salesforce are both supported on Free.
  • Questions / month
    • The documented limit is specifically called out on the Pro tier (e.g., “Cloud instance: 250 questions / month”).
    • Free is for getting started; if you hit friction on usage, Pro or Teams unlock higher throughput and org-wide deployment.

When you reach the point where:

  • More stakeholders need access,
  • You want to wire in more sources (e.g., BigQuery, PostgreSQL, MySQL),
  • Or you need advanced governance and deployment in your own VPC/on-prem,

it’s time to talk Pro or Teams.

Governance and trust boundaries (Snowflake & Salesforce)

Enterprises care less about a flashy demo and more about how this runs in production. Even in Cloud Free, the same principles apply:

  • No data movement
    • mindSDB uses connectors to query Snowflake and Salesforce where they live; there’s no ETL pipeline into a separate data store.
  • Verifiable answers
    • You can inspect the generated SQL or execution plan and see which tables/objects and fields were used.
  • Native permissions
    • On Salesforce, access respects your org’s permission model (profiles, permission sets, object/field visibility).
  • Path to private deployment
    • When you move beyond Free, Minds Enterprise: Deploy Anywhere lets you keep everything within your VPC or on-prem, so your trust boundary never changes.

That’s the difference between “AI magic” and a production-grade AI business insights solution.

Putting it all together

To recap how to sign up for mindSDB Cloud Free and connect Snowflake and Salesforce:

  1. Sign up for mindSDB Cloud Free from the Minds Enterprise pricing page.
  2. Create and verify your account, landing in your single-user Cloud workspace.
  3. Prepare Snowflake: dedicated user/role with read access to your analytics schemas.
  4. Connect Snowflake via the Snowflake connector and test the connection.
  5. Prepare Salesforce: an integration user or Connected App with appropriate object/field access.
  6. Connect Salesforce via OAuth or token-based auth and validate access.
  7. Confirm both sources are active, previewing tables/objects.
  8. Start asking cross-system questions in natural language or SQL, with no ETL and no data movement.

Once you see Snowflake and Salesforce answering questions together in under five minutes, it becomes very hard to go back to waiting days for a new dashboard.

Next Step

Get Started

Back to AI Analytics & BI Platforms

Keep Reading

More from AI Analytics & BI Platforms

How do I contact mindSDB sales or schedule a demo for Teams/Deploy Anywhere pricing?

Read more

mindSDB connectors: which data sources are supported and how do I configure credentials securely?

Read more

mindSDB open source vs mindSDB enterprise (Cloud/Deploy Anywhere): which should we use for production?

Read more