Back to Integrations
Integration Setup
Connect MagicBricks to 365 RND CRM
Automatically sync leads from your MagicBricks property listings.
Source Key: magicbricksWebhook Ready
How To Connect
1
Use MagicBricks lead export, forwarding, or a middleware connector to call the CRM webhook.
2
Include listing or project information in `message` so the CRM record has property context.
3
Make sure the webhook sends the shared secret for authorization.
4
Run a test enquiry and verify the lead owner and source in the CRM.
What CRM Does After Capture
MagicBricks leads enter your pipeline with source `magicbricks`.
Agents can track notes, meetings, reminders, and stage changes in one workflow.
Troubleshooting is easier because the raw webhook payload is retained.
Supported Fields
namephoneemailcompany_namemessageassigned_tofollow_up_date
The backend also normalizes common aliases like `full_name`, `mobile`, `company`, `notes`, and nested `data.*` webhook fields.
Example Payload
{
"name": "Aman Sharma",
"phone": "+91 98765 43210",
"email": "aman@example.com",
"company_name": "RND Prospect",
"message": "Interested in a demo and pricing details.",
"assigned_to": "clerk_user_id_or_internal_user_id"
}Sample Request
curl -X POST "http://localhost:3072/api/integrations/webhook/magicbricks" \
-H "Content-Type: application/json" \
-H "x-integration-secret: <your-secret>" \
-d '{
"name": "Aman Sharma",
"phone": "+91 98765 43210",
"email": "aman@example.com",
"company_name": "RND Prospect",
"message": "Interested in a demo and pricing details.",
"assigned_to": "clerk_user_id_or_internal_user_id"
}'Need a custom mapping?
If the source sends unusual field names, we can extend the mapping layer in the backend without changing your sales workflow.