Overview:

This guide provides detailed information on the expected JSON format for leads coming from MoveBuddha and how the payloads are processed. It is intended as a technical reference for how the MoveBuddha Integration is working. 

Relevant Links: 

• Known Lead Provider Integrations - Link 
• Debugging Inbound Leads - Link 
• MoveBuddha Website - Link

Integration Settings: 

Inbound MoveBuddha Payload: 

{
  "first_name": "Test",
  "last_name": "User",
  "email": "test@movebuddha.com",
  "date": "2025-04-01",
  "move_type": "Long distance intrastate",
  "origin_city": "Rockwall",
  "origin_state": "TX",
  "origin_zip_code": "75087",
  "destination_city": "Granbury",
  "destination_state": "TX",
  "destination_zip_code": "76048",
  "move_size": "3BR house",
  "phone_number": "5555555555"
}

MoveBuddha to Supermove, Specifics: 

• move_type - This is mapped into the supermove internal notes as "MoveBuddha Move Type". Move types are utilized in different ways depending on the Supermove Customer. As such, we allow this allows to the move_type to be included without interrupting workflows across different customer accounts. 
• move_size - Normalized to its equivalent standard Supermove Project Size.