feat(integrations): add Dynamics 365 CRM - #6714

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Aug 28, 2026 7:55pm

PR Summary

High Risk
Touches OAuth linking, callback scope validation, credential identity binding, and token resolution for Microsoft Dataverse—security-sensitive auth paths alongside a large new CRM surface. PR description also flags a merge dependency on server-side credential rebinding enforcement (#6716).

Overview
Adds a Microsoft Dynamics 365 CRM integration and workflow block with ten CRM-focused operations (list/get/create/update/search on standard tables, list owners, assign, qualify lead, close opportunity/case), backed by dedicated microsoft_dynamics_365_* tools while the generic Microsoft Dataverse block stays available for custom tables and delete.

Environment-bound OAuth is new for Dynamics paths: connect/reconnect flows collect a public-cloud Dataverse environment URL, request per-environment Microsoft scopes, validate link/callback scopes in auth, and persist an internal environment marker so credentials are not rebound across environments. Legacy unbound Dataverse credentials keep working; workflow credential selection enforces a matching environment when the block depends on environmentUrl. Token resolution projects instanceUrl from bound scopes for CRM calls.

Docs, integrations catalog, and icon mappings register microsoft_dynamics_365; connect modals, credential detail reconnect, and OAuth return handling wire in the Dataverse environment field and dedicated connect hook.

^{Reviewed by Cursor Bugbot for commit a2842cf. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

Adds a Microsoft Dynamics 365 CRM integration backed by environment-bound Dataverse OAuth and eight CRM tool modules.

• Registers a ten-operation workflow block, generated tool metadata, documentation, icons, and deployment configuration.
• Adds environment-specific OAuth connection, reconnection, credential-selection, and token-resolution behavior.
• Implements bounded listing and search plus record creation, retrieval, updating, lead qualification, opportunity closure, and case resolution.

Confidence Score: 5/5

The PR appears safe to merge from the reviewed follow-up scope because the previously reported redirect credential leak has been fixed.

No blocking failure remains from the prior redirect-safety finding: every Dynamics request enables authorization stripping, the shared transport enforces it on redirects, and the regression test covers all eight request definitions.

sequenceDiagram
  actor User
  participant UI as Workflow or integration UI
  participant OAuth as Dataverse OAuth
  participant Executor as Tool executor
  participant CRM as Dynamics 365 CRM
  User->>UI: Select environment and connect
  UI->>OAuth: Request environment-qualified scopes
  OAuth-->>UI: Environment-bound credential
  User->>UI: Configure CRM operation
  UI->>Executor: Execute with credential and environment
  Executor->>CRM: Dataverse API request
  Note over Executor,CRM: Authorization removed before following redirects
  CRM-->>Executor: Structured CRM response
  Executor-->>UI: Normalized operation output

_{Reviews (7): Last reviewed commit: "test(integrations): isolate Dynamics OAu..." | Re-trigger Greptile}

@greptile please re-review the latest commit.

@cursor review

@cursor review

@greptile please re-review the rebased latest commit.

@greptile please re-review the latest exact-head commit. The update preserves the opaque Dataverse nextLink with a paired page-size contract and aligns Opportunity Close/Case Resolution metadata limits.

@cursor review

@greptile

@greptile

@greptile