Microsoft Dynamics 365

Open portal.azure.com and sign in with a Microsoft account that has access to the Azure Active Directory tenant for your organization. In the left sidebar, search for 'App registrations' and click it. Click '+ New registration.' Fill in the registration form: - Name: `Bubble Dynamics Integration` - Supported account types: 'Accounts in this organizational directory only' (single-tenant) - Redirect URI: select 'Web' and enter your Bubble app's OAuth callback URL: `https://yourapp.bubbleapps.io/oauth_callback` Click 'Register.' You will see the Overview page with your Application (client) ID and Directory (tenant) ID — copy both. Now add the Dynamics API permission. Click 'API permissions' in the left sidebar. Click '+ Add a permission.' Click 'Dynamics CRM' (scroll down or search for it). Select 'Delegated permissions.' Check `user_impersonation`. Click 'Add permissions.' You should now see 'Dynamics CRM user_impersonation' in the permissions list with status 'Not granted for [your tenant].' Here is the critical step: click 'Grant admin consent for [your organization].' Only a Global Administrator or Application Administrator can click this button. If you see it greyed out, you do not have this role — contact your Azure AD admin. After admin consent is granted, the status changes to 'Granted for [your tenant]' with a green checkmark. Finally, create a client secret. Click 'Certificates & secrets' → '+ New client secret.' Set an expiry (24 months is recommended). Click 'Add' and IMMEDIATELY copy the secret Value — it is only shown once.

1// Azure AD App Registration details to collect:
2// Application (client) ID  → used as client_id in OAuth
3// Directory (tenant) ID    → used in token URL
4// Client Secret Value      → used as client_secret (copy immediately)
5
6// Token endpoint URL format:
7// https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token
8
9// Authorization URL format (for authorization_code flow):
10// https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/authorize
11//   ?client_id={client_id}
12//   &response_type=code
13//   &redirect_uri=https://yourapp.bubbleapps.io/oauth_callback
14//   &scope=https://orgname.crm.dynamics.com/user_impersonation offline_access
15//   &response_mode=query
16
17// Required permission:
18// API: Dynamics CRM
19// Permission: user_impersonation (delegated)
20// Admin consent: REQUIRED — must be granted by Global Admin or App Admin

Before configuring the API Connector, create the data infrastructure for storing Azure AD tokens in Bubble. In the Data tab, add a data type named `Dynamics_Auth` with these fields: - `access_token` (text) - `refresh_token` (text) - `org_url` (text) — the Dynamics 365 environment URL (e.g., `https://yourorg.crm.dynamics.com`) - `token_expiry` (date) - `user` (User) Apply a privacy rule to Dynamics_Auth: 'Everyone else → no fields visible.' Enable 'Ignore privacy rules when using workflows.' Create an `oauth_callback` page in Bubble if you do not have one from another integration. This page will receive the `?code=` URL parameter from Azure AD after user authentication. Now go to Backend Workflows and create two workflows: Workflow 1 — `Exchange Dynamics Code`: Input parameter `code` (text). Steps: (1) Call API Connector → Dynamics → Exchange Code for Token (create in next step). (2) Create or update Dynamics_Auth record: access_token, refresh_token, org_url (from response), token_expiry = Current date/time + 3540 seconds, user = Current User. Workflow 2 — `Refresh Dynamics Token`: No inputs. Steps: (1) Call API Connector → Dynamics → Refresh Token using Current User's Dynamics_Auth refresh_token. (2) Update Current User's Dynamics_Auth: new access_token and new token_expiry.

1// Dynamics_Auth data type:
2// access_token   → text
3// refresh_token  → text
4// org_url        → text  (e.g., 'https://yourorg.crm.dynamics.com')
5// token_expiry   → date
6// user           → User
7
8// Privacy: Everyone else → no fields visible
9// ✓ Ignore privacy rules when using workflows
10
11// Backend Workflow: Exchange Dynamics Code
12// Input: code (text)
13// Step 1: API Connector → Dynamics → Exchange Code for Token
14//   code: input code
15//   client_id: [Private]
16//   client_secret: [Private]
17//   tenant_id: [Private]
18//   redirect_uri: https://yourapp.bubbleapps.io/oauth_callback
19// Step 2: Create Dynamics_Auth
20//   access_token = Step1.access_token
21//   refresh_token = Step1.refresh_token
22//   org_url = Step1.resource (or hardcode your org URL)
23//   token_expiry = Current date/time + 3540 seconds
24//   user = Current User

