Propertybase

Log in to your Salesforce org with System Administrator credentials. In the top-right corner, click the gear icon → **Setup**. In Setup, use the Quick Find search bar to search for 'App Manager'. Click **App Manager** → **New Connected App** in the top-right. Fill in the Connected App form: - **Connected App Name**: Bubble Integration (or any descriptive name) - **API Name**: Bubble_Integration (auto-fills, adjust if needed) - **Contact Email**: your email address In the **API (Enable OAuth Settings)** section: - Check **Enable OAuth Settings** - **Callback URL**: https://[your-bubble-app].bubbleapps.io/oauth_callback (Bubble's URL; for now you can use a placeholder — for the password grant flow this URL is not actively used) - **Selected OAuth Scopes**: Add these scopes: - Access and manage your data (api) - Perform requests on your behalf at any time (refresh_token, offline_access) Click **Save**. Salesforce takes 2-10 minutes to provision the Connected App. After saving, click **Manage Consumer Details** (you may need to verify your identity). Copy the **Consumer Key** (client_id) and **Consumer Secret** (client_secret). Store these securely — you will paste them into Bubble's Backend Workflow in the next step. Also obtain your Salesforce **security token**: go to your Salesforce user profile → Settings → Reset My Security Token. Salesforce emails the new token to your email address. The full password for the OAuth flow is your Salesforce password + security token concatenated (e.g., if password is 'abc123' and token is 'xyz', use 'abc123xyz').

