TRAINING PROJECT

Salesforce deployment with Heroku (Legarant‑AXG)

Salesforce deployment and integration for LEGARANT-AXG: REST API, Heroku synchronization and go-live.

Context

LEGARANT, a life insurance company founded in 1980 in Nantes, acquired AXG in Germany. Integrating both CRMs required one-way synchronization of AXG data to Salesforce France, REST APIs documented via Postman, and deployment of a mobile application via Heroku Connect. Mission: design and deploy the complete technical architecture following Salesforce best practices.

Technical Challenges

One-way AXG → Salesforce sync without creating duplicates (idempotency required)
DELETE on contact = deactivation, not physical deletion (insurance industry business rule)
Unique External ID to guarantee AXG ↔ Salesforce record matching
Heroku ↔ Salesforce bidirectional connector for the Heroku mobile application

Solutions Developed

Custom Apex REST controller: contact creation with email verification before insertion
Apex DELETE endpoint: contact deactivation (IsActive = false) instead of physical deletion
Apex Trigger for automatic External ID population — uniqueness guaranteed on creation
Heroku Connect configured for bidirectional sync: Heroku PostgreSQL ↔ Salesforce
Complete Postman collection: GET, POST, PATCH, DELETE — all endpoints tested and documented
Deployment document: delivered components, manual steps, installation order

Stack & Technologies

Apex REST (@RestResource) — Custom endpoints exposed over HTTPS
Postman — Complete REST API calls collection
Heroku Connect — PostgreSQL ↔ Salesforce synchronization
Apex Trigger — Automatic External ID population
Salesforce DX — Metadata deployment
JSON — REST API data exchange format

Project Timeline

1
Architecture
Integration schema defined — AXG→Salesforce flow, required endpoints, External ID strategy
2
REST API (Postman)
4 standard endpoints implemented (GET/POST/PATCH/DELETE) on Salesforce objects, tested via Postman
3
Apex controller
Custom Apex REST endpoint built — contact creation with email check + deactivation on DELETE
4
External ID
Apex Trigger auto-populating External ID on contact creation — uniqueness guaranteed
5
Heroku Connect

Results

2/2

Skills validated

OpenClassrooms jury

API endpoints

GET, POST, PATCH, DELETE

Bidirectional

Synchronization

Heroku ↔ Salesforce

Félicitations!

Jury assessment

Clean architecture, well documented

Capturas de pantalla