In Plugins → API Connector, click 'Add another API' and name it `Microsoft Dynamics 365`. Set the base URL to your Dynamics 365 environment: `https://yourorg.crm.dynamics.com/api/data/v9.2`. Replace `yourorg` with your actual organization name (the subdomain of your Dynamics URL). Add four shared headers — ALL FOUR are required for every OData call: 1. `OData-MaxVersion: 4.0` 2. `OData-Version: 4.0` 3. `Accept: application/json` 4. `Content-Type: application/json` Add a fifth shared header for authentication: 5. `Authorization: Bearer <access_token>` — mark as Private dynamic parameter Now add the key API calls: Call 1 — Exchange Code for Token: Method POST. URL: `https://login.microsoftonline.com/<tenant_id>/oauth2/v2.0/token`. Body (form-encoded): `grant_type=authorization_code`, `code=<code>`, `client_id=<client_id>` (Private), `client_secret=<client_secret>` (Private), `scope=https://yourorg.crm.dynamics.com/user_impersonation offline_access`, `redirect_uri=https://yourapp.bubbleapps.io/oauth_callback`. Set as Action. Call 2 — Refresh Token: Method POST. Same token URL. Body: `grant_type=refresh_token`, `refresh_token=<refresh_token>` (Private), `client_id=<client_id>` (Private), `client_secret=<client_secret>` (Private). Set as Action. Call 3 — Get Contacts: Method GET. URL: `/contacts`. URL parameters: `$select=fullname,emailaddress1,telephone1,accountid`, `$filter=<filter_expression>` (dynamic), `$top=50`, `$orderby=createdon desc`. Set as Data. Initialize call — should return a response with a `value` array.

1// Shared headers (ALL REQUIRED on every Dynamics call):
2// OData-MaxVersion: 4.0
3// OData-Version: 4.0
4// Accept: application/json
5// Content-Type: application/json
6// Authorization: Bearer <access_token>  [Private dynamic param]
7
8// Call 3: Get Contacts
9{
10  "method": "GET",
11  "url": "https://yourorg.crm.dynamics.com/api/data/v9.2/contacts",
12  "params": {
13    "$select": "fullname,emailaddress1,telephone1,telephone2,accountid",
14    "$filter": "<filter_expression>",  // e.g., contains(fullname,'Smith')
15    "$top": "50",
16    "$orderby": "createdon desc"
17  }
18}
19// Response: { "@odata.context": "...", "value": [ { "fullname": "...", ... } ] }
20// Bubble binding: use 'value' array as list data source
21
22// OAuth scope for Dynamics:
23// https://yourorg.crm.dynamics.com/user_impersonation offline_access
24// The org URL MUST match your actual Dynamics environment URL exactly
25// Generic Microsoft scopes (like https://graph.microsoft.com) do NOT work for Dynamics

OData v4 query syntax expresses filtering, field selection, sorting, and joins entirely through URL parameters — not a query body like SQL or SOQL. Here is how to build common Dynamics queries in Bubble's API Connector: **$select** — specify which fields to return (always include this to avoid huge responses): `$select=name,emailaddress1,revenue,statuscode` **$filter** — filter records (OData operators: `eq`, `ne`, `gt`, `lt`, `ge`, `le`, `and`, `or`, `contains`, `startswith`, `endswith`): `$filter=statuscode eq 1 and revenue gt 1000000` `$filter=contains(name,'Microsoft')` `$filter=statecode eq 0` (0 = active, 1 = inactive for most entities) **$expand** — join related entities (like SQL JOIN): `$expand=primarycontactid($select=fullname,emailaddress1)` — expands the primary contact on an account **$orderby** and **$top**: `$orderby=createdon desc&$top=50` Dynamics 365 entity names (used in the URL path): - Contacts: `/contacts` - Accounts: `/accounts` - Leads: `/leads` - Opportunities: `/opportunities` - Cases: `/incidents` In Bubble, set each OData parameter as a URL parameter in the API Connector call. Bubble's text composition in parameter values supports building dynamic filter expressions. For PATCH (update) operations: the URL is `/contacts(guid)` where the GUID is in parentheses, NOT as a path segment. Dynamics GUIDs look like `3d86a63b-a5a4-ed11-81a9-002248e89db3`. PATCH returns HTTP 204 with an empty body — Bubble will not throw an error but you get no confirmation JSON. Handle this with a subsequent GET call to verify the update if needed.