The Salesforce access token must be obtained server-side — the Consumer Secret cannot appear in any client-side Bubble action. A Backend Workflow handles this. **First, create a data type to store the token:** Go to Data tab → Data types → New type → name it 'SalesforceToken'. Add fields: - access_token (text) - instance_url (text) — Salesforce returns a unique instance URL per org; you must use this URL for all subsequent API calls, not a hardcoded base URL - issued_at (date) — to track when the token was issued **Enable Backend Workflows:** Go to **Settings** (gear icon in editor) → **API** tab → check **'This app exposes a Workflow API'**. This requires a paid Bubble plan. **Create the Backend Workflow:** Click **Backend workflows** in the left panel → **New API workflow**. Name it 'GetSalesforceToken'. Set it to be triggered by API call (not exposed publicly — this is an internal workflow). Inside the workflow, add the action **Plugins → API Connector → POST Salesforce Token** (you'll create this API Connector call in a moment, then come back). For now, proceed to configure the API Connector call first. **Configure the token endpoint in the API Connector:** Go to Plugins → API Connector → Add another API → name it 'Salesforce'. Set base URL to https://login.salesforce.com. Click **New call**. Configure: - Name: Get Access Token - Method: POST - Endpoint: /services/oauth2/token - Body type: Form parameters URL-encoded - Body parameters (all Private): - grant_type: password - client_id: [your Consumer Key] — mark Private - client_secret: [your Consumer Secret] — mark Private - username: [your Salesforce username] — mark Private - password: [your Salesforce password + security token concatenated] — mark Private Set **Use as**: Action (not Data — the response structure is a single object, not a list). Click **Initialize call**. Bubble will execute a real token exchange with Salesforce. On success, Bubble detects the response fields: access_token, instance_url, token_type, issued_at, id. These are the fields you'll store in the SalesforceToken data type. Now return to the Backend Workflow and add the workflow steps: 1. Call the 'Get Access Token' API call 2. 'Create a new SalesforceToken' with: - access_token = Result of Step 1's access_token - instance_url = Result of Step 1's instance_url - issued_at = Current date/time 3. (Optional) Delete old SalesforceToken records to prevent accumulation Trigger this Backend Workflow once manually to create the first token. The SalesforceToken record now exists in Bubble's database, ready for use.

1{
2  "call_name": "Get Access Token",
3  "method": "POST",
4  "url": "https://login.salesforce.com/services/oauth2/token",
5  "body_type": "Form URL-encoded",
6  "body": {
7    "grant_type": "password",
8    "client_id": "<consumer_key_private>",
9    "client_secret": "<consumer_secret_private>",
10    "username": "<sf_username_private>",
11    "password": "<sf_password_plus_token_private>"
12  },
13  "use_as": "Action"
14}

With a valid access token stored in Bubble's database, configure the API Connector for actual data queries against Propertybase objects. In the API Connector, within the 'Salesforce' entry, click **New call**. Configure: - Name: SOQL Query - Method: GET - Endpoint: leave this blank — you'll use a dynamic URL built from the stored instance_url Actually, for dynamic base URLs, create a separate API Connector entry: click **Add another API** → name it 'Salesforce Data'. In the **API Root URL** field, enter a placeholder — you will override this per call with the dynamic instance_url. Alternatively, structure the call URL as a dynamic parameter. The most reliable pattern for dynamic Salesforce instance URLs in Bubble: add the full URL (including instance_url prefix) as a dynamic variable in the endpoint field: - Endpoint path: /services/data/v59.0/query - Query parameter: q (dynamic SOQL string) For the Authorization header, click **Add shared headers or parameters**: - Name: Authorization - Value: Bearer [reference to SalesforceToken's access_token field from Bubble DB] - Private: checked To make the Authorization header dynamic (pulling the token from the database), you must reference it from the workflow context, not as a fixed string. In the API Connector shared header, set the value to a Bubble dynamic expression: 'Do a search for SalesforceToken sort by issued_at descending first item's access_token'. This pulls the most recent valid token. Click **New call** → name it 'Query Propertybase Listings'. Set: - Method: GET - Use as: Data - Endpoint: /services/data/v59.0/query - Query parameter q (dynamic): will be set from workflows For the Initialize call, enter a test SOQL query to confirm the connection. Example: `SELECT Id, pb__Address__c, pb__ListPrice__c, pb__Status__c FROM pb__Listing__c WHERE pb__Status__c = 'Active' LIMIT 10` URL-encode this string for the q parameter in the Initialize call test. Bubble typically handles URL encoding automatically for query parameters. If the Initialize call succeeds, Bubble detects the Salesforce response structure: totalSize, done, records[] with each record containing Id and the requested fields. This is the data structure you'll bind to Bubble UI elements.

1{
2  "call_name": "Query Propertybase Listings",
3  "method": "GET",
4  "url": "https://[instance_url_from_db]/services/data/v59.0/query",
5  "headers": {
6    "Authorization": "Bearer <access_token_from_db_private>"
7  },
8  "params": {
9    "q": "SELECT Id, pb__Address__c, pb__ListPrice__c, pb__Status__c, pb__Bedrooms__c, pb__Bathrooms__c FROM pb__Listing__c WHERE pb__Status__c = 'Active' LIMIT 100"
10  },
11  "use_as": "Data"
12}

Propertybase field API names vary by org configuration. The pb__ prefix is standard for the managed package, but specific field names (like pb__ListPrice__c vs pb__List_Price__c) depend on how Propertybase was installed and customized in your Salesforce org. You must verify the exact names in Salesforce Object Manager before building Bubble workflows. In Salesforce Setup, search for **Object Manager** in Quick Find. Click **Object Manager**. In the search box, type 'pb__' to filter for Propertybase objects. You will see: - pb__Listing__c — property listings - pb__Transaction__c — deals and closings - pb__Commission__c — commission records - Other pb__ objects depending on your Propertybase version Click on **pb__Listing__c** → click **Fields & Relationships** in the left panel. This shows every field on the Listing object with its **Field Label** (human-readable) and **Field Name** (API name, the one you use in SOQL queries). Common fields: - pb__Address__c — property address - pb__ListPrice__c — list price - pb__Status__c — listing status - pb__Bedrooms__c — bedroom count - pb__Listing_Agent__c — assigned agent (lookup to User) - pb__CloseDate__c — close date (on Transaction) Make a list of the exact API names for every field you plan to display in Bubble. Any mismatch between what you write in a SOQL query and the actual field API name results in a Salesforce error: 'No such column 'fieldname' on entity 'pb__Listing__c'. For status values: click on pb__Status__c's field label to see its picklist values. These are the exact strings you'll use in SOQL WHERE clauses (e.g., WHERE pb__Status__c = 'Active' — the value must match the picklist entry exactly, including capitalization). Write down your verified SOQL query: ``` SELECT Id, pb__Address__c, pb__ListPrice__c, pb__Status__c, pb__Bedrooms__c FROM pb__Listing__c WHERE pb__Status__c = 'Active' ORDER BY pb__ListPrice__c ASC LIMIT 100 ``` Test this query in Salesforce's **Developer Console** (Setup → Developer Console → Query Editor tab) before putting it in Bubble. If it works in Developer Console, it will work in Bubble's API call.

1-- Test in Salesforce Developer Console (Query Editor tab)
2-- Replace field names with your org's actual API names
3SELECT 
4  Id,
5  pb__Address__c,
6  pb__ListPrice__c,
7  pb__Status__c,
8  pb__Bedrooms__c,
9  pb__Bathrooms__c,
10  pb__Listing_Agent__r.Name
11FROM pb__Listing__c
12WHERE pb__Status__c = 'Active'
13ORDER BY pb__ListPrice__c ASC
14LIMIT 100

With the API Connector configured and field names verified, build the Propertybase listing dashboard. **Create Bubble data types for caching:** Go to Data tab → New type → 'PropertybaseListing'. Add fields matching your verified SOQL fields: - sf_id (text) — Salesforce Id - address (text) — pb__Address__c value - list_price (number) — pb__ListPrice__c value - status (text) — pb__Status__c value - bedrooms (number) — pb__Bedrooms__c value - bathrooms (number) — pb__Bathrooms__c value - last_synced (date) **Create a sync workflow:** In the Workflow editor, add a workflow triggered by a 'Sync Listings' button: 1. Call the SOQL Query API call with the verified Propertybase query 2. For each record in Result's records list: - Search for existing PropertybaseListing where sf_id = record's Id - If found: Make changes to update fields - If not found: Create new PropertybaseListing 3. Update the sync timestamp displayed on the page Note: Bubble's native 'For each record' looping is available via a recursive Backend Workflow (paid plan) or via the API Connector's list handling. For smaller datasets (under 100 records), use Bubble's 'create/modify a list of things' approach. **Build the repeating group:** Add a Repeating Group: - Type of content: PropertybaseListing - Data source: Do a search for PropertybaseListing (with optional status filter) - Layout: list, 1 column for a dashboard style Inside the cell: - Text for address: Current cell's PropertybaseListing's address - Text for price: '$' + Current cell's list_price formatted as dollar amount - Text for bedrooms: Current cell's bedrooms + ' beds' - A status badge: text showing Current cell's status, conditionally styled (green background when 'Active', grey when 'Pending') - A 'View in Salesforce' link: https://[your org].lightning.force.com/[current cell's sf_id] **Add privacy rules:** Go to Data → Privacy → PropertybaseListing → add rule: 'When Current User is logged in and Current User's role = Agent or Manager → all fields visible'. Unauthenticated users should not read listing data.

**Schedule the token refresh:** Salesforce access tokens from the password grant flow typically expire within 2 hours. To keep the integration running without manual intervention, create a scheduled Backend Workflow that refreshes the token automatically. In Backend Workflows, create a new workflow named 'RefreshSalesforceToken'. Add the same steps as the GetSalesforceToken workflow: POST to the Salesforce token endpoint and update the SalesforceToken record in Bubble's database. To schedule it: in the Backend Workflows panel, click the clock icon next to RefreshSalesforceToken → **Schedule recurring** → set interval to every 90 minutes (giving a 30-minute buffer before the 2-hour expiry). This requires a paid Bubble plan. On the free plan, you would need to manually trigger token refresh — which is not viable for a production integration. RapidDev's team has built Salesforce-connected Bubble apps for real estate brokerages integrating with Propertybase, Salesforce CRM, and custom SF objects — if you need help with the SOQL data model or token refresh architecture, book a free scoping call at rapidevelopers.com/contact. **Handle SOQL pagination for large portfolios:** Salesforce limits SOQL results to 2,000 records per query. For brokerages with large listing databases, implement offset-based pagination: ```sql SELECT Id, pb__Address__c, pb__ListPrice__c, pb__Status__c FROM pb__Listing__c WHERE pb__Status__c = 'Active' ORDER BY Id ASC LIMIT 2000 OFFSET 0 ``` Increment the OFFSET by 2000 in each iteration of a recursive Backend Workflow until totalSize is reached. Store each page of results into Bubble's database during the sync, then query the Bubble database (not Salesforce directly) for display — this keeps the UI fast and avoids repeated Salesforce API calls. Salesforce API call limits apply at the edition level (Developer: 15,000/day; Enterprise: 150,000/day — verify current limits). For large syncs, consider running the full sync nightly via a scheduled Backend Workflow and only fetching changes (records modified in the last 24 hours) during daytime refresh cycles using a SOQL WHERE clause like: `WHERE LastModifiedDate >= [24 hours ago]`.

1-- Incremental sync: only fetch recently modified records
2-- Run this on hourly scheduled Backend Workflow
3SELECT 
4  Id,
5  pb__Address__c,
6  pb__ListPrice__c, 
7  pb__Status__c,
8  pb__Bedrooms__c,
9  LastModifiedDate
10FROM pb__Listing__c
11WHERE LastModifiedDate >= LAST_N_HOURS:24
12ORDER BY LastModifiedDate DESC
13LIMIT 2000