Salesforce

In your Salesforce account, click the gear icon (Settings) in the top-right, then 'Setup.' In the left sidebar search box, type 'App Manager' and click it. Click 'New Connected App' in the top right corner. Fill in the required fields: - Connected App Name: `Bubble Integration` (or your app name) - API Name: auto-populates - Contact Email: your email Under 'API (Enable OAuth Settings)': - Check 'Enable OAuth Settings' - Callback URL: enter your Bubble app's OAuth callback page URL. This must be the exact URL you will create in Bubble: `https://yourapp.bubbleapps.io/oauth_callback` or your custom domain equivalent. If you have a custom domain, use that instead. You can add multiple callback URLs by adding each on a new line. - Selected OAuth Scopes: add at minimum these three: - `Access and manage your data (api)` — for API read/write access - `Perform requests on your behalf at any time (refresh_token, offline_access)` — for refresh tokens - `Provide access to your data via the Web (web)` — for web-based auth Click Save. Salesforce takes 2–10 minutes to provision the Connected App. Wait before trying to authenticate. After waiting, go back to App Manager, find your app, click the dropdown arrow, and click 'View.' Copy the Consumer Key (this is your client_id) and click 'Click to reveal' to see the Consumer Secret (this is your client_secret). Store both securely.

1// Connected App OAuth scopes to select:
2// api              → Access and manage your data
3// refresh_token    → Perform requests on your behalf at any time
4// offline_access   → included with refresh_token scope
5// web              → Provide access to your data via the Web
6
7// Callback URLs (add your actual Bubble app URL):
8// https://yourapp.bubbleapps.io/oauth_callback
9// https://yourcustomdomain.com/oauth_callback  (if using custom domain)
10
11// After saving, find your Connected App:
12// Setup → App Manager → find 'Bubble Integration' → dropdown → View
13// Consumer Key = client_id
14// Consumer Secret = client_secret (click 'Click to reveal')

Before configuring the API Connector, set up the Bubble infrastructure to handle the OAuth redirect from Salesforce. First, create an `oauth_callback` page in Bubble (Page name: `oauth_callback`). This is the page Salesforce redirects to with the `?code=` URL parameter after the user authorizes your Connected App. Create a Salesforce_Tokens data type in the Data tab with these fields: - `access_token` (text) - `refresh_token` (text) - `instance_url` (text) — CRITICAL: this is the user's org-specific Salesforce domain - `token_expiry` (date) - `user` (User) — link to the Bubble User who authenticated Apply privacy rules to Salesforce_Tokens: Everyone else → no fields visible. Enable 'Ignore privacy rules when using workflows.' Now go to Backend Workflows. Create a new workflow named `Exchange Salesforce Code`. Add an input parameter `code` (text). Inside this workflow: 1. Call 'API Connector → Salesforce → Exchange Code for Token' (you will create this call in the next step) 2. Create or update a Salesforce_Tokens record: access_token = result access_token, refresh_token = result refresh_token, instance_url = result instance_url, token_expiry = Current date/time + 7200 seconds, user = Current User On your `oauth_callback` Bubble page, add a Page is loaded workflow: - Condition: Only when Get URL parameter 'code' is not empty - Action: Schedule API Workflow → Exchange Salesforce Code, with code = Get URL parameter 'code' - After exchange: navigate user to your main app page

1// Salesforce_Tokens data type:
2// access_token   → text
3// refresh_token  → text
4// instance_url   → text  (e.g., 'https://mycompany.my.salesforce.com')
5// token_expiry   → date
6// user           → User
7
8// Privacy rule: Everyone else → no fields visible
9// ✓ Ignore privacy rules when using workflows
10
11// oauth_callback page workflow:
12// Trigger: Page is loaded
13// Condition: Get URL parameter 'code' is not empty
14// Step 1: Schedule API Workflow → Exchange Salesforce Code
15//   code = Get URL parameter 'code'
16// Step 2: Navigate to /main-app-page
17
18// If code is empty (user cancelled):
19// Condition: Get URL parameter 'error' is not empty
20// Step 1: Navigate to /login with error message