1// Common OData queries for Dynamics 365 entities:
2
3// Get active accounts with $expand for primary contact:
4// GET /accounts?$select=name,telephone1,revenue,websiteurl&$filter=statecode eq 0&$expand=primarycontactid($select=fullname,emailaddress1)&$top=50&$orderby=revenue desc
5
6// Get opportunities in active stage:
7// GET /opportunities?$select=name,estimatedvalue,stepname,closeddateestimate,parentaccountid&$filter=statecode eq 0&$orderby=closeddateestimate asc&$top=100
8
9// Search contacts by name:
10// GET /contacts?$select=fullname,emailaddress1,telephone1&$filter=contains(fullname,'<search_term>')&$top=20
11
12// Create a new Lead:
13// POST /leads
14// Body: { "firstname": "Jane", "lastname": "Smith", "emailaddress1": "jane@company.com", "companyname": "Acme Corp" }
15
16// Update contact email (PATCH returns 204, no body):
17// PATCH /contacts(3d86a63b-a5a4-ed11-81a9-002248e89db3)
18// Body: { "emailaddress1": "new@email.com" }
19
20// Dynamics entity plural names:
21// contacts, accounts, leads, opportunities, incidents (cases), tasks, phonecalls

Create the user-facing login flow that connects each Bubble user to their Dynamics 365 account. Add a 'Connect Dynamics 365' button to your onboarding or settings page. When clicked, it redirects to the Azure AD authorization URL: ``` https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/authorize?client_id={client_id}&response_type=code&redirect_uri=https://yourapp.bubbleapps.io/oauth_callback&scope=https://yourorg.crm.dynamics.com/user_impersonation+offline_access&response_mode=query ``` On your `oauth_callback` page, add a Page is loaded workflow: - Condition: Get URL parameter 'code' is not empty - Action: Schedule API Workflow → Exchange Dynamics Code (at Current date/time), passing `code` = Get URL parameter 'code' - After workflow: Navigate to main dashboard page For token refresh in every workflow that calls Dynamics: 1. Check: Is Current User's Dynamics_Auth token_expiry < Current date/time? OR Is Dynamics_Auth empty? 2. If yes: Schedule API Workflow → Refresh Dynamics Token (at Current date/time) 3. Then proceed with the Dynamics API call using the stored access_token For the `oauth_callback` page to also handle errors (user cancelled or consent denied), add a second condition: - Condition: Get URL parameter 'error' is not empty - Action: Navigate to login page, passing error message as URL parameter for display RapidDev's team has experience with enterprise Azure AD integrations in Bubble — visit rapidevelopers.com/contact if you need help navigating your organization's Azure AD tenant requirements.

1// Azure AD Authorization URL:
2https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/authorize
3  ?client_id={client_id}
4  &response_type=code
5  &redirect_uri=https://yourapp.bubbleapps.io/oauth_callback
6  &scope=https://yourorg.crm.dynamics.com/user_impersonation+offline_access
7  &response_mode=query
8
9// oauth_callback page workflow:
10// Trigger: Page is loaded
11// Case 1: code param exists
12//   Action: Schedule API Workflow → Exchange Dynamics Code
13//     code = Get URL parameter 'code'
14//   Then: Navigate to /dashboard
15// Case 2: error param exists
16//   Action: Navigate to /login?msg=dynamics_auth_failed
17
18// Token refresh check in all Dynamics workflows:
19// Condition: Dynamics_Auth is empty OR token_expiry < Current date/time
20// Action: Schedule API Workflow → Refresh Dynamics Token
21// Wait: Add a 2-second pause or chain the next action after the Backend Workflow
22
23// Then call Dynamics API with:
24// Authorization header: Bearer + Current User's Dynamics_Auth access_token