Overview

CRM integrations with Dynamic Planner typically combine interactive user journeys (Fact Find, Risk Profiling, Reviews) with background synchronisation of client records, arrangements and planning data. Integrations must use secure OAuth flows, handle webhook-style event notifications, and maintain consistency between CRM and Dynamic Planner entities.

Common integration capabilities include:

• Launching Dynamic Planner Fact Finds and workflows from CRM screens
• Synchronising client, relationship and arrangement data
• Reading risk profiles, plans, reviews and adviser outputs
• Receiving event notifications (e.g., fact find opened or completed)
• Reducing manual re‑keying and enabling adviser automation

How CRM Integrations Work

CRM systems interact with Dynamic Planner using REST APIs, OAuth authentication and optional event notification subscriptions. Most implementations require both interactive user-context calls and backend system-to-system processing.

• Hybrid OAuth Flow — used when a CRM user launches a Dynamic Planner workflow (Fact Find, Profiling, Recommendation).
• Client Credentials Flow — used for internal or scheduled CRM background services that synchronise data without a user present.
• Event Subscriptions — allow CRMs to receive notifications when client actions occur in Dynamic Planner.

Requirements

To implement a CRM integration you will need:

• A Dynamic Planner developer account
• Allocated OAuth credentials (client_id and client_secret)
• Approved scopes for the required CRM and Fact Find operations
• Support for secure refresh-token handling
• Logging of x-dt-traceid and x-dt-requestid for diagnostics and support enquiries

Make sure you have reviewed the Authentication & Access documentation before implementing CRM workflows.

Supported Features

CRM integrations vary by partner but typically include some or all of the following capabilities:

• Start a Fact Find, Review or Planning process from a CRM record
• Retrieve up‑to‑date risk profiles and investment recommendations
• Sync client and relationship structures across systems
• Read arrangements, valuations and product information
• Receive event notifications for workflow automation

Data Flow Overview

CRM interactions with Dynamic Planner generally follow this sequence:

1. A CRM user or service obtains a valid OAuth access token.
2. The CRM calls the required API endpoints (clients, relationships, arrangements).
3. If enabled, Dynamic Planner sends events when the user interacts with workflows.
4. The CRM updates its records based on new analysis, outcomes or fact find data.

This ensures both systems remain aligned while reducing adviser duplication.

Best Practices for CRM Integrations

• Implement retry logic for transient HTTP errors (429, 500, 503) using exponential back‑off.
• Use idempotency keys whenever creating or updating entities to avoid duplicates.
• Cache tokens responsibly and refresh them before expiry.
• Minimise API calls by batching CRM synchronisation where possible.
• Log all diagnostic headers to speed up issue resolution.

Next Steps

1. Request OAuth credentials via the “Get API Access” form.
2. Review the Authentication, Making Requests and Pagination guides.
3. Check the API Reference (Swagger) for available CRM‑related endpoints.
4. Implement core client and relationship sync flows.
5. Enable event subscriptions if workflow automation is required.
6. Test end‑to‑end scenarios in the sandbox environment.