In Plugins → API Connector, click 'Add another API' and name it `Salesforce`. Leave the base URL blank for now — you will use the stored `instance_url` as a prefix in individual calls since each Salesforce org has a different subdomain. Call 1 — Exchange Code for Token: Click 'Add another call.' Name it `Exchange Code for Token`. Method: POST. URL: `https://login.salesforce.com/services/oauth2/token`. Body type: Form URL-encoded (NOT JSON — Salesforce's token endpoint requires form-encoded). Body parameters: - `grant_type` = `authorization_code` - `code` = `<code>` (dynamic) - `client_id` = your Consumer Key (mark Private) - `client_secret` = your Consumer Secret (mark Private) - `redirect_uri` = `https://yourapp.bubbleapps.io/oauth_callback` (must match Connected App exactly) Set 'Use as' to Action. Call 2 — Refresh Token: Name `Refresh Salesforce Token`. Method: POST. URL: `https://login.salesforce.com/services/oauth2/token`. Body: - `grant_type` = `refresh_token` - `refresh_token` = `<refresh_token>` (dynamic, Private) - `client_id` = your Consumer Key (Private) - `client_secret` = your Consumer Secret (Private) Set 'Use as' to Action. Call 3 — SOQL Query: Name `SOQL Query`. Method: GET. URL: `<instance_url>/services/data/v59.0/query` (instance_url dynamic). URL parameter: `q` = `<soql_query>` (dynamic). Add header `Authorization` = `Bearer <access_token>` (Private dynamic). Set 'Use as' to Data. Initialize with a test instance URL and token. Call 4 — Create Record: Name `Create SObject`. Method: POST. URL: `<instance_url>/services/data/v59.0/sobjects/<object_type>/` (both dynamic). Header: `Authorization: Bearer <access_token>`. JSON body = `<record_data>` (dynamic JSON object). Set 'Use as' to Action.

1// Call 1: Exchange Code for Token
2{
3  "method": "POST",
4  "url": "https://login.salesforce.com/services/oauth2/token",
5  "content_type": "application/x-www-form-urlencoded",
6  "body": {
7    "grant_type": "authorization_code",
8    "code": "<authorization_code>",
9    "client_id": "<consumer_key>",       // Private
10    "client_secret": "<consumer_secret>", // Private
11    "redirect_uri": "https://yourapp.bubbleapps.io/oauth_callback"
12  }
13}
14// Response: { "access_token": "...", "refresh_token": "...", "instance_url": "https://yourorg.my.salesforce.com", "token_type": "Bearer" }
15
16// Call 3: SOQL Query
17{
18  "method": "GET",
19  "url": "<instance_url>/services/data/v59.0/query",
20  "headers": {
21    "Authorization": "Bearer <access_token>"  // Private
22  },
23  "params": {
24    "q": "<soql_query>"
25  }
26}
27// Response: { "totalSize": 25, "done": true, "records": [ {...}, {...} ] }
28
29// Example SOQL queries (URL-encode spaces as +):
30// Opportunities this quarter:
31// SELECT Id, Name, StageName, Amount, CloseDate, Owner.Name FROM Opportunity WHERE CloseDate = THIS_QUARTER
32// Open leads:
33// SELECT Id, FirstName, LastName, Email, Company, Status FROM Lead WHERE IsConverted = false ORDER BY CreatedDate DESC LIMIT 50

Users need a way to connect their Salesforce account to your Bubble app. Create a 'Connect Salesforce' button on your main dashboard or onboarding page. When clicked, this button should redirect the user to Salesforce's authorization URL. In Bubble, add a workflow to the button: action 'Open an external website' with the URL: ``` https://login.salesforce.com/services/oauth2/authorize?response_type=code&client_id=YOUR_CONSUMER_KEY&redirect_uri=https://yourapp.bubbleapps.io/oauth_callback&scope=api+refresh_token+offline_access ``` Set this to open in the same window (not a new tab) so the redirect back to your Bubble app works correctly with the URL parameter. After the user authenticates and is redirected back to your `oauth_callback` page, the Backend Workflow you created in step 2 fires automatically, exchanges the code for tokens, and stores them in Salesforce_Tokens. Now add a token refresh Backend Workflow named `Refresh Salesforce Token`. This workflow reads the current user's Salesforce_Tokens record, calls the Refresh Token API Connector call with the stored refresh_token, and updates the Salesforce_Tokens record with the new access_token and token_expiry. In every workflow that makes a Salesforce API call: 1. Check if Salesforce_Tokens for Current User is empty OR if token_expiry < Current date/time 2. If so: Schedule API Workflow → Refresh Salesforce Token (at Current date/time) 3. Then proceed with the API call using the stored access_token and instance_url

1// Authorization URL to redirect users to for Salesforce login:
2// https://login.salesforce.com/services/oauth2/authorize
3//   ?response_type=code
4//   &client_id=YOUR_CONSUMER_KEY
5//   &redirect_uri=https://yourapp.bubbleapps.io/oauth_callback
6//   &scope=api+refresh_token+offline_access
7
8// Button workflow:
9// Event: Button 'Connect Salesforce' is clicked
10// Action: Open an external website
11//   URL: [build from above template]
12//   Open in current tab (not new tab)
13
14// Token freshness check pattern in all Salesforce workflows:
15// Condition: Only when Current User's Salesforce_Tokens token_expiry < Current date/time
16//   OR Current User's Salesforce_Tokens is empty
17// Action: Schedule API Workflow → Refresh Salesforce Token → at Current date/time
18// Wait for workflow completion before proceeding with API call
19
20// Backend Workflow: Refresh Salesforce Token
21// Step 1: API Connector → Salesforce → Refresh Salesforce Token
22//   refresh_token: Current User's Salesforce_Tokens's refresh_token
23//   client_id: [Consumer Key - Private]
24//   client_secret: [Consumer Secret - Private]
25// Step 2: Make changes to Current User's Salesforce_Tokens
26//   access_token = Step 1 result access_token
27//   token_expiry = Current date/time + 7140 seconds (119 minutes, ~2hr with buffer)

With the authentication infrastructure in place, you can now query Salesforce data and display it in your Bubble app. For a Repeating Group showing Opportunities, set the data source to 'Get data from an external API → Salesforce → SOQL Query.' Build the SOQL query dynamically. Remember that spaces in SOQL must be URL-encoded — Bubble handles this automatically when you set the `q` parameter value in the API call. Build the instance_url dynamically in your workflow by reading `Current User's Salesforce_Tokens's instance_url`. Pass this as the `instance_url` parameter in the API Connector call. Example SOQL for open opportunities: ```sql SELECT Id, Name, StageName, Amount, CloseDate, Account.Name, Owner.Name FROM Opportunity WHERE IsClosed = false ORDER BY CloseDate ASC LIMIT 50 ``` Salesforce wraps all results in `{ "records": [...], "totalSize": N, "done": true }`. When binding to a Repeating Group, use the `records` array. For large result sets where `done = false`, use the `nextRecordsUrl` field to fetch the next batch. For creating records (POST to /sobjects/Lead/), build the JSON body as a flat object — Salesforce does NOT require the `data` array wrapper that Zoho uses. Required fields for Lead: `LastName` and `Company`. RapidDev's team has built enterprise Salesforce integrations in Bubble — if you need guidance on specific Salesforce objects (Campaigns, Cases, Custom Objects), visit rapidevelopers.com/contact for a free scoping call.

1// SOQL queries for common Salesforce objects:
2
3// Opportunities (open pipeline):
4// SELECT Id, Name, StageName, Amount, CloseDate, Account.Name, Owner.Name FROM Opportunity WHERE IsClosed = false ORDER BY Amount DESC LIMIT 50
5
6// Leads (recent, unconverted):
7// SELECT Id, FirstName, LastName, Email, Company, Phone, Status, LeadSource FROM Lead WHERE IsConverted = false ORDER BY CreatedDate DESC LIMIT 50
8
9// Contacts (by account):
10// SELECT Id, FirstName, LastName, Email, Phone, Title, Account.Name FROM Contact WHERE AccountId = '<account_id>' ORDER BY LastName ASC
11
12// Create Lead (flat JSON body - no data[] wrapper):
13{
14  "FirstName": "<first_name>",
15  "LastName": "<last_name>",  // required
16  "Email": "<email>",
17  "Company": "<company>",     // required
18  "Phone": "<phone>",
19  "LeadSource": "Web",
20  "Status": "Open - Not Contacted"
21}
22
23// Update Opportunity Stage (PATCH to /sobjects/Opportunity/{id}):
24{
25  "StageName": "<new_stage>",
26  "CloseDate": "<close_date_yyyy-mm-dd>"
27}